openapi: 3.0.0
info:
version: '2018-08-08'
x-release: v4
title: AWS Global Accelerator
description: '<fullname>Global Accelerator</fullname> <p>This is the <i>Global Accelerator API Reference</i>. This guide is for developers who need detailed information about 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/what-is-global-accelerator.html">Global Accelerator
Developer Guide</a>.</p> <p>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 Amazon Web Services 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 Amazon Web Services Regions but you must specify the US West (Oregon) Region to create, update, or otherwise work with accelerators. That is,
for example, specify <code>--region us-west-2</code> on AWS CLI commands.</p> </important> <p>By default, Global Accelerator provides you with static IP addresses that you associate with your accelerator.
The static IP addresses are anycast from the Amazon Web Services edge network. For IPv4, Global Accelerator provides two static IPv4 addresses. For dual-stack, Global Accelerator provides a total of
four addresses: two static IPv4 addresses and two static IPv6 addresses. With a standard accelerator for IPv4, instead of using the addresses that Global Accelerator provides, you can configure these
entry points to be IPv4 addresses from your own IP address ranges that you bring toGlobal Accelerator (BYOIP). </p> <p>For a standard accelerator, they distribute incoming application traffic across
multiple endpoint resources in multiple Amazon Web Services 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 Amazon Web Services Region or multiple Amazon Web Services 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 Amazon Web Services 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 more information about understanding and using Global
Accelerator, see the <a href="https://docs.aws.amazon.com/global-accelerator/latest/dg/what-is-global-accelerator.html">Global Accelerator Developer Guide</a>.</p>'
x-logo:
url: https://api.apis.guru/v2/cache/logo/https_twitter.com_awscloud_profile_image.png
backgroundColor: '#FFFFFF'
termsOfService: https://aws.amazon.com/service-terms/
contact:
name: Mike Ralphson
email: [email protected]
url: https://github.com/mermade/aws2openapi
x-twitter: PermittedSoc
license:
name: Apache 2.0 License
url: http://www.apache.org/licenses/
x-providerName: amazonaws.com
x-serviceName: globalaccelerator
x-aws-signingName: globalaccelerator
x-origin:
- contentType: application/json
url: https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/globalaccelerator-2018-08-08.normal.json
converter:
url: https://github.com/mermade/aws2openapi
version: 1.0.0
x-apisguru-driver: external
x-apiClientRegistration:
url: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_ct
x-apisguru-categories:
- cloud
x-preferred: true
externalDocs:
description: Amazon Web Services documentation
url: https://docs.aws.amazon.com/globalaccelerator/
servers:
- url: http://globalaccelerator.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The AWS Global Accelerator multi-region endpoint
- url: https://globalaccelerator.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The AWS Global Accelerator multi-region endpoint
- url: http://globalaccelerator.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The AWS Global Accelerator endpoint for China (Beijing) and China (Ningxia)
- url: https://globalaccelerator.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The AWS Global Accelerator endpoint for China (Beijing) and China (Ningxia)
x-hasEquivalentPaths: true
paths:
/#X-Amz-Target=GlobalAccelerator_V20180706.AddCustomRoutingEndpoints:
post:
operationId: AddCustomRoutingEndpoints
description: '<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>'
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/AddCustomRoutingEndpointsResponse'
examples:
AddCustomRoutingEndpoints200Example:
summary: Default AddCustomRoutingEndpoints 200 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'480':
description: EndpointAlreadyExistsException
content:
application/json:
schema:
$ref: '#/components/schemas/EndpointAlreadyExistsException'
examples:
AddCustomRoutingEndpoints480Example:
summary: Default AddCustomRoutingEndpoints 480 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'481':
description: EndpointGroupNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/EndpointGroupNotFoundException'
examples:
AddCustomRoutingEndpoints481Example:
summary: Default AddCustomRoutingEndpoints 481 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'482':
description: InternalServiceErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalServiceErrorException'
examples:
AddCustomRoutingEndpoints482Example:
summary: Default AddCustomRoutingEndpoints 482 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'483':
description: InvalidArgumentException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidArgumentException'
examples:
AddCustomRoutingEndpoints483Example:
summary: Default AddCustomRoutingEndpoints 483 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'484':
description: LimitExceededException
content:
application/json:
schema:
$ref: '#/components/schemas/LimitExceededException'
examples:
AddCustomRoutingEndpoints484Example:
summary: Default AddCustomRoutingEndpoints 484 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'485':
description: AccessDeniedException
content:
application/json:
schema:
$ref: '#/components/schemas/AccessDeniedException'
examples:
AddCustomRoutingEndpoints485Example:
summary: Default AddCustomRoutingEndpoints 485 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'486':
description: ConflictException
content:
application/json:
schema:
$ref: '#/components/schemas/ConflictException'
examples:
AddCustomRoutingEndpoints486Example:
summary: Default AddCustomRoutingEndpoints 486 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AddCustomRoutingEndpointsRequest'
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GlobalAccelerator_V20180706.AddCustomRoutingEndpoints
summary: Amazon Global Accelerator Add Custom Routing Endpoints
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
/#X-Amz-Target=GlobalAccelerator_V20180706.AddEndpoints:
post:
operationId: AddEndpoints
description: <p>Add endpoints to an endpoint group. The <code>AddEndpoints</code> API operation is the recommended option for adding endpoints. The alternative options are to add endpoints when
you create an endpoint group (with the <a href="https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateEndpointGroup.html">CreateEndpointGroup</a> API) or when you update an
endpoint group (with the <a href="https://docs.aws.amazon.com/global-accelerator/latest/api/API_UpdateEndpointGroup.html">UpdateEndpointGroup</a> API). </p> <p>There are two advantages to
using <code>AddEndpoints</code> to add endpoints:</p> <ul> <li> <p>It's faster, because Global Accelerator only has to resolve the new endpoints that you're adding.</p> </li> <li> <p>It's more
convenient, because you don't need to specify all of the current endpoints that are already in the endpoint group in addition to the new endpoints that you want to add.</p> </li> </ul>
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/AddEndpointsResponse'
examples:
AddEndpoints200Example:
summary: Default AddEndpoints 200 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'480':
description: TransactionInProgressException
content:
application/json:
schema:
$ref: '#/components/schemas/TransactionInProgressException'
examples:
AddEndpoints480Example:
summary: Default AddEndpoints 480 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'481':
description: EndpointGroupNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/EndpointGroupNotFoundException'
examples:
AddEndpoints481Example:
summary: Default AddEndpoints 481 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'482':
description: InternalServiceErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalServiceErrorException'
examples:
AddEndpoints482Example:
summary: Default AddEndpoints 482 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'483':
description: InvalidArgumentException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidArgumentException'
examples:
AddEndpoints483Example:
summary: Default AddEndpoints 483 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'484':
description: LimitExceededException
content:
application/json:
schema:
$ref: '#/components/schemas/LimitExceededException'
examples:
AddEndpoints484Example:
summary: Default AddEndpoints 484 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'485':
description: AccessDeniedException
content:
application/json:
schema:
$ref: '#/components/schemas/AccessDeniedException'
examples:
AddEndpoints485Example:
summary: Default AddEndpoints 485 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AddEndpointsRequest'
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GlobalAccelerator_V20180706.AddEndpoints
summary: Amazon Global Accelerator Add Endpoints
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
/#X-Amz-Target=GlobalAccelerator_V20180706.AdvertiseByoipCidr:
post:
operationId: AdvertiseByoipCidr
description: <p>Advertises an IPv4 address range that is provisioned for use with your Amazon Web Services resources through bring your own IP addresses (BYOIP). It can take a few minutes before
traffic to the specified addresses starts routing to Amazon Web Services 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>Global Accelerator Developer Guide</i>.</p>
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/AdvertiseByoipCidrResponse'
examples:
AdvertiseByoipCidr200Example:
summary: Default AdvertiseByoipCidr 200 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'480':
description: InternalServiceErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalServiceErrorException'
examples:
AdvertiseByoipCidr480Example:
summary: Default AdvertiseByoipCidr 480 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'481':
description: InvalidArgumentException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidArgumentException'
examples:
AdvertiseByoipCidr481Example:
summary: Default AdvertiseByoipCidr 481 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'482':
description: AccessDeniedException
content:
application/json:
schema:
$ref: '#/components/schemas/AccessDeniedException'
examples:
AdvertiseByoipCidr482Example:
summary: Default AdvertiseByoipCidr 482 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'483':
description: ByoipCidrNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/ByoipCidrNotFoundException'
examples:
AdvertiseByoipCidr483Example:
summary: Default AdvertiseByoipCidr 483 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'484':
description: IncorrectCidrStateException
content:
application/json:
schema:
$ref: '#/components/schemas/IncorrectCidrStateException'
examples:
AdvertiseByoipCidr484Example:
summary: Default AdvertiseByoipCidr 484 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AdvertiseByoipCidrRequest'
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GlobalAccelerator_V20180706.AdvertiseByoipCidr
summary: Amazon Global Accelerator Advertise Byoip Cidr
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
/#X-Amz-Target=GlobalAccelerator_V20180706.AllowCustomRoutingTraffic:
post:
operationId: AllowCustomRoutingTraffic
description: '<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>'
responses:
'200':
description: Success
'480':
description: EndpointGroupNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/EndpointGroupNotFoundException'
examples:
AllowCustomRoutingTraffic480Example:
summary: Default AllowCustomRoutingTraffic 480 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'481':
description: InvalidArgumentException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidArgumentException'
examples:
AllowCustomRoutingTraffic481Example:
summary: Default AllowCustomRoutingTraffic 481 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'482':
description: InternalServiceErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalServiceErrorException'
examples:
AllowCustomRoutingTraffic482Example:
summary: Default AllowCustomRoutingTraffic 482 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AllowCustomRoutingTrafficRequest'
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GlobalAccelerator_V20180706.AllowCustomRoutingTraffic
summary: Amazon Global Accelerator Allow Custom Routing Traffic
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
/#X-Amz-Target=GlobalAccelerator_V20180706.CreateAccelerator:
post:
operationId: CreateAccelerator
description: <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 Amazon Web Services Regions but you must specify the
US West (Oregon) Region to create, update, or otherwise work with accelerators. That is, for example, specify <code>--region us-west-2</code> on AWS CLI commands.</p> </important>
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/CreateAcceleratorResponse'
examples:
CreateAccelerator200Example:
summary: Default CreateAccelerator 200 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'480':
description: InternalServiceErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalServiceErrorException'
examples:
CreateAccelerator480Example:
summary: Default CreateAccelerator 480 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'481':
description: InvalidArgumentException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidArgumentException'
examples:
CreateAccelerator481Example:
summary: Default CreateAccelerator 481 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
'482':
description: LimitExceededException
content:
application/json:
schema:
$ref: '#/components/schemas/LimitExceededException'
examples:
CreateAccelerator482Example:
summary: Default CreateAccelerator 482 response
x-microcks-default: true
value:
acceleratorArn: arn:aws:globalaccelerator::123456789012:accelerator/abc123
status: DEPLOYED
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CreateAcceleratorRequest'
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- GlobalAccelerator_V20180706.CreateAccelerator
summary: Amazon Global Accelerator Create Accelerator
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
/#X-Amz-Target=GlobalAccelerator_V20180706.CreateCustomRoutingAccelerator:
post:
operationId: CreateCustomRoutingAccelerator
description: <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 Amazon Web Services Regions but you must specify the US West (Oregon) Region to create, update, or otherwise work with accelerators. That is, for
exa
# --- truncated at 32 KB (315 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/amazon-global-accelerator/refs/heads/main/openapi/amazon-global-accelerator-openapi.yml