feat(client-route-53): Amazon Route 53 now supports the Asia Pacific (Melbourne) Region (ap-southeast-4) for latency records, geoproximity records, and private DNS for Amazon VPCs in that region.

Author: awstools

clients/client-route-53/src/Route53.ts

@@ -570,19 +570,19 @@ export interface Route53ClientResolvedConfig extends Route53ClientResolvedConfig
 /**
  * <p>Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web
  * 			service.</p>
- * 		       <p>You can use Route 53 to:</p>
- * 		       <ul>
+ *          <p>You can use Route 53 to:</p>
+ *          <ul>
  *             <li>
  *                <p>Register domain names.</p>
- * 				           <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-domain-registration.html">How domain registration works</a>.</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-domain-registration.html">How domain registration works</a>.</p>
  *             </li>
  *             <li>
  *                <p>Route internet traffic to the resources for your domain</p>
- * 				           <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html">How internet traffic is routed to your website or web application</a>.</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html">How internet traffic is routed to your website or web application</a>.</p>
  *             </li>
  *             <li>
  *                <p>Check the health of your resources.</p>
- * 				           <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-health-checks.html">How Route 53 checks the health of your resources</a>.</p>
+ *                <p>For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-health-checks.html">How Route 53 checks the health of your resources</a>.</p>
  *             </li>
  *          </ul>
  */

clients/client-route-53/src/Route53Client.ts

@@ -31,39 +31,39 @@ export interface AssociateVPCWithHostedZoneCommandOutput extends AssociateVPCWit
 
 /**
  * <p>Associates an Amazon VPC with a private hosted zone. </p>
- * 		       <important>
- * 			         <p>To perform the association, the VPC and the private hosted zone must already
+ *          <important>
+ *             <p>To perform the association, the VPC and the private hosted zone must already
  * 				exist. You can't convert a public hosted zone into a private hosted zone.</p>
- * 		       </important>
- * 		       <note>
- * 			         <p>If you want to associate a VPC that was created by using one Amazon Web Services account with a private hosted zone that was created by using a
+ *          </important>
+ *          <note>
+ *             <p>If you want to associate a VPC that was created by using one Amazon Web Services account with a private hosted zone that was created by using a
  * 				different account, the Amazon Web Services account that created the private hosted
  * 				zone must first submit a <code>CreateVPCAssociationAuthorization</code> request.
  * 				Then the account that created the VPC must submit an
  * 					<code>AssociateVPCWithHostedZone</code> request.</p>
- * 		       </note>
- * 		       <note>
- * 			         <p>When granting access, the hosted zone and the Amazon VPC must belong to
+ *          </note>
+ *          <note>
+ *             <p>When granting access, the hosted zone and the Amazon VPC must belong to
  * 				the same partition. A partition is a group of Amazon Web Services Regions. Each
  * 					Amazon Web Services account is scoped to one partition.</p>
- * 			         <p>The following are the supported partitions:</p>
- * 			         <ul>
+ *             <p>The following are the supported partitions:</p>
+ *             <ul>
  *                <li>
- * 					             <p>
+ *                   <p>
  *                      <code>aws</code> - Amazon Web Services Regions</p>
- * 				           </li>
+ *                </li>
  *                <li>
- * 					             <p>
+ *                   <p>
  *                      <code>aws-cn</code> - China Regions</p>
- * 				           </li>
+ *                </li>
  *                <li>
- * 					             <p>
+ *                   <p>
  *                      <code>aws-us-gov</code> - Amazon Web Services GovCloud (US) Region</p>
- * 				           </li>
+ *                </li>
  *             </ul>
- * 			         <p>For more information, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Access Management</a>
+ *             <p>For more information, see <a href="https://docs.aws.amazon.com/general/latest/gr/aws-arns-and-namespaces.html">Access Management</a>
  * 				in the <i>Amazon Web Services General Reference</i>.</p>
- * 		       </note>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

clients/client-route-53/src/commands/AssociateVPCWithHostedZoneCommand.ts

@@ -32,28 +32,28 @@ export interface ChangeCidrCollectionCommandOutput extends ChangeCidrCollectionR
 /**
  * <p>Creates, changes, or deletes CIDR blocks within a collection. Contains authoritative
  * 			IP information mapping blocks to one or multiple locations.</p>
- * 		       <p>A change request can update multiple locations in a collection at a time, which is
+ *          <p>A change request can update multiple locations in a collection at a time, which is
  * 			helpful if you want to move one or more CIDR blocks from one location to another in one
  * 			transaction, without downtime. </p>
- * 		       <p>
+ *          <p>
  *             <b>Limits</b>
  *          </p>
- * 		       <p>The max number of CIDR blocks included in the request is 1000. As a result, big updates
+ *          <p>The max number of CIDR blocks included in the request is 1000. As a result, big updates
  * 			require multiple API calls.</p>
- * 		       <p>
+ *          <p>
  *             <b> PUT and DELETE_IF_EXISTS</b>
  *          </p>
- * 		       <p>Use <code>ChangeCidrCollection</code> to perform the following actions:</p>
- * 		       <ul>
+ *          <p>Use <code>ChangeCidrCollection</code> to perform the following actions:</p>
+ *          <ul>
  *             <li>
- * 				           <p>
+ *                <p>
  *                   <code>PUT</code>: Create a CIDR block within the specified collection.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>
+ *                <p>
  *                   <code> DELETE_IF_EXISTS</code>: Delete an existing CIDR block from the
  * 					collection.</p>
- * 			         </li>
+ *             </li>
  *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

clients/client-route-53/src/commands/ChangeCidrCollectionCommand.ts

@@ -35,36 +35,36 @@ export interface ChangeResourceRecordSetsCommandOutput extends ChangeResourceRec
  * 				<code>ChangeResourceRecordSets</code> to create a resource record set that routes
  * 			traffic for test.example.com to a web server that has an IP address of
  * 			192.0.2.44.</p>
- * 		       <p>
+ *          <p>
  *             <b>Deleting Resource Record Sets</b>
  *          </p>
- * 		       <p>To delete a resource record set, you must specify all the same values that you
+ *          <p>To delete a resource record set, you must specify all the same values that you
  * 			specified when you created it.</p>
- * 		       <p>
+ *          <p>
  *             <b>Change Batches and Transactional Changes</b>
  *          </p>
- * 		       <p>The request body must include a document with a
+ *          <p>The request body must include a document with a
  * 				<code>ChangeResourceRecordSetsRequest</code> element. The request body contains a
  * 			list of change items, known as a change batch. Change batches are considered
  * 			transactional changes. Route 53 validates the changes in the request and then either
  * 			makes all or none of the changes in the change batch request. This ensures that DNS
  * 			routing isn't adversely affected by partial changes to the resource record sets in a
  * 			hosted zone. </p>
- * 		       <p>For example, suppose a change batch request contains two changes: it deletes the
+ *          <p>For example, suppose a change batch request contains two changes: it deletes the
  * 				<code>CNAME</code> resource record set for www.example.com and creates an alias
  * 			resource record set for www.example.com. If validation for both records succeeds, Route
  * 			53 deletes the first resource record set and creates the second resource record set in a
  * 			single operation. If validation for either the <code>DELETE</code> or the
  * 				<code>CREATE</code> action fails, then the request is canceled, and the original
  * 				<code>CNAME</code> record continues to exist.</p>
- * 		       <note>
- * 			         <p>If you try to delete the same resource record set more than once in a single
+ *          <note>
+ *             <p>If you try to delete the same resource record set more than once in a single
  * 				change batch, Route 53 returns an <code>InvalidChangeBatch</code> error.</p>
- * 		       </note>
- * 		       <p>
+ *          </note>
+ *          <p>
  *             <b>Traffic Flow</b>
  *          </p>
- * 		       <p>To create resource record sets for complex routing configurations, use either the
+ *          <p>To create resource record sets for complex routing configurations, use either the
  * 			traffic flow visual editor in the Route 53 console or the API actions for traffic
  * 			policies and traffic policy instances. Save the configuration as a traffic policy, then
  * 			associate the traffic policy with one or more domain names (such as example.com) or
@@ -73,54 +73,52 @@ export interface ChangeResourceRecordSetsCommandOutput extends ChangeResourceRec
  * 			expected. For more information, see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/traffic-flow.html">Using Traffic Flow to Route
  * 				DNS Traffic</a> in the <i>Amazon Route 53 Developer
  * 			Guide</i>.</p>
- * 		       <p>
+ *          <p>
  *             <b>Create, Delete, and Upsert</b>
  *          </p>
- * 		       <p>Use <code>ChangeResourceRecordsSetsRequest</code> to perform the following
+ *          <p>Use <code>ChangeResourceRecordsSetsRequest</code> to perform the following
  * 			actions:</p>
- * 		       <ul>
+ *          <ul>
  *             <li>
- * 				           <p>
+ *                <p>
  *                   <code>CREATE</code>: Creates a resource record set that has the specified
  * 					values.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>
+ *                <p>
  *                   <code>DELETE</code>: Deletes an existing resource record set that has the
  * 					specified values.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>
+ *                <p>
  *                   <code>UPSERT</code>: If a resource set exists Route 53 updates it with the
  * 					values in the request. </p>
- * 			         </li>
+ *             </li>
  *          </ul>
- * 		       <p>
+ *          <p>
  *             <b>Syntaxes for Creating, Updating, and Deleting Resource Record
  * 				Sets</b>
  *          </p>
- * 		       <p>The syntax for a request depends on the type of resource record set that you want to
+ *          <p>The syntax for a request depends on the type of resource record set that you want to
  * 			create, delete, or update, such as weighted, alias, or failover. The XML elements in
  * 			your request must appear in the order listed in the syntax. </p>
- *
- * 		       <p>For an example for each type of resource record set, see "Examples."</p>
- *
- * 		       <p>Don't refer to the syntax in the "Parameter Syntax" section, which includes
+ *          <p>For an example for each type of resource record set, see "Examples."</p>
+ *          <p>Don't refer to the syntax in the "Parameter Syntax" section, which includes
  * 			all of the elements for every kind of resource record set that you can create, delete,
  * 			or update by using <code>ChangeResourceRecordSets</code>. </p>
- * 		       <p>
+ *          <p>
  *             <b>Change Propagation to Route 53 DNS Servers</b>
  *          </p>
- * 		       <p>When you submit a <code>ChangeResourceRecordSets</code> request, Route 53 propagates
+ *          <p>When you submit a <code>ChangeResourceRecordSets</code> request, Route 53 propagates
  * 			your changes to all of the Route 53 authoritative DNS servers. While your changes are
  * 			propagating, <code>GetChange</code> returns a status of <code>PENDING</code>. When
  * 			propagation is complete, <code>GetChange</code> returns a status of <code>INSYNC</code>.
  * 			Changes generally propagate to all Route 53 name servers within 60 seconds. For more
  * 			information, see <a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_GetChange.html">GetChange</a>.</p>
- * 		       <p>
+ *          <p>
  *             <b>Limits on ChangeResourceRecordSets Requests</b>
  *          </p>
- * 		       <p>For information about the limits on a <code>ChangeResourceRecordSets</code> request,
+ *          <p>For information about the limits on a <code>ChangeResourceRecordSets</code> request,
  * 			see <a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DNSLimitations.html">Limits</a> in the <i>Amazon Route 53 Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

clients/client-route-53/src/commands/ChangeResourceRecordSetsCommand.ts

@@ -30,7 +30,7 @@ export interface ChangeTagsForResourceCommandOutput extends ChangeTagsForResourc
 
 /**
  * <p>Adds, edits, or deletes tags for a health check or a hosted zone.</p>
- * 		       <p>For information about using tags for cost allocation, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Using Cost Allocation
+ *          <p>For information about using tags for cost allocation, see <a href="https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html">Using Cost Allocation
  * 				Tags</a> in the <i>Billing and Cost Management User Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

clients/client-route-53/src/commands/ChangeTagsForResourceCommand.ts

@@ -30,39 +30,39 @@ export interface CreateHealthCheckCommandOutput extends CreateHealthCheckRespons
 
 /**
  * <p>Creates a new health check.</p>
- * 		       <p>For information about adding health checks to resource record sets, see <a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_ResourceRecordSet.html#Route53-Type-ResourceRecordSet-HealthCheckId">HealthCheckId</a> in <a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html">ChangeResourceRecordSets</a>. </p>
- * 		       <p>
+ *          <p>For information about adding health checks to resource record sets, see <a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_ResourceRecordSet.html#Route53-Type-ResourceRecordSet-HealthCheckId">HealthCheckId</a> in <a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_ChangeResourceRecordSets.html">ChangeResourceRecordSets</a>. </p>
+ *          <p>
  *             <b>ELB Load Balancers</b>
  *          </p>
- * 		       <p>If you're registering EC2 instances with an Elastic Load Balancing (ELB) load
+ *          <p>If you're registering EC2 instances with an Elastic Load Balancing (ELB) load
  * 			balancer, do not create Amazon Route 53 health checks for the EC2 instances. When you
  * 			register an EC2 instance with a load balancer, you configure settings for an ELB health
  * 			check, which performs a similar function to a Route 53 health check.</p>
- * 		       <p>
+ *          <p>
  *             <b>Private Hosted Zones</b>
  *          </p>
- * 		       <p>You can associate health checks with failover resource record sets in a private hosted
+ *          <p>You can associate health checks with failover resource record sets in a private hosted
  * 			zone. Note the following:</p>
- * 		       <ul>
+ *          <ul>
  *             <li>
- * 				           <p>Route 53 health checkers are outside the VPC. To check the health of an
+ *                <p>Route 53 health checkers are outside the VPC. To check the health of an
  * 					endpoint within a VPC by IP address, you must assign a public IP address to the
  * 					instance in the VPC.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>You can configure a health checker to check the health of an external resource
+ *                <p>You can configure a health checker to check the health of an external resource
  * 					that the instance relies on, such as a database server.</p>
- * 			         </li>
+ *             </li>
  *             <li>
- * 				           <p>You can create a CloudWatch metric, associate an alarm with the metric, and
+ *                <p>You can create a CloudWatch metric, associate an alarm with the metric, and
  * 					then create a health check that is based on the state of the alarm. For example,
  * 					you might create a CloudWatch metric that checks the status of the Amazon EC2
  * 						<code>StatusCheckFailed</code> metric, add an alarm to the metric, and then
  * 					create a health check that is based on the state of the alarm. For information
  * 					about creating CloudWatch metrics and alarms by using the CloudWatch console,
  * 					see the <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/WhatIsCloudWatch.html">Amazon
  * 						CloudWatch User Guide</a>.</p>
- * 			         </li>
+ *             </li>
  *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.