@aws-sdk/client-route53resolver 3.281.0 → 3.287.0

package/dist-es/protocols/Aws_json1_1.js

@@ -1787,6 +1787,9 @@ const deserializeAws_json1_1GetResolverConfigCommandError = async (output, conte
         case "ThrottlingException":
         case "com.amazonaws.route53resolver#ThrottlingException":
             throw await deserializeAws_json1_1ThrottlingExceptionResponse(parsedOutput, context);
+        case "ValidationException":
+        case "com.amazonaws.route53resolver#ValidationException":
+            throw await deserializeAws_json1_1ValidationExceptionResponse(parsedOutput, context);
         default:
             const parsedBody = parsedOutput.body;
             throwDefaultError({
@@ -2132,6 +2135,9 @@ const deserializeAws_json1_1GetResolverRulePolicyCommandError = async (output, c
     };
     const errorCode = loadRestJsonErrorCode(output, parsedOutput.body);
     switch (errorCode) {
+        case "AccessDeniedException":
+        case "com.amazonaws.route53resolver#AccessDeniedException":
+            throw await deserializeAws_json1_1AccessDeniedExceptionResponse(parsedOutput, context);
         case "InternalServiceErrorException":
         case "com.amazonaws.route53resolver#InternalServiceErrorException":
             throw await deserializeAws_json1_1InternalServiceErrorExceptionResponse(parsedOutput, context);
@@ -2498,6 +2504,9 @@ const deserializeAws_json1_1ListResolverConfigsCommandError = async (output, con
         case "ThrottlingException":
         case "com.amazonaws.route53resolver#ThrottlingException":
             throw await deserializeAws_json1_1ThrottlingExceptionResponse(parsedOutput, context);
+        case "ValidationException":
+        case "com.amazonaws.route53resolver#ValidationException":
+            throw await deserializeAws_json1_1ValidationExceptionResponse(parsedOutput, context);
         default:
             const parsedBody = parsedOutput.body;
             throwDefaultError({
@@ -2993,6 +3002,9 @@ const deserializeAws_json1_1PutResolverRulePolicyCommandError = async (output, c
     };
     const errorCode = loadRestJsonErrorCode(output, parsedOutput.body);
     switch (errorCode) {
+        case "AccessDeniedException":
+        case "com.amazonaws.route53resolver#AccessDeniedException":
+            throw await deserializeAws_json1_1AccessDeniedExceptionResponse(parsedOutput, context);
         case "InternalServiceErrorException":
         case "com.amazonaws.route53resolver#InternalServiceErrorException":
             throw await deserializeAws_json1_1InternalServiceErrorExceptionResponse(parsedOutput, context);
@@ -3347,6 +3359,9 @@ const deserializeAws_json1_1UpdateResolverConfigCommandError = async (output, co
         case "ThrottlingException":
         case "com.amazonaws.route53resolver#ThrottlingException":
             throw await deserializeAws_json1_1ThrottlingExceptionResponse(parsedOutput, context);
+        case "ValidationException":
+        case "com.amazonaws.route53resolver#ValidationException":
+            throw await deserializeAws_json1_1ValidationExceptionResponse(parsedOutput, context);
         default:
             const parsedBody = parsedOutput.body;
             throwDefaultError({
@@ -3711,6 +3726,7 @@ const serializeAws_json1_1CreateResolverEndpointRequest = (input, context) => {
             IpAddresses: serializeAws_json1_1IpAddressesRequest(input.IpAddresses, context),
         }),
         ...(input.Name != null && { Name: input.Name }),
+        ...(input.ResolverEndpointType != null && { ResolverEndpointType: input.ResolverEndpointType }),
         ...(input.SecurityGroupIds != null && {
             SecurityGroupIds: serializeAws_json1_1SecurityGroupIds(input.SecurityGroupIds, context),
         }),
@@ -3910,6 +3926,7 @@ const serializeAws_json1_1IpAddressesRequest = (input, context) => {
 const serializeAws_json1_1IpAddressRequest = (input, context) => {
     return {
         ...(input.Ip != null && { Ip: input.Ip }),
+        ...(input.Ipv6 != null && { Ipv6: input.Ipv6 }),
         ...(input.SubnetId != null && { SubnetId: input.SubnetId }),
     };
 };
@@ -3917,6 +3934,7 @@ const serializeAws_json1_1IpAddressUpdate = (input, context) => {
     return {
         ...(input.Ip != null && { Ip: input.Ip }),
         ...(input.IpId != null && { IpId: input.IpId }),
+        ...(input.Ipv6 != null && { Ipv6: input.Ipv6 }),
         ...(input.SubnetId != null && { SubnetId: input.SubnetId }),
     };
 };
@@ -4093,6 +4111,7 @@ const serializeAws_json1_1TagResourceRequest = (input, context) => {
 const serializeAws_json1_1TargetAddress = (input, context) => {
     return {
         ...(input.Ip != null && { Ip: input.Ip }),
+        ...(input.Ipv6 != null && { Ipv6: input.Ipv6 }),
         ...(input.Port != null && { Port: input.Port }),
     };
 };
@@ -4145,6 +4164,19 @@ const serializeAws_json1_1UpdateFirewallRuleRequest = (input, context) => {
         ...(input.Priority != null && { Priority: input.Priority }),
     };
 };
+const serializeAws_json1_1UpdateIpAddress = (input, context) => {
+    return {
+        ...(input.IpId != null && { IpId: input.IpId }),
+        ...(input.Ipv6 != null && { Ipv6: input.Ipv6 }),
+    };
+};
+const serializeAws_json1_1UpdateIpAddresses = (input, context) => {
+    return input
+        .filter((e) => e != null)
+        .map((entry) => {
+        return serializeAws_json1_1UpdateIpAddress(entry, context);
+    });
+};
 const serializeAws_json1_1UpdateResolverConfigRequest = (input, context) => {
     return {
         ...(input.AutodefinedReverseFlag != null && { AutodefinedReverseFlag: input.AutodefinedReverseFlag }),
@@ -4161,6 +4193,10 @@ const serializeAws_json1_1UpdateResolverEndpointRequest = (input, context) => {
     return {
         ...(input.Name != null && { Name: input.Name }),
         ...(input.ResolverEndpointId != null && { ResolverEndpointId: input.ResolverEndpointId }),
+        ...(input.ResolverEndpointType != null && { ResolverEndpointType: input.ResolverEndpointType }),
+        ...(input.UpdateIpAddresses != null && {
+            UpdateIpAddresses: serializeAws_json1_1UpdateIpAddresses(input.UpdateIpAddresses, context),
+        }),
     };
 };
 const serializeAws_json1_1UpdateResolverRuleRequest = (input, context) => {
@@ -4607,6 +4643,7 @@ const deserializeAws_json1_1IpAddressResponse = (output, context) => {
         CreationTime: __expectString(output.CreationTime),
         Ip: __expectString(output.Ip),
         IpId: __expectString(output.IpId),
+        Ipv6: __expectString(output.Ipv6),
         ModificationTime: __expectString(output.ModificationTime),
         Status: __expectString(output.Status),
         StatusMessage: __expectString(output.StatusMessage),
@@ -4801,6 +4838,7 @@ const deserializeAws_json1_1ResolverEndpoint = (output, context) => {
         IpAddressCount: __expectInt32(output.IpAddressCount),
         ModificationTime: __expectString(output.ModificationTime),
         Name: __expectString(output.Name),
+        ResolverEndpointType: __expectString(output.ResolverEndpointType),
         SecurityGroupIds: output.SecurityGroupIds != null
             ? deserializeAws_json1_1SecurityGroupIds(output.SecurityGroupIds, context)
             : undefined,
@@ -4974,6 +5012,7 @@ const deserializeAws_json1_1TagResourceResponse = (output, context) => {
 const deserializeAws_json1_1TargetAddress = (output, context) => {
     return {
         Ip: __expectString(output.Ip),
+        Ipv6: __expectString(output.Ipv6),
         Port: __expectInt32(output.Port),
     };
 };

package/dist-types/Route53Resolver.d.ts

@@ -69,32 +69,26 @@ import { Route53ResolverClient } from "./Route53ResolverClient";
  * 			such as domain names for EC2 instances or Elastic Load Balancing load balancers.
  * 			Resolver performs recursive lookups against public name servers for all other domain
  * 			names.</p>
- *
- * 		       <p>You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:</p>
- *
- * 		       <p>
+ *          <p>You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:</p>
+ *          <p>
  *             <b>Forward DNS queries from resolvers on your network to Route 53 Resolver</b>
  *          </p>
- *
- * 		       <p>DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers
+ *          <p>DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers
  * 			to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone.
  * 			For more information, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-network-to-vpc">How DNS Resolvers
  * 			on Your Network Forward DNS Queries to Route 53 Resolver</a> in the <i>Amazon Route 53 Developer Guide</i>.</p>
- *
- * 		       <p>
+ *          <p>
  *             <b>Conditionally forward queries from a VPC to resolvers on your network</b>
  *          </p>
- *
- * 		       <p>You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network.
+ *          <p>You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network.
  * 			To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward
  * 			(such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to.
  * 			If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match
  * 			(acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-vpc-to-network">How Route 53 Resolver
  * 			Forwards DNS Queries from Your VPCs to Your Network</a> in the <i>Amazon Route 53 Developer Guide</i>.</p>
- *
- * 		       <p>Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose
+ *          <p>Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose
  * 			whether to forward queries from your VPCs to your network (outbound queries), from your
  * 			network to your VPCs (inbound queries), or both.</p>
  */
@@ -108,7 +102,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     /**
      * <p>Adds IP addresses to an inbound or an outbound Resolver endpoint. If you want to add more than one IP address,
      * 			submit one <code>AssociateResolverEndpointIpAddress</code> request for each IP address.</p>
-     * 		       <p>To remove an IP address from an endpoint, see
+     *          <p>To remove an IP address from an endpoint, see
      * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverEndpointIpAddress.html">DisassociateResolverEndpointIpAddress</a>.
      * 		</p>
      */
@@ -119,12 +113,10 @@ export declare class Route53Resolver extends Route53ResolverClient {
      * <p>Associates an Amazon VPC with a specified query logging configuration. Route 53 Resolver logs DNS queries that originate in all of the Amazon VPCs
      * 			that are associated with a specified query logging configuration. To associate more than one VPC with a configuration, submit one <code>AssociateResolverQueryLogConfig</code>
      * 			request for each VPC.</p>
-     *
-     * 		       <note>
+     *          <note>
      *             <p>The VPCs that you associate with a query logging configuration must be in the same Region as the configuration.</p>
      *          </note>
-     *
-     * 		       <p>To remove a VPC from a query logging configuration, see
+     *          <p>To remove a VPC from a query logging configuration, see
      * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverQueryLogConfig.html">DisassociateResolverQueryLogConfig</a>.
      * 			</p>
      */
@@ -161,7 +153,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     createFirewallRuleGroup(args: CreateFirewallRuleGroupCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: CreateFirewallRuleGroupCommandOutput) => void): void;
     /**
      * <p>Creates a Resolver endpoint. There are two types of Resolver endpoints, inbound and outbound:</p>
-     * 		       <ul>
+     *          <ul>
      *             <li>
      *                <p>An <i>inbound Resolver endpoint</i> forwards DNS queries to the DNS service for a VPC
      * 				from your network.</p>
@@ -178,11 +170,9 @@ export declare class Route53Resolver extends Route53ResolverClient {
     /**
      * <p>Creates a Resolver query logging configuration, which defines where you want Resolver to save DNS query logs that originate in your VPCs.
      * 			Resolver can log queries only for VPCs that are in the same Region as the query logging configuration.</p>
-     *
-     * 		       <p>To specify which VPCs you want to log queries for, you use <code>AssociateResolverQueryLogConfig</code>. For more information, see
+     *          <p>To specify which VPCs you want to log queries for, you use <code>AssociateResolverQueryLogConfig</code>. For more information, see
      * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_AssociateResolverQueryLogConfig.html">AssociateResolverQueryLogConfig</a>. </p>
-     *
-     * 		       <p>You can optionally use Resource Access Manager (RAM) to share a query logging configuration with other Amazon Web Services accounts. The other accounts
+     *          <p>You can optionally use Resource Access Manager (RAM) to share a query logging configuration with other Amazon Web Services accounts. The other accounts
      * 			can then associate VPCs with the configuration. The query logs that Resolver creates for a configuration include all DNS queries that originate in all
      * 			VPCs that are associated with the configuration.</p>
      */
@@ -217,7 +207,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     /**
      * <p>Deletes a Resolver endpoint. The effect of deleting a Resolver endpoint depends on whether it's an inbound or an outbound
      * 			Resolver endpoint:</p>
-     * 		       <ul>
+     *          <ul>
      *             <li>
      *                <p>
      *                   <b>Inbound</b>: DNS queries from your network are no longer routed
@@ -236,11 +226,9 @@ export declare class Route53Resolver extends Route53ResolverClient {
      * <p>Deletes a query logging configuration. When you delete a configuration, Resolver stops logging DNS queries for all of the Amazon VPCs that are
      * 			associated with the configuration. This also applies if the query logging configuration is shared with other Amazon Web Services accounts, and
      * 			the other accounts have associated VPCs with the shared configuration.</p>
-     *
-     * 		       <p>Before you can delete a query logging configuration, you must first disassociate all VPCs from the configuration. See
+     *          <p>Before you can delete a query logging configuration, you must first disassociate all VPCs from the configuration. See
      * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverQueryLogConfig.html">DisassociateResolverQueryLogConfig</a>.</p>
-     *
-     * 		       <p>If you used Resource Access Manager (RAM) to share a query logging configuration with other accounts, you must stop sharing
+     *          <p>If you used Resource Access Manager (RAM) to share a query logging configuration with other accounts, you must stop sharing
      * 			the configuration before you can delete a configuration. The accounts that you shared the configuration with can first disassociate VPCs
      * 			that they associated with the configuration, but that's not necessary. If you stop sharing the configuration, those VPCs are automatically
      * 			disassociated from the configuration.</p>
@@ -265,7 +253,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     /**
      * <p>Removes IP addresses from an inbound or an outbound Resolver endpoint. If you want to remove more than one IP address,
      * 			submit one <code>DisassociateResolverEndpointIpAddress</code> request for each IP address.</p>
-     * 		       <p>To add an IP address to an endpoint, see
+     *          <p>To add an IP address to an endpoint, see
      * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_AssociateResolverEndpointIpAddress.html">AssociateResolverEndpointIpAddress</a>.
      * 		</p>
      */
@@ -274,13 +262,12 @@ export declare class Route53Resolver extends Route53ResolverClient {
     disassociateResolverEndpointIpAddress(args: DisassociateResolverEndpointIpAddressCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DisassociateResolverEndpointIpAddressCommandOutput) => void): void;
     /**
      * <p>Disassociates a VPC from a query logging configuration.</p>
-     *
-     * 		       <note>
-     * 			         <p>Before you can delete a query logging configuration, you must first disassociate all VPCs
+     *          <note>
+     *             <p>Before you can delete a query logging configuration, you must first disassociate all VPCs
      * 				from the configuration. If you used Resource Access Manager (RAM) to share a
      * 				query logging configuration with other accounts, VPCs can be disassociated from the
      * 				configuration in the following ways:</p>
-     * 			         <ul>
+     *             <ul>
      *                <li>
      *                   <p>The accounts that you shared the configuration with can disassociate VPCs from the configuration.</p>
      *                </li>
@@ -288,17 +275,17 @@ export declare class Route53Resolver extends Route53ResolverClient {
      *                   <p>You can stop sharing the configuration.</p>
      *                </li>
      *             </ul>
-     * 		       </note>
+     *          </note>
      */
     disassociateResolverQueryLogConfig(args: DisassociateResolverQueryLogConfigCommandInput, options?: __HttpHandlerOptions): Promise<DisassociateResolverQueryLogConfigCommandOutput>;
     disassociateResolverQueryLogConfig(args: DisassociateResolverQueryLogConfigCommandInput, cb: (err: any, data?: DisassociateResolverQueryLogConfigCommandOutput) => void): void;
     disassociateResolverQueryLogConfig(args: DisassociateResolverQueryLogConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: DisassociateResolverQueryLogConfigCommandOutput) => void): void;
     /**
      * <p>Removes the association between a specified Resolver rule and a specified VPC.</p>
-     * 		       <important>
-     * 			         <p>If you disassociate a Resolver rule from a VPC, Resolver stops forwarding DNS queries for the
+     *          <important>
+     *             <p>If you disassociate a Resolver rule from a VPC, Resolver stops forwarding DNS queries for the
      * 				domain name that you specified in the Resolver rule. </p>
-     * 		       </important>
+     *          </important>
      */
     disassociateResolverRule(args: DisassociateResolverRuleCommandInput, options?: __HttpHandlerOptions): Promise<DisassociateResolverRuleCommandOutput>;
     disassociateResolverRule(args: DisassociateResolverRuleCommandInput, cb: (err: any, data?: DisassociateResolverRuleCommandOutput) => void): void;
@@ -336,7 +323,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     getFirewallRuleGroupPolicy(args: GetFirewallRuleGroupPolicyCommandInput, cb: (err: any, data?: GetFirewallRuleGroupPolicyCommandOutput) => void): void;
     getFirewallRuleGroupPolicy(args: GetFirewallRuleGroupPolicyCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: GetFirewallRuleGroupPolicyCommandOutput) => void): void;
     /**
-     * <p>Retrieves the behavior configuration of Route 53 Resolver behavior for a single VPC from
+     * <p>Retrieves the behavior configuration of Route 53 Resolver behavior for a single VPC from
      * 				Amazon Virtual Private Cloud.</p>
      */
     getResolverConfig(args: GetResolverConfigCommandInput, options?: __HttpHandlerOptions): Promise<GetResolverConfigCommandOutput>;
@@ -403,16 +390,16 @@ export declare class Route53Resolver extends Route53ResolverClient {
      * 	requirements: </p>
      *          <ul>
      *             <li>
-     *       	        <p>It can optionally start with <code>*</code> (asterisk).</p>
-     *       	     </li>
+     *                <p>It can optionally start with <code>*</code> (asterisk).</p>
+     *             </li>
      *             <li>
-     *       	        <p>With the exception of the optional starting asterisk, it must only contain
+     *                <p>With the exception of the optional starting asterisk, it must only contain
      *       	   the following characters: <code>A-Z</code>, <code>a-z</code>,
      *       	   <code>0-9</code>, <code>-</code> (hyphen).</p>
-     *       	     </li>
+     *             </li>
      *             <li>
-     *       	        <p>It must be from 1-255 characters in length. </p>
-     *       	     </li>
+     *                <p>It must be from 1-255 characters in length. </p>
+     *             </li>
      *          </ul>
      */
     importFirewallDomains(args: ImportFirewallDomainsCommandInput, options?: __HttpHandlerOptions): Promise<ImportFirewallDomainsCommandOutput>;
@@ -462,7 +449,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     listFirewallRules(args: ListFirewallRulesCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: ListFirewallRulesCommandOutput) => void): void;
     /**
      * <p>Retrieves the Resolver configurations that you have defined.
-     * 			Route 53 Resolver uses the configurations to manage DNS resolution behavior for your VPCs.</p>
+     * 			Route 53 Resolver uses the configurations to manage DNS resolution behavior for your VPCs.</p>
      */
     listResolverConfigs(args: ListResolverConfigsCommandInput, options?: __HttpHandlerOptions): Promise<ListResolverConfigsCommandOutput>;
     listResolverConfigs(args: ListResolverConfigsCommandInput, cb: (err: any, data?: ListResolverConfigsCommandOutput) => void): void;
@@ -576,7 +563,7 @@ export declare class Route53Resolver extends Route53ResolverClient {
     updateFirewallRuleGroupAssociation(args: UpdateFirewallRuleGroupAssociationCommandInput, cb: (err: any, data?: UpdateFirewallRuleGroupAssociationCommandOutput) => void): void;
     updateFirewallRuleGroupAssociation(args: UpdateFirewallRuleGroupAssociationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateFirewallRuleGroupAssociationCommandOutput) => void): void;
     /**
-     * <p>Updates the behavior configuration of Route 53 Resolver behavior for a single VPC from
+     * <p>Updates the behavior configuration of Route 53 Resolver behavior for a single VPC from
      * 				Amazon Virtual Private Cloud.</p>
      */
     updateResolverConfig(args: UpdateResolverConfigCommandInput, options?: __HttpHandlerOptions): Promise<UpdateResolverConfigCommandOutput>;
@@ -589,7 +576,8 @@ export declare class Route53Resolver extends Route53ResolverClient {
     updateResolverDnssecConfig(args: UpdateResolverDnssecConfigCommandInput, cb: (err: any, data?: UpdateResolverDnssecConfigCommandOutput) => void): void;
     updateResolverDnssecConfig(args: UpdateResolverDnssecConfigCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: UpdateResolverDnssecConfigCommandOutput) => void): void;
     /**
-     * <p>Updates the name of an inbound or an outbound Resolver endpoint.  </p>
+     * <p>Updates the name, or enpoint type for an inbound or an outbound Resolver endpoint.
+     * 			You can only update between IPV4 and DUALSTACK, IPV6 endpoint type can't be updated to other type. </p>
      */
     updateResolverEndpoint(args: UpdateResolverEndpointCommandInput, options?: __HttpHandlerOptions): Promise<UpdateResolverEndpointCommandOutput>;
     updateResolverEndpoint(args: UpdateResolverEndpointCommandInput, cb: (err: any, data?: UpdateResolverEndpointCommandOutput) => void): void;

package/dist-types/Route53ResolverClient.d.ts

@@ -191,32 +191,26 @@ export interface Route53ResolverClientResolvedConfig extends Route53ResolverClie
  * 			such as domain names for EC2 instances or Elastic Load Balancing load balancers.
  * 			Resolver performs recursive lookups against public name servers for all other domain
  * 			names.</p>
- *
- * 		       <p>You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:</p>
- *
- * 		       <p>
+ *          <p>You can also configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection:</p>
+ *          <p>
  *             <b>Forward DNS queries from resolvers on your network to Route 53 Resolver</b>
  *          </p>
- *
- * 		       <p>DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers
+ *          <p>DNS resolvers on your network can forward DNS queries to Resolver in a specified VPC. This allows your DNS resolvers
  * 			to easily resolve domain names for Amazon Web Services resources such as EC2 instances or records in a Route 53 private hosted zone.
  * 			For more information, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-network-to-vpc">How DNS Resolvers
  * 			on Your Network Forward DNS Queries to Route 53 Resolver</a> in the <i>Amazon Route 53 Developer Guide</i>.</p>
- *
- * 		       <p>
+ *          <p>
  *             <b>Conditionally forward queries from a VPC to resolvers on your network</b>
  *          </p>
- *
- * 		       <p>You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network.
+ *          <p>You can configure Resolver to forward queries that it receives from EC2 instances in your VPCs to DNS resolvers on your network.
  * 			To forward selected queries, you create Resolver rules that specify the domain names for the DNS queries that you want to forward
  * 			(such as example.com), and the IP addresses of the DNS resolvers on your network that you want to forward the queries to.
  * 			If a query matches multiple rules (example.com, acme.example.com), Resolver chooses the rule with the most specific match
  * 			(acme.example.com) and forwards the query to the IP addresses that you specified in that rule. For more information, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-vpc-to-network">How Route 53 Resolver
  * 			Forwards DNS Queries from Your VPCs to Your Network</a> in the <i>Amazon Route 53 Developer Guide</i>.</p>
- *
- * 		       <p>Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose
+ *          <p>Like Amazon VPC, Resolver is Regional. In each Region where you have VPCs, you can choose
  * 			whether to forward queries from your VPCs to your network (outbound queries), from your
  * 			network to your VPCs (inbound queries), or both.</p>
  */

package/dist-types/commands/AssociateResolverEndpointIpAddressCommand.d.ts

@@ -16,7 +16,7 @@ export interface AssociateResolverEndpointIpAddressCommandOutput extends Associa
 /**
  * <p>Adds IP addresses to an inbound or an outbound Resolver endpoint. If you want to add more than one IP address,
  * 			submit one <code>AssociateResolverEndpointIpAddress</code> request for each IP address.</p>
- * 		       <p>To remove an IP address from an endpoint, see
+ *          <p>To remove an IP address from an endpoint, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverEndpointIpAddress.html">DisassociateResolverEndpointIpAddress</a>.
  * 		</p>
  * @example

package/dist-types/commands/AssociateResolverQueryLogConfigCommand.d.ts

@@ -17,12 +17,10 @@ export interface AssociateResolverQueryLogConfigCommandOutput extends AssociateR
  * <p>Associates an Amazon VPC with a specified query logging configuration. Route 53 Resolver logs DNS queries that originate in all of the Amazon VPCs
  * 			that are associated with a specified query logging configuration. To associate more than one VPC with a configuration, submit one <code>AssociateResolverQueryLogConfig</code>
  * 			request for each VPC.</p>
- *
- * 		       <note>
+ *          <note>
  *             <p>The VPCs that you associate with a query logging configuration must be in the same Region as the configuration.</p>
  *          </note>
- *
- * 		       <p>To remove a VPC from a query logging configuration, see
+ *          <p>To remove a VPC from a query logging configuration, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverQueryLogConfig.html">DisassociateResolverQueryLogConfig</a>.
  * 			</p>
  * @example

package/dist-types/commands/CreateResolverEndpointCommand.d.ts

@@ -15,7 +15,7 @@ export interface CreateResolverEndpointCommandOutput extends CreateResolverEndpo
 }
 /**
  * <p>Creates a Resolver endpoint. There are two types of Resolver endpoints, inbound and outbound:</p>
- * 		       <ul>
+ *          <ul>
  *             <li>
  *                <p>An <i>inbound Resolver endpoint</i> forwards DNS queries to the DNS service for a VPC
  * 				from your network.</p>

package/dist-types/commands/CreateResolverQueryLogConfigCommand.d.ts

@@ -16,11 +16,9 @@ export interface CreateResolverQueryLogConfigCommandOutput extends CreateResolve
 /**
  * <p>Creates a Resolver query logging configuration, which defines where you want Resolver to save DNS query logs that originate in your VPCs.
  * 			Resolver can log queries only for VPCs that are in the same Region as the query logging configuration.</p>
- *
- * 		       <p>To specify which VPCs you want to log queries for, you use <code>AssociateResolverQueryLogConfig</code>. For more information, see
+ *          <p>To specify which VPCs you want to log queries for, you use <code>AssociateResolverQueryLogConfig</code>. For more information, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_AssociateResolverQueryLogConfig.html">AssociateResolverQueryLogConfig</a>. </p>
- *
- * 		       <p>You can optionally use Resource Access Manager (RAM) to share a query logging configuration with other Amazon Web Services accounts. The other accounts
+ *          <p>You can optionally use Resource Access Manager (RAM) to share a query logging configuration with other Amazon Web Services accounts. The other accounts
  * 			can then associate VPCs with the configuration. The query logs that Resolver creates for a configuration include all DNS queries that originate in all
  * 			VPCs that are associated with the configuration.</p>
  * @example

package/dist-types/commands/DeleteResolverEndpointCommand.d.ts

@@ -16,7 +16,7 @@ export interface DeleteResolverEndpointCommandOutput extends DeleteResolverEndpo
 /**
  * <p>Deletes a Resolver endpoint. The effect of deleting a Resolver endpoint depends on whether it's an inbound or an outbound
  * 			Resolver endpoint:</p>
- * 		       <ul>
+ *          <ul>
  *             <li>
  *                <p>
  *                   <b>Inbound</b>: DNS queries from your network are no longer routed

package/dist-types/commands/DeleteResolverQueryLogConfigCommand.d.ts

@@ -17,11 +17,9 @@ export interface DeleteResolverQueryLogConfigCommandOutput extends DeleteResolve
  * <p>Deletes a query logging configuration. When you delete a configuration, Resolver stops logging DNS queries for all of the Amazon VPCs that are
  * 			associated with the configuration. This also applies if the query logging configuration is shared with other Amazon Web Services accounts, and
  * 			the other accounts have associated VPCs with the shared configuration.</p>
- *
- * 		       <p>Before you can delete a query logging configuration, you must first disassociate all VPCs from the configuration. See
+ *          <p>Before you can delete a query logging configuration, you must first disassociate all VPCs from the configuration. See
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_DisassociateResolverQueryLogConfig.html">DisassociateResolverQueryLogConfig</a>.</p>
- *
- * 		       <p>If you used Resource Access Manager (RAM) to share a query logging configuration with other accounts, you must stop sharing
+ *          <p>If you used Resource Access Manager (RAM) to share a query logging configuration with other accounts, you must stop sharing
  * 			the configuration before you can delete a configuration. The accounts that you shared the configuration with can first disassociate VPCs
  * 			that they associated with the configuration, but that's not necessary. If you stop sharing the configuration, those VPCs are automatically
  * 			disassociated from the configuration.</p>

package/dist-types/commands/DisassociateResolverEndpointIpAddressCommand.d.ts

@@ -16,7 +16,7 @@ export interface DisassociateResolverEndpointIpAddressCommandOutput extends Disa
 /**
  * <p>Removes IP addresses from an inbound or an outbound Resolver endpoint. If you want to remove more than one IP address,
  * 			submit one <code>DisassociateResolverEndpointIpAddress</code> request for each IP address.</p>
- * 		       <p>To add an IP address to an endpoint, see
+ *          <p>To add an IP address to an endpoint, see
  * 			<a href="https://docs.aws.amazon.com/Route53/latest/APIReference/API_route53resolver_AssociateResolverEndpointIpAddress.html">AssociateResolverEndpointIpAddress</a>.
  * 		</p>
  * @example

package/dist-types/commands/DisassociateResolverQueryLogConfigCommand.d.ts

@@ -15,13 +15,12 @@ export interface DisassociateResolverQueryLogConfigCommandOutput extends Disasso
 }
 /**
  * <p>Disassociates a VPC from a query logging configuration.</p>
- *
- * 		       <note>
- * 			         <p>Before you can delete a query logging configuration, you must first disassociate all VPCs
+ *          <note>
+ *             <p>Before you can delete a query logging configuration, you must first disassociate all VPCs
  * 				from the configuration. If you used Resource Access Manager (RAM) to share a
  * 				query logging configuration with other accounts, VPCs can be disassociated from the
  * 				configuration in the following ways:</p>
- * 			         <ul>
+ *             <ul>
  *                <li>
  *                   <p>The accounts that you shared the configuration with can disassociate VPCs from the configuration.</p>
  *                </li>
@@ -29,7 +28,7 @@ export interface DisassociateResolverQueryLogConfigCommandOutput extends Disasso
  *                   <p>You can stop sharing the configuration.</p>
  *                </li>
  *             </ul>
- * 		       </note>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/DisassociateResolverRuleCommand.d.ts

@@ -15,10 +15,10 @@ export interface DisassociateResolverRuleCommandOutput extends DisassociateResol
 }
 /**
  * <p>Removes the association between a specified Resolver rule and a specified VPC.</p>
- * 		       <important>
- * 			         <p>If you disassociate a Resolver rule from a VPC, Resolver stops forwarding DNS queries for the
+ *          <important>
+ *             <p>If you disassociate a Resolver rule from a VPC, Resolver stops forwarding DNS queries for the
  * 				domain name that you specified in the Resolver rule. </p>
- * 		       </important>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/GetResolverConfigCommand.d.ts

@@ -14,7 +14,7 @@ export interface GetResolverConfigCommandInput extends GetResolverConfigRequest
 export interface GetResolverConfigCommandOutput extends GetResolverConfigResponse, __MetadataBearer {
 }
 /**
- * <p>Retrieves the behavior configuration of Route 53 Resolver behavior for a single VPC from
+ * <p>Retrieves the behavior configuration of Route 53 Resolver behavior for a single VPC from
  * 				Amazon Virtual Private Cloud.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

package/dist-types/commands/ImportFirewallDomainsCommand.d.ts

@@ -19,16 +19,16 @@ export interface ImportFirewallDomainsCommandOutput extends ImportFirewallDomain
  * 	requirements: </p>
  *          <ul>
  *             <li>
- *       	        <p>It can optionally start with <code>*</code> (asterisk).</p>
- *       	     </li>
+ *                <p>It can optionally start with <code>*</code> (asterisk).</p>
+ *             </li>
  *             <li>
- *       	        <p>With the exception of the optional starting asterisk, it must only contain
+ *                <p>With the exception of the optional starting asterisk, it must only contain
  *       	   the following characters: <code>A-Z</code>, <code>a-z</code>,
  *       	   <code>0-9</code>, <code>-</code> (hyphen).</p>
- *       	     </li>
+ *             </li>
  *             <li>
- *       	        <p>It must be from 1-255 characters in length. </p>
- *       	     </li>
+ *                <p>It must be from 1-255 characters in length. </p>
+ *             </li>
  *          </ul>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

package/dist-types/commands/ListResolverConfigsCommand.d.ts

@@ -15,7 +15,7 @@ export interface ListResolverConfigsCommandOutput extends ListResolverConfigsRes
 }
 /**
  * <p>Retrieves the Resolver configurations that you have defined.
- * 			Route 53 Resolver uses the configurations to manage DNS resolution behavior for your VPCs.</p>
+ * 			Route 53 Resolver uses the configurations to manage DNS resolution behavior for your VPCs.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/UpdateResolverConfigCommand.d.ts

@@ -14,7 +14,7 @@ export interface UpdateResolverConfigCommandInput extends UpdateResolverConfigRe
 export interface UpdateResolverConfigCommandOutput extends UpdateResolverConfigResponse, __MetadataBearer {
 }
 /**
- * <p>Updates the behavior configuration of Route 53 Resolver behavior for a single VPC from
+ * <p>Updates the behavior configuration of Route 53 Resolver behavior for a single VPC from
  * 				Amazon Virtual Private Cloud.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

package/dist-types/commands/UpdateResolverEndpointCommand.d.ts

@@ -14,7 +14,8 @@ export interface UpdateResolverEndpointCommandInput extends UpdateResolverEndpoi
 export interface UpdateResolverEndpointCommandOutput extends UpdateResolverEndpointResponse, __MetadataBearer {
 }
 /**
- * <p>Updates the name of an inbound or an outbound Resolver endpoint.  </p>
+ * <p>Updates the name, or enpoint type for an inbound or an outbound Resolver endpoint.
+ * 			You can only update between IPV4 and DUALSTACK, IPV6 endpoint type can't be updated to other type. </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript