You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>Global Accelerator is a service in which you create <i>accelerators</i> to improve the performance
19
18
of your applications for local and global users. Depending on the type of accelerator you choose, you can
20
19
gain additional benefits. </p>
21
20
<ul>
22
21
<li>
23
22
<p>By using a standard accelerator, you can improve availability of your internet applications
24
-
that are used by a global audience. With a standard accelerator, Global Accelerator directs traffic to optimal endpoints over the AWS
23
+
that are used by a global audience. With a standard accelerator, Global Accelerator directs traffic to optimal endpoints over the Amazon Web Services
25
24
global network. </p>
26
25
</li>
27
26
<li>
@@ -30,16 +29,21 @@ can use application logic to directly map one or more users to a specific endpoi
30
29
</li>
31
30
</ul>
32
31
<important>
33
-
<p>Global Accelerator is a global service that supports endpoints in multiple AWS Regions but you must specify the
34
-
US West (Oregon) Region to create or update accelerators.</p>
32
+
<p>Global Accelerator is a global service that supports endpoints in multiple Amazon Web Services Regions but you must specify the
33
+
US West (Oregon) Region to create, update, or otherwise work with accelerators. That is, for example, specify <code>--region us-west-2</code>
34
+
on AWS CLI commands.</p>
35
35
</important>
36
-
<p>By default, Global Accelerator provides you with two static IP addresses that you associate with your accelerator. With
37
-
a standard accelerator, instead of using the
38
-
IP addresses that Global Accelerator provides, you can configure these entry points to be IPv4 addresses from your own IP address ranges
39
-
that you bring to Global Accelerator. The static IP addresses are anycast from the AWS edge network. For a standard accelerator,
40
-
they distribute incoming application traffic across multiple endpoint resources in multiple AWS Regions, which increases
36
+
37
+
<p>By default, Global Accelerator provides you with static IP addresses that you associate with your accelerator. The static IP addresses
38
+
are anycast from the Amazon Web Services edge network. For IPv4, Global Accelerator provides two static IPv4 addresses. For dual-stack,
39
+
Global Accelerator provides a total of four addresses: two static IPv4 addresses and two static IPv6 addresses.
40
+
With a standard accelerator for IPv4, instead of using the addresses that Global Accelerator provides, you can configure
41
+
these entry points to be IPv4 addresses from your own IP address ranges that you bring toGlobal Accelerator (BYOIP). </p>
42
+
43
+
<p>For a standard accelerator,
44
+
they distribute incoming application traffic across multiple endpoint resources in multiple Amazon Web Services Regions , which increases
41
45
the availability of your applications. Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers,
42
-
Amazon EC2 instances, or Elastic IP addresses that are located in one AWS Region or multiple Regions. For custom routing
46
+
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
43
47
accelerators, you map traffic that arrives to the static IP addresses to specific Amazon EC2 servers in endpoints that
44
48
are virtual private cloud (VPC) subnets.</p>
45
49
@@ -51,113 +55,12 @@ are assigned to it, so you can no longer route traffic by using them. You can us
51
55
IAM policies like tag-based permissions with Global Accelerator to limit the users who have
52
56
permissions to delete an accelerator. For more information, see <ahref="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
53
57
</important>
54
-
<p>For standard accelerators, Global Accelerator uses the AWS global network to route traffic to the optimal regional endpoint based
58
+
<p>For standard accelerators, Global Accelerator uses the Amazon Web Services global network to route traffic to the optimal regional endpoint based
55
59
on health, client location, and policies that you configure. The service reacts instantly to
56
60
changes in health or configuration to ensure that internet traffic from clients is always
57
61
directed to healthy endpoints.</p>
58
-
59
-
<p>For a list of the AWS Regions where Global Accelerator and other services are currently supported, see the
<p>AWS Global Accelerator includes the following components:</p>
64
-
<dl>
65
-
<dt>Static IP addresses</dt>
66
-
<dd>
67
-
<p>Global Accelerator provides you with a set of two static IP addresses that are anycast from the AWS edge
68
-
network. If you bring your own IP address range to AWS (BYOIP) to use with a standard accelerator, you
69
-
can instead assign IP addresses from your own pool to use with your accelerator. For more information,
70
-
see <ahref="https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html">
71
-
Bring your own IP addresses (BYOIP) in AWS Global Accelerator</a>.</p>
72
-
<p>The IP addresses serve as single fixed entry points for your clients. If you already have Elastic
73
-
Load Balancing load balancers, Amazon EC2 instances, or Elastic IP address resources set up for your applications,
74
-
you can easily add those to a standard accelerator in Global Accelerator. This allows Global Accelerator to use static IP addresses
75
-
to access the resources.</p>
76
-
<p>The static IP addresses remain assigned to your accelerator for as long as it exists, even
77
-
if you disable the accelerator and it no longer accepts or routes traffic.
78
-
However, when you <i>delete</i> an accelerator, you lose the
79
-
static IP addresses that are assigned to it, so you can no longer route
80
-
traffic by using them. You can use IAM policies like tag-based permissions
81
-
with Global Accelerator to delete an accelerator. For more information, see <ahref="https://docs.aws.amazon.com/global-accelerator/latest/dg/access-control-manage-access-tag-policies.html">Tag-based policies</a>.</p>
82
-
</dd>
83
-
<dt>Accelerator</dt>
84
-
<dd>
85
-
<p>An accelerator directs traffic to endpoints over the AWS global network to improve the
86
-
performance of your internet applications. Each accelerator includes one or more listeners.</p>
87
-
<p>There are two types of accelerators:</p>
88
-
<ul>
89
-
<li>
90
-
<p>A <i>standard</i> accelerator directs traffic to the optimal AWS endpoint based
91
-
on several factors, including the user’s location, the health of the endpoint, and the endpoint weights
92
-
that you configure. This improves the availability and performance of your applications.
93
-
Endpoints can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses.</p>
94
-
</li>
95
-
<li>
96
-
<p>A <i>custom routing</i> accelerator directs traffic to one of possibly thousands of
97
-
Amazon EC2 instances running in a single or multiple virtual private
98
-
clouds (VPCs). With custom routing, listener ports are mapped to
99
-
statically associate port ranges with VPC subnets, which
100
-
allows Global Accelerator to determine an EC2 instance IP address at the time of
101
-
connection. By default, all port mapping destinations in a VPC
102
-
subnet can't receive traffic. You can choose to configure all
103
-
destinations in the subnet to receive traffic, or to specify
104
-
individual port mappings that can receive traffic.</p>
105
-
</li>
106
-
</ul>
107
-
<p>For more information, see <ahref="https://docs.aws.amazon.com/global-accelerator/latest/dg/introduction-accelerator-types.html">Types of accelerators</a>.</p>
108
-
</dd>
109
-
<dt>DNS name</dt>
110
-
<dd>
111
-
<p>Global Accelerator assigns each accelerator a default Domain Name System (DNS) name, similar to
112
-
<code>a1234567890abcdef.awsglobalaccelerator.com</code>, that points to
113
-
the static IP addresses that Global Accelerator assigns to you or that you choose from your
114
-
own IP address range. Depending on the use
115
-
case, you can use your accelerator's static IP addresses or DNS name to
116
-
route traffic to your accelerator, or set up DNS records to route traffic using
117
-
your own custom domain name.</p>
118
-
</dd>
119
-
<dt>Network zone</dt>
120
-
<dd>
121
-
<p>A network zone services the static IP addresses for your accelerator from a unique IP subnet. Similar to an
122
-
AWS Availability Zone, a network zone is an isolated unit with its own set of physical infrastructure.
123
-
When you configure an accelerator, by default, Global Accelerator allocates two IPv4 addresses for it. If one IP address from a
124
-
network zone becomes unavailable due to IP address blocking by certain client networks, or network
125
-
disruptions, then client applications can retry on the healthy static IP address from the other isolated
126
-
network zone.</p>
127
-
</dd>
128
-
<dt>Listener</dt>
129
-
<dd>
130
-
<p>A listener processes inbound connections from clients to Global Accelerator, based on the port (or port range)
131
-
and protocol (or protocols) that you configure. A listener can be configured for TCP, UDP, or both TCP and UDP protocols. Each
132
-
listener has one or more endpoint groups associated with it, and traffic is forwarded
133
-
to endpoints in one of the groups. You associate endpoint groups with listeners by specifying the Regions that you
134
-
want to distribute traffic to. With a standard accelerator, traffic is distributed to optimal endpoints within the endpoint
135
-
groups associated with a listener.</p>
136
-
</dd>
137
-
<dt>Endpoint group</dt>
138
-
<dd>
139
-
<p>Each endpoint group is associated with a specific AWS Region. Endpoint groups include one or
140
-
more endpoints in the Region. With a standard accelerator, you can increase or reduce the percentage of
141
-
traffic that would be otherwise directed to an endpoint group by adjusting a
142
-
setting called a <i>traffic dial</i>. The traffic dial lets
143
-
you easily do performance testing or blue/green deployment testing, for example, for new
144
-
releases across different AWS Regions. </p>
145
-
</dd>
146
-
<dt>Endpoint</dt>
147
-
<dd>
148
-
<p>An endpoint is a resource that Global Accelerator directs traffic to.</p>
149
-
<p>Endpoints for standard accelerators can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP
150
-
addresses. An Application Load Balancer endpoint can be internet-facing or internal. Traffic for
151
-
standard accelerators is routed to endpoints based on the health of the
152
-
endpoint along with configuration options that you choose, such as endpoint
153
-
weights. For each endpoint, you can configure weights, which are numbers
154
-
that you can use to specify the proportion of traffic to route to each one.
155
-
This can be useful, for example, to do performance testing within a
156
-
Region.</p>
157
-
<p>Endpoints for custom routing accelerators are virtual private cloud (VPC) subnets with one
158
-
or many EC2 instances.</p>
159
-
</dd>
160
-
</dl>
62
+
<p>For more information about understanding and using Global Accelerator, see the
0 commit comments