|
2613 | 2613 | "shape":"SecurityPolicy",
|
2614 | 2614 | "documentation":"<p>The Transport Layer Security (TLS) version + cipher suite for this <a>DomainName</a>. The valid values are <code>TLS_1_0</code> and <code>TLS_1_2</code>.</p>"
|
2615 | 2615 | },
|
2616 |
| - "mutualTlsAuthentication":{"shape":"MutualTlsAuthenticationInput"} |
| 2616 | + "mutualTlsAuthentication":{"shape":"MutualTlsAuthenticationInput"}, |
| 2617 | + "ownershipVerificationCertificateArn":{ |
| 2618 | + "shape":"String", |
| 2619 | + "documentation":"<p>The ARN of the public certificate issued by ACM to validate ownership of your custom domain. Only required when configuring mutual TLS and using an ACM imported or private CA certificate ARN as the regionalCertificateArn.</p>" |
| 2620 | + } |
2617 | 2621 | },
|
2618 | 2622 | "documentation":"<p>A request to create a new domain name.</p>"
|
2619 | 2623 | },
|
|
3565 | 3569 | },
|
3566 | 3570 | "domainNameStatus":{
|
3567 | 3571 | "shape":"DomainNameStatus",
|
3568 |
| - "documentation":"<p>The status of the <a>DomainName</a> migration. The valid values are <code>AVAILABLE</code> and <code>UPDATING</code>. If the status is <code>UPDATING</code>, the domain cannot be modified further until the existing operation is complete. If it is <code>AVAILABLE</code>, the domain can be updated.</p>" |
| 3572 | + "documentation":"<p>The status of the <a>DomainName</a> migration. The valid values are <code>AVAILABLE</code>, <code>UPDATING</code>, <code>PENDING_CERTIFICATE_REIMPORT</code>, and <code>PENDING_OWNERSHIP_VERIFICATION</code>. If the status is <code>UPDATING</code>, the domain cannot be modified further until the existing operation is complete. If it is <code>AVAILABLE</code>, the domain can be updated.</p>" |
3569 | 3573 | },
|
3570 | 3574 | "domainNameStatusMessage":{
|
3571 | 3575 | "shape":"String",
|
|
3582 | 3586 | "mutualTlsAuthentication":{
|
3583 | 3587 | "shape":"MutualTlsAuthentication",
|
3584 | 3588 | "documentation":"<p>The mutual TLS authentication configuration for a custom domain name. If specified, API Gateway performs two-way authentication between the client and the server. Clients must present a trusted certificate to access your API.</p>"
|
| 3589 | + }, |
| 3590 | + "ownershipVerificationCertificateArn":{ |
| 3591 | + "shape":"String", |
| 3592 | + "documentation":"<p>The ARN of the public certificate issued by ACM to validate ownership of your custom domain. Only required when configuring mutual TLS and using an ACM imported or private CA certificate ARN as the regionalCertificateArn.</p>" |
3585 | 3593 | }
|
3586 | 3594 | },
|
3587 | 3595 | "documentation":"<p>Represents a custom domain name as a user-friendly host name of an API (<a>RestApi</a>).</p> <div class=\"Remarks\"> <p>When you deploy an API, API Gateway creates a default host name for the API. This default API host name is of the <code>{restapi-id}.execute-api.{region}.amazonaws.com</code> format. With the default host name, you can access the API's root resource with the URL of <code>https://{restapi-id}.execute-api.{region}.amazonaws.com/{stage}/</code>. When you set up a custom domain name of <code>apis.example.com</code> for this API, you can then access the same resource using the URL of the <code>https://apis.examples.com/myApi</code>, where <code>myApi</code> is the base path mapping (<a>BasePathMapping</a>) of your API under the custom domain name. </p> </div> <div class=\"seeAlso\"> <a href=\"https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html\">Set a Custom Host Name for an API</a> </div>"
|
|
3591 | 3599 | "enum":[
|
3592 | 3600 | "AVAILABLE",
|
3593 | 3601 | "UPDATING",
|
3594 |
| - "PENDING" |
| 3602 | + "PENDING", |
| 3603 | + "PENDING_CERTIFICATE_REIMPORT", |
| 3604 | + "PENDING_OWNERSHIP_VERIFICATION" |
3595 | 3605 | ]
|
3596 | 3606 | },
|
3597 | 3607 | "DomainNames":{
|
|
0 commit comments