@aws-sdk/client-route-53 3.36.0 → 3.36.1

package/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [3.36.1](https://github.com/aws/aws-sdk-js-v3/compare/v3.36.0...v3.36.1) (2021-10-12)
+
+
+### Bug Fixes
+
+* **clients:** emitDeclarationOnly in tsconfig.types.json ([#2893](https://github.com/aws/aws-sdk-js-v3/issues/2893)) ([6dc3d56](https://github.com/aws/aws-sdk-js-v3/commit/6dc3d56c20809c90cbdc4dd48627eeebc64af99d))
+
+
+
+
+
 # [3.36.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.35.0...v3.36.0) (2021-10-08)
 
 

package/dist-cjs/Route53.js

@@ -66,9 +66,6 @@ const UpdateHostedZoneCommentCommand_1 = require("./commands/UpdateHostedZoneCom
 const UpdateTrafficPolicyCommentCommand_1 = require("./commands/UpdateTrafficPolicyCommentCommand");
 const UpdateTrafficPolicyInstanceCommand_1 = require("./commands/UpdateTrafficPolicyInstanceCommand");
 const Route53Client_1 = require("./Route53Client");
-/**
- * <p>Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.</p>
- */
 class Route53 extends Route53Client_1.Route53Client {
     activateKeySigningKey(args, optionsOrCb, cb) {
         const command = new ActivateKeySigningKeyCommand_1.ActivateKeySigningKeyCommand(args);

package/dist-cjs/Route53Client.js

@@ -10,9 +10,6 @@ const middleware_signing_1 = require("@aws-sdk/middleware-signing");
 const middleware_user_agent_1 = require("@aws-sdk/middleware-user-agent");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const runtimeConfig_1 = require("./runtimeConfig");
-/**
- * <p>Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.</p>
- */
 class Route53Client extends smithy_client_1.Client {
     constructor(configuration) {
         const _config_0 = runtimeConfig_1.getRuntimeConfig(configuration);
@@ -31,11 +28,6 @@ class Route53Client extends smithy_client_1.Client {
         this.middlewareStack.use(middleware_signing_1.getAwsAuthPlugin(this.config));
         this.middlewareStack.use(middleware_user_agent_1.getUserAgentPlugin(this.config));
     }
-    /**
-     * Destroy underlying resources, like sockets. It's usually not necessary to do this.
-     * However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed.
-     * Otherwise, sockets might stay open for quite a long time before the server terminates them.
-     */
     destroy() {
         super.destroy();
     }

package/dist-cjs/commands/ActivateKeySigningKeyCommand.js

@@ -6,36 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Activates a key-signing key (KSK) so that it can be used for signing by DNSSEC. This operation changes the
- * 			KSK status to <code>ACTIVE</code>.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, ActivateKeySigningKeyCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, ActivateKeySigningKeyCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new ActivateKeySigningKeyCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link ActivateKeySigningKeyCommandInput} for command's `input` shape.
- * @see {@link ActivateKeySigningKeyCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class ActivateKeySigningKeyCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getIdNormalizerPlugin(configuration));

package/dist-cjs/commands/AssociateVPCWithHostedZoneCommand.js

@@ -6,45 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <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 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 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>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, AssociateVPCWithHostedZoneCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, AssociateVPCWithHostedZoneCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new AssociateVPCWithHostedZoneCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link AssociateVPCWithHostedZoneCommandInput} for command's `input` shape.
- * @see {@link AssociateVPCWithHostedZoneCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class AssociateVPCWithHostedZoneCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getIdNormalizerPlugin(configuration));

package/dist-cjs/commands/ChangeResourceRecordSetsCommand.js

@@ -6,116 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Creates, changes, or deletes a resource record set, which contains authoritative DNS information for a specified
- * 			domain name or subdomain name. For example, you can use <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>
- *             <b>Deleting Resource Record Sets</b>
- *          </p>
- * 		       <p>To delete a resource record set, you must specify all the same values that you specified when you created it.</p>
- *
- * 		       <p>
- *             <b>Change Batches and Transactional Changes</b>
- *          </p>
- * 		       <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 <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 change batch, Route 53 returns an <code>InvalidChangeBatch</code> error.</p>
- * 		       </note>
- *
- * 		       <p>
- *             <b>Traffic Flow</b>
- *          </p>
- * 		       <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 subdomain names (such as www.example.com),
- * 			in the same hosted zone or in multiple hosted zones. You can roll back the updates if the new configuration isn't performing
- * 			as 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>
- *             <b>Create, Delete, and Upsert</b>
- *          </p>
- * 		       <p>Use <code>ChangeResourceRecordsSetsRequest</code> to perform the following actions:</p>
- * 			      <ul>
- *             <li>
- * 					          <p>
- *                   <code>CREATE</code>: Creates a resource record set that has the specified values.</p>
- * 				        </li>
- *             <li>
- * 					          <p>
- *                   <code>DELETE</code>: Deletes an existing resource record set that has the specified values.</p>
- * 				        </li>
- *             <li>
- * 					          <p>
- *                   <code>UPSERT</code>: If a resource record set does not already exist, Amazon Web Services creates it.
- * 						If a resource set does exist, Route 53 updates it with the values in the request. </p>
- * 				        </li>
- *          </ul>
- *
- * 		       <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 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 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>
- *             <b>Change Propagation to Route 53 DNS Servers</b>
- *          </p>
- * 		       <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>
- *             <b>Limits on ChangeResourceRecordSets Requests</b>
- *          </p>
- * 		       <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.
- * ```javascript
- * import { Route53Client, ChangeResourceRecordSetsCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, ChangeResourceRecordSetsCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new ChangeResourceRecordSetsCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link ChangeResourceRecordSetsCommandInput} for command's `input` shape.
- * @see {@link ChangeResourceRecordSetsCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class ChangeResourceRecordSetsCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getChangeResourceRecordSetsPlugin(configuration));

package/dist-cjs/commands/ChangeTagsForResourceCommand.js

@@ -5,38 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <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 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.
- * ```javascript
- * import { Route53Client, ChangeTagsForResourceCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, ChangeTagsForResourceCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new ChangeTagsForResourceCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link ChangeTagsForResourceCommandInput} for command's `input` shape.
- * @see {@link ChangeTagsForResourceCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class ChangeTagsForResourceCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/CreateHealthCheckCommand.js

@@ -5,68 +5,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <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>
- *             <b>ELB Load Balancers</b>
- *          </p>
- * 		       <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>
- *             <b>Private Hosted Zones</b>
- *          </p>
- * 		       <p>You can associate health checks with failover resource record sets in a private hosted zone. Note the following:</p>
- * 		       <ul>
- *             <li>
- * 				           <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>
- * 				           <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>
- * 				           <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>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, CreateHealthCheckCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, CreateHealthCheckCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new CreateHealthCheckCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateHealthCheckCommandInput} for command's `input` shape.
- * @see {@link CreateHealthCheckCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateHealthCheckCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         const stack = clientStack.concat(this.middlewareStack);

package/dist-cjs/commands/CreateHostedZoneCommand.js

@@ -6,67 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Creates a new public or private hosted zone. You create records in a public hosted zone to define how you want to route traffic
- * 			on the internet for a domain, such as example.com, and its subdomains (apex.example.com, acme.example.com). You create records in a
- * 			private hosted zone to define how you want to route traffic for a domain and its subdomains within one or more
- * 			Amazon Virtual Private Clouds (Amazon VPCs). </p>
- * 		       <important>
- * 			         <p>You can't convert a public hosted zone to a private hosted zone or vice versa. Instead, you must create a new hosted zone
- * 				with the same name and create new resource record sets.</p>
- * 		       </important>
- * 		       <p>For more information about charges for hosted zones, see <a href="http://aws.amazon.com/route53/pricing/">Amazon Route 53 Pricing</a>.</p>
- * 		       <p>Note the following:</p>
- * 		       <ul>
- *             <li>
- * 				           <p>You can't create a hosted zone for a top-level domain (TLD) such as .com.</p>
- * 			         </li>
- *             <li>
- * 				           <p>For public hosted zones, Route 53 automatically creates a default SOA record and four NS records for the zone.
- * 					For more information about SOA and NS records, see
- * 					<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/SOA-NSrecords.html">NS and SOA Records that Route 53 Creates for a Hosted Zone</a> in the
- * 					<i>Amazon Route 53 Developer Guide</i>.</p>
- * 				           <p>If you want to use the same name servers for multiple public hosted zones, you can optionally associate a reusable delegation set
- * 					with the hosted zone. See the <code>DelegationSetId</code> element.</p>
- * 			         </li>
- *             <li>
- * 				           <p>If your domain is registered with a registrar other than Route 53, you must update the name servers with your registrar to make
- * 					Route 53 the DNS service for the domain. For more information, see
- * 					<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/MigratingDNS.html">Migrating DNS Service for an Existing Domain to Amazon Route 53</a> in the
- * 					<i>Amazon Route 53 Developer Guide</i>. </p>
- * 			         </li>
- *          </ul>
- * 		       <p>When you submit a <code>CreateHostedZone</code> request, the initial status of the hosted zone is <code>PENDING</code>.
- * 			For public hosted zones, this means that the NS and SOA records are not yet available on all Route 53 DNS servers. When the
- * 			NS and SOA records are available, the status of the zone changes to <code>INSYNC</code>.</p>
- * 		       <p>The <code>CreateHostedZone</code> request requires the caller to have an <code>ec2:DescribeVpcs</code> permission.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, CreateHostedZoneCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, CreateHostedZoneCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new CreateHostedZoneCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateHostedZoneCommandInput} for command's `input` shape.
- * @see {@link CreateHostedZoneCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateHostedZoneCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getIdNormalizerPlugin(configuration));

package/dist-cjs/commands/CreateKeySigningKeyCommand.js

@@ -6,35 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Creates a new key-signing key (KSK) associated with a hosted zone. You can only have two KSKs per hosted zone.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, CreateKeySigningKeyCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, CreateKeySigningKeyCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new CreateKeySigningKeyCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateKeySigningKeyCommandInput} for command's `input` shape.
- * @see {@link CreateKeySigningKeyCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateKeySigningKeyCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getIdNormalizerPlugin(configuration));

package/dist-cjs/commands/CreateQueryLoggingConfigCommand.js

@@ -6,151 +6,11 @@ const middleware_serde_1 = require("@aws-sdk/middleware-serde");
 const smithy_client_1 = require("@aws-sdk/smithy-client");
 const models_0_1 = require("../models/models_0");
 const Aws_restXml_1 = require("../protocols/Aws_restXml");
-/**
- * <p>Creates a configuration for DNS query logging. After you create a query logging configuration, Amazon Route 53 begins to publish
- * 			log data to an Amazon CloudWatch Logs log group.</p>
- * 		       <p>DNS query logs contain information about the queries that Route 53 receives for a specified public hosted zone, such as the following:</p>
- * 		       <ul>
- *             <li>
- *                <p>Route 53 edge location that responded to the DNS query</p>
- *             </li>
- *             <li>
- *                <p>Domain or subdomain that was requested</p>
- *             </li>
- *             <li>
- *                <p>DNS record type, such as A or AAAA</p>
- *             </li>
- *             <li>
- *                <p>DNS response code, such as <code>NoError</code> or <code>ServFail</code>
- *                </p>
- *             </li>
- *          </ul>
- *
- * 		       <dl>
- *             <dt>Log Group and Resource Policy</dt>
- *             <dd>
- *                <p>Before you create a query logging configuration, perform the following operations.</p>
- * 					          <note>
- *                   <p>If you create a query logging configuration using the Route 53 console, Route 53 performs these operations automatically.</p>
- *                </note>
- * 					          <ol>
- *                   <li>
- *                      <p>Create a CloudWatch Logs log group, and make note of the ARN, which you specify when you create a
- * 							query logging configuration. Note the following:</p>
- * 							              <ul>
- *                         <li>
- *                            <p>You must create the log group in the us-east-1 region.</p>
- *                         </li>
- *                         <li>
- *                            <p>You must use the same Amazon Web Services account to create the log group and the hosted zone that you want to
- * 									configure query logging for.</p>
- *                         </li>
- *                         <li>
- *                            <p>When you create log groups for query logging, we recommend that you use a consistent prefix, for example:</p>
- * 									                  <p>
- *                               <code>/aws/route53/<i>hosted zone name</i>
- *                               </code>
- *                            </p>
- * 									                  <p>In the next step, you'll create a resource policy, which controls access to one or more log groups and the associated
- * 										Amazon Web Services resources, such as Route 53 hosted zones. There's a limit on the number of resource policies that you can create, so
- * 										we recommend that you use a consistent prefix so you can use the same resource policy for all the log groups that you create
- * 										for query logging.</p>
- * 								                </li>
- *                      </ul>
- * 						            </li>
- *                   <li>
- *                      <p>Create a CloudWatch Logs resource policy, and give it the permissions that Route 53 needs to create log streams and to
- * 							send query logs to log streams. For the value of <code>Resource</code>, specify the ARN for the log group that you created
- * 							in the previous step. To use the same resource policy for all the CloudWatch Logs log groups that you created for query logging configurations,
- * 							replace the hosted zone name with <code>*</code>, for example:</p>
- * 							              <p>
- *                         <code>arn:aws:logs:us-east-1:123412341234:log-group:/aws/route53/*</code>
- *                      </p>
- * 							              <note>
- *                         <p>You can't use the CloudWatch console to create or edit a resource policy. You must use the CloudWatch API, one of the Amazon Web Services SDKs,
- * 								or the CLI.</p>
- *                      </note>
- * 						            </li>
- *                </ol>
- * 				        </dd>
- *             <dt>Log Streams and Edge Locations</dt>
- *             <dd>
- *                <p>When Route 53 finishes creating the configuration for DNS query logging, it does the following:</p>
- * 					          <ul>
- *                   <li>
- *                      <p>Creates a log stream for an edge location the first time that the edge location responds to DNS queries for the
- * 							specified hosted zone. That log stream is used to log all queries that Route 53 responds to for that edge location.</p>
- *                   </li>
- *                   <li>
- *                      <p>Begins to send query logs to the applicable log stream.</p>
- *                   </li>
- *                </ul>
- * 					          <p>The name of each log stream is in the following format:</p>
- * 					          <p>
- *                   <code>
- *                      <i>hosted zone ID</i>/<i>edge location code</i>
- *                   </code>
- *                </p>
- * 					          <p>The edge location code is a three-letter code and an arbitrarily assigned number, for example, DFW3. The three-letter code
- * 						typically corresponds with the International Air Transport Association airport code for an airport near the edge location.
- * 						(These abbreviations might change in the future.) For a list of edge locations, see "The Route 53 Global Network" on the
- * 						<a href="http://aws.amazon.com/route53/details/">Route 53 Product Details</a> page.</p>
- * 				        </dd>
- *             <dt>Queries That Are Logged</dt>
- *             <dd>
- *                <p>Query logs contain only the queries that DNS resolvers forward to Route 53. If a DNS resolver has already cached
- * 					the response to a query (such as the IP address for a load balancer for example.com), the resolver will continue to return
- * 					the cached response. It doesn't forward another query to Route 53 until the TTL for the corresponding resource record set expires.
- * 					Depending on how many DNS queries are submitted for a resource record set, and depending on the TTL for that resource record set,
- * 					query logs might contain information about only one query out of every several thousand queries that are submitted to DNS.
- * 					For more information about how DNS works, see
- * 					<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html">Routing Internet Traffic to Your Website or Web Application</a>
- * 					in the <i>Amazon Route 53 Developer Guide</i>.</p>
- * 				        </dd>
- *             <dt>Log File Format</dt>
- *             <dd>
- *                <p>For a list of the values in each query log and the format of each value, see
- * 					<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/query-logs.html">Logging DNS Queries</a> in the
- * 					<i>Amazon Route 53 Developer Guide</i>.</p>
- * 				        </dd>
- *             <dt>Pricing</dt>
- *             <dd>
- *                <p>For information about charges for query logs, see
- * 					<a href="http://aws.amazon.com/cloudwatch/pricing/">Amazon CloudWatch Pricing</a>.</p>
- *             </dd>
- *             <dt>How to Stop Logging</dt>
- *             <dd>
- *                <p>If you want Route 53 to stop sending query logs to CloudWatch Logs, delete the query logging configuration. For more information, see
- * 					<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_DeleteQueryLoggingConfig.html">DeleteQueryLoggingConfig</a>.</p>
- * 				        </dd>
- *          </dl>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { Route53Client, CreateQueryLoggingConfigCommand } from "@aws-sdk/client-route-53"; // ES Modules import
- * // const { Route53Client, CreateQueryLoggingConfigCommand } = require("@aws-sdk/client-route-53"); // CommonJS import
- * const client = new Route53Client(config);
- * const command = new CreateQueryLoggingConfigCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateQueryLoggingConfigCommandInput} for command's `input` shape.
- * @see {@link CreateQueryLoggingConfigCommandOutput} for command's `response` shape.
- * @see {@link Route53ClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateQueryLoggingConfigCommand extends smithy_client_1.Command {
-    // Start section: command_properties
-    // End section: command_properties
     constructor(input) {
-        // Start section: command_constructor
         super();
         this.input = input;
-        // End section: command_constructor
     }
-    /**
-     * @internal
-     */
     resolveMiddleware(clientStack, configuration, options) {
         this.middlewareStack.use(middleware_serde_1.getSerdePlugin(configuration, this.serialize, this.deserialize));
         this.middlewareStack.use(middleware_sdk_route53_1.getIdNormalizerPlugin(configuration));