@aws-sdk/client-global-accelerator 3.36.0 → 3.39.0

package/CHANGELOG.md

@@ -3,6 +3,48 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.39.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.38.0...v3.39.0) (2021-10-29)
+
+**Note:** Version bump only for package @aws-sdk/client-global-accelerator
+
+
+
+
+
+# [3.38.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.37.0...v3.38.0) (2021-10-22)
+
+
+### Features
+
+* **client-documentation-generator:** rename package ([#2916](https://github.com/aws/aws-sdk-js-v3/issues/2916)) ([1a80bfd](https://github.com/aws/aws-sdk-js-v3/commit/1a80bfd2dfc583001ddb4a21b6432eaaad699aa7))
+* **clients:** export folder from index.ts ([#2912](https://github.com/aws/aws-sdk-js-v3/issues/2912)) ([183b46d](https://github.com/aws/aws-sdk-js-v3/commit/183b46dde7f5613128038bf1c076f3c0b693203b))
+
+
+
+
+
+# [3.37.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.36.1...v3.37.0) (2021-10-15)
+
+
+### Features
+
+* **clients:** update clients as of 10/15/2021 ([#2902](https://github.com/aws/aws-sdk-js-v3/issues/2902)) ([2730b54](https://github.com/aws/aws-sdk-js-v3/commit/2730b5424377944a5a2ad5e1ad7d3ca4135dae1c))
+
+
+
+
+
+## [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/GlobalAccelerator.js

@@ -49,156 +49,6 @@ const UpdateEndpointGroupCommand_1 = require("./commands/UpdateEndpointGroupComm
 const UpdateListenerCommand_1 = require("./commands/UpdateListenerCommand");
 const WithdrawByoipCidrCommand_1 = require("./commands/WithdrawByoipCidrCommand");
 const GlobalAcceleratorClient_1 = require("./GlobalAcceleratorClient");
-/**
- * <fullname>AWS Global Accelerator</fullname>
- * 		       <p>This is the <i>AWS Global Accelerator API Reference</i>. This guide is for developers who need detailed information about
- * 			AWS Global Accelerator API actions, data types, and errors. For more information about Global Accelerator features, see the
- * 			<a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/Welcome.html">AWS Global Accelerator Developer Guide</a>.</p>
- *
- * 		       <p>AWS Global Accelerator is a service in which you create <i>accelerators</i> to improve the performance
- * 			of your applications for local and global users. Depending on the type of accelerator you choose, you can
- * 			gain additional benefits. </p>
- * 		       <ul>
- *             <li>
- *                <p>By using a standard accelerator, you can improve availability of your internet applications
- * 				that are used by a global audience. With a standard accelerator, Global Accelerator directs traffic to optimal endpoints over the AWS
- * 				global network. </p>
- *             </li>
- *             <li>
- *                <p>For other scenarios, you might choose a custom routing accelerator. With a custom routing accelerator, you
- * 				can use application logic to directly map one or more users to a specific endpoint among many endpoints.</p>
- *             </li>
- *          </ul>
- * 		       <important>
- * 			         <p>Global Accelerator is a global service that supports endpoints in multiple AWS Regions but you must specify the
- * 				US West (Oregon) Region to create or update accelerators.</p>
- * 		       </important>
- * 		       <p>By default, Global Accelerator provides you with two static IP addresses that you associate with your accelerator. With
- * 			a standard accelerator, instead of using the
- * 			IP addresses that Global Accelerator provides, you can configure these entry points to be IPv4 addresses from your own IP address ranges
- * 			that you bring to Global Accelerator. The static IP addresses are anycast from the AWS edge network. For a standard accelerator,
- * 			they distribute incoming application traffic across multiple endpoint resources in multiple AWS Regions, which increases
- * 			the availability of your applications. Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers,
- * 			Amazon EC2 instances, or Elastic IP addresses that are located in one AWS Region or multiple Regions. For custom routing
- * 			accelerators, you map traffic that arrives to the static IP addresses to specific Amazon EC2 servers in endpoints that
- * 			are virtual private cloud (VPC) subnets.</p>
- *
- * 		       <important>
- *             <p>The static IP addresses remain assigned to your accelerator for as long as it exists, even if you
- * 				disable the accelerator and it no longer accepts or routes traffic. However, when you
- * 					<i>delete</i> an accelerator, you lose the static IP addresses that
- * 				are assigned to it, so you can no longer route traffic by using them. You can use
- * 				IAM policies like tag-based permissions with Global Accelerator to limit the users who have
- * 				permissions to delete an accelerator. For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
- *          </important>
- * 		       <p>For standard accelerators, Global Accelerator uses the AWS global network to route traffic to the optimal regional endpoint based
- * 			on health, client location, and policies that you configure. The service reacts instantly to
- * 			changes in health or configuration to ensure that internet traffic from clients is always
- * 			directed to healthy endpoints.</p>
- *
- * 		       <p>For a list of the AWS Regions where Global Accelerator and other services are currently supported, see the
- * 			<a href="https://docs.aws.amazon.com/about-aws/global-infrastructure/regional-product-services/">AWS
- * 				Region Table</a>.</p>
- *
- * 		       <p>AWS Global Accelerator includes the following components:</p>
- * 		       <dl>
- *             <dt>Static IP addresses</dt>
- *             <dd>
- *                <p>Global Accelerator provides you with a set of two static IP addresses that are anycast from the AWS edge
- * 					network. If you bring your own IP address range to AWS (BYOIP) to use with a standard accelerator, you
- * 					can instead assign IP addresses from your own pool to use with your accelerator. For more information,
- * 					see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html">
- * 						Bring your own IP addresses (BYOIP) in AWS Global Accelerator</a>.</p>
- * 					          <p>The IP addresses serve as single fixed entry points for your clients. If you already have Elastic
- * 						Load Balancing load balancers, Amazon EC2 instances, or Elastic IP address resources set up for your applications,
- * 						you can easily add those to a standard accelerator in Global Accelerator. This allows Global Accelerator to use static IP addresses
- * 						to access the resources.</p>
- * 					          <p>The static IP addresses remain assigned to your accelerator for as long as it exists, even
- * 						if you disable the accelerator and it no longer accepts or routes traffic.
- * 						However, when you <i>delete</i> an accelerator, you lose the
- * 						static IP addresses that are assigned to it, so you can no longer route
- * 						traffic by using them. You can use IAM policies like tag-based permissions
- * 						with Global Accelerator to delete an accelerator. For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
- * 				        </dd>
- *             <dt>Accelerator</dt>
- *             <dd>
- *                <p>An accelerator directs traffic to endpoints over the AWS global network to improve the
- * 					performance of your internet applications. Each accelerator includes one or more listeners.</p>
- * 					          <p>There are two types of accelerators:</p>
- * 					          <ul>
- *                   <li>
- *                      <p>A <i>standard</i> accelerator directs traffic to the optimal AWS endpoint based
- * 							on several factors, including the user’s location, the health of the endpoint, and the endpoint weights
- * 							that you configure. This improves the availability and performance of your applications.
- * 							Endpoints can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses.</p>
- *                   </li>
- *                   <li>
- *                      <p>A <i>custom routing</i> accelerator directs traffic to one of possibly thousands of
- * 								Amazon EC2 instances running in a single or multiple virtual private
- * 								clouds (VPCs). With custom routing, listener ports are mapped to
- * 								statically associate port ranges with VPC subnets, which
- * 								allows Global Accelerator to determine an EC2 instance IP address at the time of
- * 								connection. By default, all port mapping destinations in a VPC
- * 								subnet can't receive traffic. You can choose to configure all
- * 								destinations in the subnet to receive traffic, or to specify
- * 								individual port mappings that can receive traffic.</p>
- *                   </li>
- *                </ul>
- * 					          <p>For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-accelerator-types.html">Types of accelerators</a>.</p>
- * 				        </dd>
- *             <dt>DNS name</dt>
- *             <dd>
- *                <p>Global Accelerator assigns each accelerator a default Domain Name System (DNS) name, similar to
- * 					<code>a1234567890abcdef.awsglobalaccelerator.com</code>, that points to
- * 					the static IP addresses that Global Accelerator assigns to you or that you choose from your
- * 					own IP address range. Depending on the use
- * 					case, you can use your accelerator's static IP addresses or DNS name to
- * 					route traffic to your accelerator, or set up DNS records to route traffic using
- * 					your own custom domain name.</p>
- * 				        </dd>
- *             <dt>Network zone</dt>
- *             <dd>
- *                <p>A network zone services the static IP addresses for your accelerator from a unique IP subnet. Similar to an
- * 					AWS Availability Zone, a network zone is an isolated unit with its own set of physical infrastructure.
- * 					When you configure an accelerator, by default, Global Accelerator allocates two IPv4 addresses for it. If one IP address from a
- * 					network zone becomes unavailable due to IP address blocking by certain client networks, or network
- * 					disruptions, then client applications can retry on the healthy static IP address from the other isolated
- * 					network zone.</p>
- * 				        </dd>
- *             <dt>Listener</dt>
- *             <dd>
- *                <p>A listener processes inbound connections from clients to Global Accelerator, based on the port (or port range)
- * 					and protocol (or protocols) that you configure. A listener can be configured for TCP, UDP, or both TCP and UDP protocols. Each
- * 					listener has one or more endpoint groups associated with it, and traffic is forwarded
- * 					to endpoints in one of the groups. You associate endpoint groups with listeners by specifying the Regions that you
- * 					want to distribute traffic to. With a standard accelerator, traffic is distributed to optimal endpoints within the endpoint
- * 					groups associated with a listener.</p>
- *             </dd>
- *             <dt>Endpoint group</dt>
- *             <dd>
- *                <p>Each endpoint group is associated with a specific AWS Region. Endpoint groups include one or
- * 					more endpoints in the Region. With a standard accelerator, you can increase or reduce the percentage of
- * 					traffic that would be otherwise directed to an endpoint group by adjusting a
- * 					setting called a <i>traffic dial</i>. The traffic dial lets
- * 					you easily do performance testing or blue/green deployment testing, for example, for new
- * 					releases across different AWS Regions. </p>
- * 				        </dd>
- *             <dt>Endpoint</dt>
- *             <dd>
- *                <p>An endpoint is a resource that Global Accelerator directs traffic to.</p>
- * 					          <p>Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP
- * 						addresses. An Application Load Balancer endpoint can be internet-facing or internal. Traffic for
- * 						standard accelerators is routed to endpoints based on the health of the
- * 						endpoint along with configuration options that you choose, such as endpoint
- * 						weights. For each endpoint, you can configure weights, which are numbers
- * 						that you can use to specify the proportion of traffic to route to each one.
- * 						This can be useful, for example, to do performance testing within a
- * 						Region.</p>
- * 					          <p>Endpoints for custom routing accelerators are virtual private cloud (VPC) subnets with one
- * 						or many EC2 instances.</p>
- * 				        </dd>
- *          </dl>
- */
 class GlobalAccelerator extends GlobalAcceleratorClient_1.GlobalAcceleratorClient {
     addCustomRoutingEndpoints(args, optionsOrCb, cb) {
         const command = new AddCustomRoutingEndpointsCommand_1.AddCustomRoutingEndpointsCommand(args);

package/dist-cjs/GlobalAcceleratorClient.js

@@ -10,156 +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");
-/**
- * <fullname>AWS Global Accelerator</fullname>
- * 		       <p>This is the <i>AWS Global Accelerator API Reference</i>. This guide is for developers who need detailed information about
- * 			AWS Global Accelerator API actions, data types, and errors. For more information about Global Accelerator features, see the
- * 			<a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/Welcome.html">AWS Global Accelerator Developer Guide</a>.</p>
- *
- * 		       <p>AWS Global Accelerator is a service in which you create <i>accelerators</i> to improve the performance
- * 			of your applications for local and global users. Depending on the type of accelerator you choose, you can
- * 			gain additional benefits. </p>
- * 		       <ul>
- *             <li>
- *                <p>By using a standard accelerator, you can improve availability of your internet applications
- * 				that are used by a global audience. With a standard accelerator, Global Accelerator directs traffic to optimal endpoints over the AWS
- * 				global network. </p>
- *             </li>
- *             <li>
- *                <p>For other scenarios, you might choose a custom routing accelerator. With a custom routing accelerator, you
- * 				can use application logic to directly map one or more users to a specific endpoint among many endpoints.</p>
- *             </li>
- *          </ul>
- * 		       <important>
- * 			         <p>Global Accelerator is a global service that supports endpoints in multiple AWS Regions but you must specify the
- * 				US West (Oregon) Region to create or update accelerators.</p>
- * 		       </important>
- * 		       <p>By default, Global Accelerator provides you with two static IP addresses that you associate with your accelerator. With
- * 			a standard accelerator, instead of using the
- * 			IP addresses that Global Accelerator provides, you can configure these entry points to be IPv4 addresses from your own IP address ranges
- * 			that you bring to Global Accelerator. The static IP addresses are anycast from the AWS edge network. For a standard accelerator,
- * 			they distribute incoming application traffic across multiple endpoint resources in multiple AWS Regions, which increases
- * 			the availability of your applications. Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers,
- * 			Amazon EC2 instances, or Elastic IP addresses that are located in one AWS Region or multiple Regions. For custom routing
- * 			accelerators, you map traffic that arrives to the static IP addresses to specific Amazon EC2 servers in endpoints that
- * 			are virtual private cloud (VPC) subnets.</p>
- *
- * 		       <important>
- *             <p>The static IP addresses remain assigned to your accelerator for as long as it exists, even if you
- * 				disable the accelerator and it no longer accepts or routes traffic. However, when you
- * 					<i>delete</i> an accelerator, you lose the static IP addresses that
- * 				are assigned to it, so you can no longer route traffic by using them. You can use
- * 				IAM policies like tag-based permissions with Global Accelerator to limit the users who have
- * 				permissions to delete an accelerator. For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
- *          </important>
- * 		       <p>For standard accelerators, Global Accelerator uses the AWS global network to route traffic to the optimal regional endpoint based
- * 			on health, client location, and policies that you configure. The service reacts instantly to
- * 			changes in health or configuration to ensure that internet traffic from clients is always
- * 			directed to healthy endpoints.</p>
- *
- * 		       <p>For a list of the AWS Regions where Global Accelerator and other services are currently supported, see the
- * 			<a href="https://docs.aws.amazon.com/about-aws/global-infrastructure/regional-product-services/">AWS
- * 				Region Table</a>.</p>
- *
- * 		       <p>AWS Global Accelerator includes the following components:</p>
- * 		       <dl>
- *             <dt>Static IP addresses</dt>
- *             <dd>
- *                <p>Global Accelerator provides you with a set of two static IP addresses that are anycast from the AWS edge
- * 					network. If you bring your own IP address range to AWS (BYOIP) to use with a standard accelerator, you
- * 					can instead assign IP addresses from your own pool to use with your accelerator. For more information,
- * 					see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html">
- * 						Bring your own IP addresses (BYOIP) in AWS Global Accelerator</a>.</p>
- * 					          <p>The IP addresses serve as single fixed entry points for your clients. If you already have Elastic
- * 						Load Balancing load balancers, Amazon EC2 instances, or Elastic IP address resources set up for your applications,
- * 						you can easily add those to a standard accelerator in Global Accelerator. This allows Global Accelerator to use static IP addresses
- * 						to access the resources.</p>
- * 					          <p>The static IP addresses remain assigned to your accelerator for as long as it exists, even
- * 						if you disable the accelerator and it no longer accepts or routes traffic.
- * 						However, when you <i>delete</i> an accelerator, you lose the
- * 						static IP addresses that are assigned to it, so you can no longer route
- * 						traffic by using them. You can use IAM policies like tag-based permissions
- * 						with Global Accelerator to delete an accelerator. For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
- * 				        </dd>
- *             <dt>Accelerator</dt>
- *             <dd>
- *                <p>An accelerator directs traffic to endpoints over the AWS global network to improve the
- * 					performance of your internet applications. Each accelerator includes one or more listeners.</p>
- * 					          <p>There are two types of accelerators:</p>
- * 					          <ul>
- *                   <li>
- *                      <p>A <i>standard</i> accelerator directs traffic to the optimal AWS endpoint based
- * 							on several factors, including the user’s location, the health of the endpoint, and the endpoint weights
- * 							that you configure. This improves the availability and performance of your applications.
- * 							Endpoints can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses.</p>
- *                   </li>
- *                   <li>
- *                      <p>A <i>custom routing</i> accelerator directs traffic to one of possibly thousands of
- * 								Amazon EC2 instances running in a single or multiple virtual private
- * 								clouds (VPCs). With custom routing, listener ports are mapped to
- * 								statically associate port ranges with VPC subnets, which
- * 								allows Global Accelerator to determine an EC2 instance IP address at the time of
- * 								connection. By default, all port mapping destinations in a VPC
- * 								subnet can't receive traffic. You can choose to configure all
- * 								destinations in the subnet to receive traffic, or to specify
- * 								individual port mappings that can receive traffic.</p>
- *                   </li>
- *                </ul>
- * 					          <p>For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-accelerator-types.html">Types of accelerators</a>.</p>
- * 				        </dd>
- *             <dt>DNS name</dt>
- *             <dd>
- *                <p>Global Accelerator assigns each accelerator a default Domain Name System (DNS) name, similar to
- * 					<code>a1234567890abcdef.awsglobalaccelerator.com</code>, that points to
- * 					the static IP addresses that Global Accelerator assigns to you or that you choose from your
- * 					own IP address range. Depending on the use
- * 					case, you can use your accelerator's static IP addresses or DNS name to
- * 					route traffic to your accelerator, or set up DNS records to route traffic using
- * 					your own custom domain name.</p>
- * 				        </dd>
- *             <dt>Network zone</dt>
- *             <dd>
- *                <p>A network zone services the static IP addresses for your accelerator from a unique IP subnet. Similar to an
- * 					AWS Availability Zone, a network zone is an isolated unit with its own set of physical infrastructure.
- * 					When you configure an accelerator, by default, Global Accelerator allocates two IPv4 addresses for it. If one IP address from a
- * 					network zone becomes unavailable due to IP address blocking by certain client networks, or network
- * 					disruptions, then client applications can retry on the healthy static IP address from the other isolated
- * 					network zone.</p>
- * 				        </dd>
- *             <dt>Listener</dt>
- *             <dd>
- *                <p>A listener processes inbound connections from clients to Global Accelerator, based on the port (or port range)
- * 					and protocol (or protocols) that you configure. A listener can be configured for TCP, UDP, or both TCP and UDP protocols. Each
- * 					listener has one or more endpoint groups associated with it, and traffic is forwarded
- * 					to endpoints in one of the groups. You associate endpoint groups with listeners by specifying the Regions that you
- * 					want to distribute traffic to. With a standard accelerator, traffic is distributed to optimal endpoints within the endpoint
- * 					groups associated with a listener.</p>
- *             </dd>
- *             <dt>Endpoint group</dt>
- *             <dd>
- *                <p>Each endpoint group is associated with a specific AWS Region. Endpoint groups include one or
- * 					more endpoints in the Region. With a standard accelerator, you can increase or reduce the percentage of
- * 					traffic that would be otherwise directed to an endpoint group by adjusting a
- * 					setting called a <i>traffic dial</i>. The traffic dial lets
- * 					you easily do performance testing or blue/green deployment testing, for example, for new
- * 					releases across different AWS Regions. </p>
- * 				        </dd>
- *             <dt>Endpoint</dt>
- *             <dd>
- *                <p>An endpoint is a resource that Global Accelerator directs traffic to.</p>
- * 					          <p>Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP
- * 						addresses. An Application Load Balancer endpoint can be internet-facing or internal. Traffic for
- * 						standard accelerators is routed to endpoints based on the health of the
- * 						endpoint along with configuration options that you choose, such as endpoint
- * 						weights. For each endpoint, you can configure weights, which are numbers
- * 						that you can use to specify the proportion of traffic to route to each one.
- * 						This can be useful, for example, to do performance testing within a
- * 						Region.</p>
- * 					          <p>Endpoints for custom routing accelerators are virtual private cloud (VPC) subnets with one
- * 						or many EC2 instances.</p>
- * 				        </dd>
- *          </dl>
- */
 class GlobalAcceleratorClient extends smithy_client_1.Client {
     constructor(configuration) {
         const _config_0 = runtimeConfig_1.getRuntimeConfig(configuration);
@@ -178,11 +28,6 @@ class GlobalAcceleratorClient 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/AddCustomRoutingEndpointsCommand.js

@@ -5,45 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Associate a virtual private cloud (VPC) subnet endpoint with your custom routing accelerator.</p>
- * 	        <p>The listener port range must be large enough to support the number of IP addresses that can be
- * 		specified in your subnet. The number of ports required is: subnet size times the number
- * 		of ports per destination EC2 instances. For example, a subnet defined as /24 requires a listener
- * 		port range of at least 255 ports. </p>
- * 	        <p>Note: You must have enough remaining listener ports available to
- * 		map to the subnet ports, or the call will fail with a LimitExceededException.</p>
- * 	        <p>By default, all destinations in a subnet in a custom routing accelerator cannot receive traffic. To enable all
- * 			destinations to receive traffic, or to specify individual port mappings that can receive
- * 			traffic, see the <a href="https://docs.aws.amazon.com/global-accelerator/latest/api/API_AllowCustomRoutingTraffic.html">
- * 				AllowCustomRoutingTraffic</a> operation.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, AddCustomRoutingEndpointsCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, AddCustomRoutingEndpointsCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new AddCustomRoutingEndpointsCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link AddCustomRoutingEndpointsCommandInput} for command's `input` shape.
- * @see {@link AddCustomRoutingEndpointsCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class AddCustomRoutingEndpointsCommand 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/AdvertiseByoipCidrCommand.js

@@ -5,41 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Advertises an IPv4 address range that is provisioned for use with your AWS resources
- * 			through bring your own IP addresses (BYOIP). It can take a few minutes before traffic to
- * 			the specified addresses starts routing to AWS because of propagation delays. </p>
- * 		       <p>To stop advertising the BYOIP address range, use <a href="https://docs.aws.amazon.com/global-accelerator/latest/api/WithdrawByoipCidr.html">
- * 			WithdrawByoipCidr</a>.</p>
- * 		       <p>For more information, see <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html">Bring Your Own
- * 			IP Addresses (BYOIP)</a> in the <i>AWS Global Accelerator Developer Guide</i>.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, AdvertiseByoipCidrCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, AdvertiseByoipCidrCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new AdvertiseByoipCidrCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link AdvertiseByoipCidrCommandInput} for command's `input` shape.
- * @see {@link AdvertiseByoipCidrCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class AdvertiseByoipCidrCommand 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/AllowCustomRoutingTrafficCommand.js

@@ -5,40 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Specify the Amazon EC2 instance (destination) IP addresses and ports for a VPC subnet endpoint that can receive traffic
- * 			for a custom routing accelerator. You can allow traffic to all destinations in the subnet endpoint, or allow traffic to a
- * 			specified list of destination IP addresses and ports in the subnet. Note that you cannot specify IP addresses or ports
- * 			outside of the range that you configured for the endpoint group.</p>
- * 		       <p>After you make changes, you can verify that the updates are complete by checking the status of your
- * 			accelerator: the status changes from IN_PROGRESS to DEPLOYED.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, AllowCustomRoutingTrafficCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, AllowCustomRoutingTrafficCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new AllowCustomRoutingTrafficCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link AllowCustomRoutingTrafficCommandInput} for command's `input` shape.
- * @see {@link AllowCustomRoutingTrafficCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class AllowCustomRoutingTrafficCommand 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/CreateAcceleratorCommand.js

@@ -5,40 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Create an accelerator. An accelerator includes one or more listeners that process inbound connections and direct traffic
- * 			to one or more endpoint groups, each of which includes endpoints, such as Network Load Balancers. </p>
- * 		       <important>
- * 			         <p>Global Accelerator is a global service that supports endpoints in multiple AWS Regions but you must specify the
- * 				US West (Oregon) Region to create or update accelerators.</p>
- * 		       </important>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, CreateAcceleratorCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, CreateAcceleratorCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new CreateAcceleratorCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateAcceleratorCommandInput} for command's `input` shape.
- * @see {@link CreateAcceleratorCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateAcceleratorCommand 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/CreateCustomRoutingAcceleratorCommand.js

@@ -5,44 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Create a custom routing accelerator. A custom routing accelerator directs traffic to one of possibly thousands
- * 		of Amazon EC2 instance destinations running in a single or multiple virtual private clouds (VPC) subnet endpoints.</p>
- * 	        <p>Be aware that, by default, all destination EC2 instances in a VPC subnet endpoint cannot receive
- * 			traffic. To enable all destinations to receive traffic, or to specify individual port
- * 			mappings that can receive traffic, see the <a href="https://docs.aws.amazon.com/global-accelerator/latest/api/API_AllowCustomRoutingTraffic.html">
- * 				AllowCustomRoutingTraffic</a> operation.</p>
- * 	        <important>
- * 		          <p>Global Accelerator is a global service that supports endpoints in multiple AWS Regions but you must specify the
- * 			US West (Oregon) Region to create or update accelerators.</p>
- * 	        </important>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, CreateCustomRoutingAcceleratorCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, CreateCustomRoutingAcceleratorCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new CreateCustomRoutingAcceleratorCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateCustomRoutingAcceleratorCommandInput} for command's `input` shape.
- * @see {@link CreateCustomRoutingAcceleratorCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateCustomRoutingAcceleratorCommand 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/CreateCustomRoutingEndpointGroupCommand.js

@@ -5,37 +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_json1_1_1 = require("../protocols/Aws_json1_1");
-/**
- * <p>Create an endpoint group for the specified listener for a custom routing accelerator.
- * 		An endpoint group is a collection of endpoints in one AWS
- * 		Region. </p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { GlobalAcceleratorClient, CreateCustomRoutingEndpointGroupCommand } from "@aws-sdk/client-global-accelerator"; // ES Modules import
- * // const { GlobalAcceleratorClient, CreateCustomRoutingEndpointGroupCommand } = require("@aws-sdk/client-global-accelerator"); // CommonJS import
- * const client = new GlobalAcceleratorClient(config);
- * const command = new CreateCustomRoutingEndpointGroupCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateCustomRoutingEndpointGroupCommandInput} for command's `input` shape.
- * @see {@link CreateCustomRoutingEndpointGroupCommandOutput} for command's `response` shape.
- * @see {@link GlobalAcceleratorClientResolvedConfig | config} for command's `input` shape.
- *
- */
 class CreateCustomRoutingEndpointGroupCommand 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);