id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
bedf6aca71ae-3
|
You can use an AWS Organizations service control policy \(SCP\) to apply a permissions boundary to an AWS Organizations organization or organizational unit \(OU\)\.
**IAM users or roles**
You can use a managed policy for a user's or role's permissions boundary\. For more information, see [Permissions Boundaries for IAM Entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries) in the *IAM User Guide*\.
**Topics**
+ [Identity\-based Policies](#auth_access_manage-access-intro-identity-policies)
+ [Resource\-based Policies](#auth_access_manage-access-intro-resource-policies)
+ [Policy Access\-Level Classifications](#auth_access_policies-access-level)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
0842b913a6e9-0
|
You can attach policies to IAM identities\. For example, you can do the following:
**Attach a permissions policy to a user or a group in your account**
To grant a user permissions to create an AWS Global Accelerator resource, such as an accelerator, you can attach a permissions policy to a user or a group to which the user belongs\.
**Attach a permissions policy to a role \(grant cross\-account permissions\)**
You can attach an identity\-based permissions policy to an IAM role to grant cross\-account permissions\. For example, the administrator in account A can create a role to grant cross\-account permissions to another AWS account \(for example, account B\) or an AWS service as follows:
1. Account A administrator creates an IAM role and attaches a permissions policy to the role that grants permissions on resources in account A\.
1. Account A administrator attaches a trust policy to the role identifying account B as the principal who can assume the role\.
1. Account B administrator can then delegate permissions to assume the role to any users in account B\. Doing this allows users in account B to create or access resources in account A\. The principal in the trust policy can also be an AWS service principal if you want to grant an AWS service permissions to assume the role\.
For more information about using IAM to delegate permissions, see [Access Management](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) in the *IAM User Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
0842b913a6e9-1
|
For more information about users, groups, roles, and permissions, see [Identities \(Users, Groups, and Roles\)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id.html) in the *IAM User Guide*\.
The following are two examples of policies that you could use with Global Accelerator The first example policy grants a user programmatic access to all List and Describe actions for accelerators in your AWS account:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"globalaccelerator:List*",
"globalaccelerator:Describe*"
],
"Resource": "*"
}
]
}
```
The following example grants programmatic access to the `ListAccelerators` operation:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"globalaccelerator:ListAccelerators",
],
"Resource": "*"
}
]
}
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
8dc16a13ba8f-0
|
Resource\-based policies are JSON policy documents that you attach to a resource\. These policies allow you to specify what actions a specified principal can perform on that resource and under what conditions\. The most common resource\-based policy is for an Amazon S3 bucket\. Resource\-based policies are inline policies that exist only on the resource\. There are no managed resource\-based policies\.
Granting permissions to members of other AWS accounts using a resource\-based policy has some advantages over an IAM role\. For more information, see [How IAM Roles Differ from Resource\-based Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_compare-resource-policies.html) in the *IAM User Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
eb8afd94bc4f-0
|
In the IAM console, actions are grouped using the following access\-level classifications:
**List**
Provides permission to list resources within the service to determine whether an object exists\. Actions with this level of access can list objects but cannot see the contents of a resource\. Most actions with the **List** access level cannot be performed on a specific resource\. When you create a policy statement with these actions, you must specify **All resources** \(`"*"`\)\.
**Read**
Provides permission to read but not edit the contents and attributes of resources in the service\. For example, the Amazon S3 operations `GetObject` and `GetBucketLocation` have the **Read** access level\.
**Write**
Provides permission to create, delete, or modify resources in the service\. For example, the Amazon S3 operations `CreateBucket`, `DeleteBucket`, and `PutObject` have the **Write** access level\.
**Permissions management**
Provides permission to grant or modify resource permissions in the service\. For example, most IAM and AWS Organizations policy actions have the **Permissions management** access level\.
**Tip**
To improve the security of your AWS account, restrict or regularly monitor policies that include the **Permissions management** access\-level classification\.
**Tagging**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
eb8afd94bc4f-1
|
**Tagging**
Provides permission to create, delete, or modify tags that are attached to a resource in the service\. For example, the Amazon EC2 `CreateTags` and `DeleteTags` operations have the **Tagging** access level\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_what-are-policies.md
|
b427de2557d9-0
|
When you create an accelerator, Global Accelerator provisions two static IP addresses for you\. It also assigns a default Domain Name System \(DNS\) name to your accelerator, similar to `a1234567890abcdef.awsglobalaccelerator.com`, that points to the static IP addresses\. The static IP addresses are advertised globally using anycast from the AWS edge network to your endpoints such as Network Load Balancers, Application Load Balancers, EC2 instances, or Elastic IP addresses\. You can use your accelerator's static IP addresses or DNS name to route traffic to your accelerator\. DNS servers and DNS resolvers use a round robin to resolve the DNS name for an accelerator, so the name resolves to the static IP addresses for the accelerator, returned by Amazon Route 53 in random order\. Clients typically use the first IP address that is returned\.
**Note**
Global Accelerator creates two Pointer \(PTR\) records that map an accelerator’s static IP addresses to the corresponding DNS name generated by Global Accelerator, to support reverse DNS lookup\. This is also known as a reverse hosted zone\. Be aware that the DNS name that Global Accelerator generates for you isn't configurable, and you can't create PTR records that point to your custom domain name\. Global Accelerator also does not create PTR records for static IP addresses from an IP address range that you bring to AWS \(BYOIP\)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.dns-addressing.md
|
bc710c2f2d29-0
|
AWS Global Accelerator automatically checks the health of the endpoints that are associated with your static IP addresses, and then directs user traffic only to healthy endpoints\.
If you've configured custom health check settings—in Global Accelerator or by configuring settings directly for Network Load Balancer or Application Load Balancer load balancers—Global Accelerator uses those settings as follows:
+ For Network Load Balancer and Application Load Balancer endpoints, Global Accelerator follows the health check settings that you've configured for the load balancers on the Elastic Load Balancing console\.
+ For Elastic IP address endpoints, you can configure custom health check settings in Global Accelerator\. By default, Global Accelerator uses the listener port and protocol for health checks\. For UDP listeners with Elastic IP address endpoints, Global Accelerator uses the listener port and the TCP protocol for health checks, so you must have a TCP server on your endpoint\.
When you add an endpoint, it must pass a health check to be considered healthy before traffic is directed to it\. If Global Accelerator doesn’t have any healthy endpoints to route traffic to, it routes requests to all endpoints\.
Global Accelerator includes default health checks that are run automatically, but you can configure the timing for the checks and other options\. For more information, see [Health Check Options](about-endpoint-groups-health-check-options.md)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoint-groups-automatic-health-checks.md
|
072829d54eff-0
|
AWS Global Accelerator is a service in which you create *accelerators* to improve availability and performance of your applications for local and global users\. Global Accelerator directs traffic to optimal endpoints over the AWS global network\. This improves the availability and performance of your internet applications that are used by a global audience\. Global Accelerator is a global service that supports endpoints in multiple AWS Regions, which are listed in the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)\.
By default, Global Accelerator provides you with two static IP addresses that you associate with your accelerator\. \(Or, 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 and distribute incoming application traffic across multiple endpoint resources in multiple AWS Regions, which increases the availability of your applications\. Endpoints 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\.
**Important**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/what-is-global-accelerator.md
|
072829d54eff-1
|
**Important**
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 *delete* 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 with Global Accelerator, for example, tag\-based permissions, to limit the users who have permissions to delete an accelerator\. For more information, see [ Tag\-based policies](auth-and-access-control.md#access-control-manage-access-tag-policies)\.
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\.
For a list of the AWS Regions where Global Accelerator and other services are currently supported, see the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)\.
**Topics**
+ [AWS Global Accelerator components](introduction-components.md)
+ [How AWS Global Accelerator works](introduction-how-it-works.md)
+ [Location and IP address ranges of Global Accelerator edge servers](introduction-ip-ranges.md)
+ [AWS Global Accelerator use cases](introduction-benefits-of-migrating.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/what-is-global-accelerator.md
|
072829d54eff-2
|
+ [AWS Global Accelerator use cases](introduction-benefits-of-migrating.md)
+ [AWS Global Accelerator Speed Comparison Tool](introduction-speed-comparison-tool.md)
+ [How to get started with AWS Global Accelerator](introduction-get-started.md)
+ [Tagging in AWS Global Accelerator](tagging-in-global-accelerator.md)
+ [Pricing for AWS Global Accelerator](introduction-pricing.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/what-is-global-accelerator.md
|
2d1cb82d836b-0
|
There are two ways that you can customize how AWS Global Accelerator sends traffic to your endpoints:
+ Change the traffic dial to cap the traffic for one or more endpoint groups
+ Specify weights to change the proportion of traffic to the endpoints in a group
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-traffic-dials-weights.md
|
991c78c42754-0
|
For each endpoint group in an accelerator, you can set a traffic dial to control the percentage of traffic that is sent to the endpoint group\. The percentage is applied only to traffic that is already directed to the endpoint group, not to all listener traffic\.
The traffic dial limits the portion of traffic that an endpoint group accepts, expressed as a percentage of traffic directed to that endpoint group\. For example, if you set the traffic dial for an endpoint group in US\-East\-1 to 50 \(that is, 50%\) and the accelerator directs 100 user requests to that endpoint group, only 50 requests are accepted by the group\. The accelerator directs the remaining 50 requests to endpoint groups in other Regions\.
For more information, see [Adjusting Traffic Flow With Traffic Dials](about-endpoint-groups-traffic-dial.md)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-traffic-dials-weights.md
|
c7ff40bdcefd-0
|
For each endpoint, you can specify weights, which are numbers that change the proportion of traffic that the accelerator routes to each endpoint\. This can be useful, for example, to do performance testing within a Region\.
A weight is a value that determines the proportion of traffic that the accelerator directs to an endpoint\. By default, the weight for an endpoint is 128—that is, half of the maximum value for a weight, 255\.
The accelerator calculates the sum of the weights for the endpoints in an endpoint group, and then directs traffic to the endpoints based on the ratio of each endpoint's weight to the total\. For an example of how weights work, see [Endpoint Weights](about-endpoints-endpoint-weights.md)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-traffic-dials-weights.md
|
47fa06858d52-0
|
Traffic dials and weights affect how the accelerator serves traffic in different ways:
+ You configure traffic dials for *endpoint groups*\. The traffic dial lets you cut off a percentage of traffic—or all traffic—to the group, by "dialing down" traffic that the accelerator has already directed to it based on other factors, such as proximity\.
+ You use weights, on the other hand, to set values for *individual endpoints* within an endpoint group\. Weights provide a way to divide up traffic within the endpoint group—for example, if you want to do performance testing for specific endpoints in a Region\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-traffic-dials-weights.md
|
642f84b66e22-0
|
Endpoints in AWS Global Accelerator can be Network Load Balancers, Application Load Balancers, Amazon EC2 instances, or Elastic IP addresses\. A static IP address serves as a single point of contact for clients, and Global Accelerator then distributes incoming traffic across healthy endpoints\. Global Accelerator directs traffic to endpoints by using the port \(or port range\) that you specify for the listener that the endpoint group for the endpoint belongs to\.
Each endpoint group can have multiple endpoints\. You can add each endpoint to multiple endpoint groups, but the endpoint groups must be associated with different listeners\.
Global Accelerator continually monitors the health of all endpoints that are included in an endpoint group\. It routes traffic only to the active endpoints that are healthy\. If Global Accelerator doesn’t have any healthy endpoints to route traffic to, it routes traffic to all endpoints\.
Be aware of the following for specific types of Global Accelerator endpoints:
**Load balancer endpoints**
+ An Application Load Balancer endpoint can be internet\-facing or internal\. A Network Load Balancer endpoint must be internet\-facing\.
**Amazon EC2 instance endpoints**
+ An EC2 instance endpoint can't be one of the following types: C1, CC1, CC2, CG1, CG2, CR1, CS1, G1, G2, HI1, HS1, M1, M2, M3, or T1\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoints.md
|
642f84b66e22-1
|
+ EC2 instances are supported as endpoints in only some AWS Regions\. For a list of supported Regions, see [Supported AWS Regions for client IP address preservation](preserve-client-ip-address.regions.md)\.
+ We recommend that you remove an EC2 instance from Global Accelerator endpoint groups before you terminate the instance\. If you terminate an EC2 instance before you remove it from an endpoint group in Global Accelerator, and then you create another instance in the same VPC with the same private IP address, and health checks pass, Global Accelerator will route traffic to the new endpoint\.
**Topics**
+ [Adding, editing, or removing an endpoint](about-endpoints-adding-endpoints.md)
+ [Endpoint weights](about-endpoints-endpoint-weights.md)
+ [Adding endpoints with client IP address preservation](#about-endpoints-sipp-caveats)
+ [Transitioning endpoints to use client IP address preservation](about-endpoints.transition-to-IP-preservation.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoints.md
|
d3cafe996627-0
|
A feature that you can use with some endpoint types—in some Regions— is *client IP address preservation*\. With this feature, you preserve the source IP address of the original client for packets that arrive at the endpoint\. You can use this feature with Application Load Balancer and EC2 instance endpoints\. For more information, see [Preserve client IP addresses in AWS Global Accelerator](preserve-client-ip-address.md)\.
If you intend to use the client IP address preservation feature, be aware of the following when you add endpoints to Global Accelerator:
**Elastic network interfaces**
To support client IP address preservation, Global Accelerator creates elastic network interfaces in your AWS account—one for each subnet where an endpoint is present\. For more information about how Global Accelerator works with elastic network interfaces, see [Best practices for client IP address preservation](best-practices-aga.md)\.
**Endpoints in private subnets**
You can target an Application Load Balancer or an EC2 instance in a private subnet using AWS Global Accelerator but you must have an [internet gateway](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html) attached to the VPC that contains the endpoints\. For more information, see [Secure VPC connections in AWS Global Accelerator](secure-vpc-connections.md)\.
**Add the client IP address to the allow list**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoints.md
|
d3cafe996627-1
|
**Add the client IP address to the allow list**
Before you add and begin to route traffic to endpoints that preserve the client IP address, make sure that all your required security configurations, for example, security groups, are updated to include the user client IP address on the allow list\. Network access control lists \(ACLs\) only apply to egress \(outbound\) traffic\. If you need to filter ingress \(inbound\) traffic, you must use security groups\.
**Configure network access control lists \(ACLs\)**
Network ACLs associated with your VPC subnets apply to egress \(outbound\) traffic when client IP address preservation is enabled on your accelerator\. However, for traffic to be allowed to exit through Global Accelerator, you must configure the ACL as both an inbound and outbound rule\.
For example, to allow TCP and UDP clients using an ephemeral source port to connect to your endpoint through Global Accelerator, associate the subnet of your endpoint with a Network ACL that allows outbound traffic destined to an ephemeral TCP or UDP port \(port range 1024\-65535, destination 0\.0\.0\.0/0\)\. In addition, create a matching inbound rule \(port range 1024\-65535, source 0\.0\.0\.0/0\)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoints.md
|
d3cafe996627-2
|
Security group and AWS WAF rules are an additional set of capabilities that you can apply to protect your resources\. For example, the inbound security group rules associated with your Amazon EC2 instances and Application Load Balancers allow you to control the destination ports that clients can connect to through Global Accelerator, such as port 80 for HTTP or port 443 for HTTPS\. Note that Amazon EC2 instance security groups apply to any traffic that arrives to your instances, including traffic from Global Accelerator and any public or Elastic IP address that is assigned to your instance\. As a best practice, use private subnets if you want to ensure that traffic is delivered only by Global Accelerator\. Also make sure that the inbound security group rules are configured appropriately to correctly allow or deny traffic for your applications\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoints.md
|
5dd66122eafc-0
|
When you create an Application Load Balancer in the AWS Management Console, you can optionally [ add an accelerator at the same time](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-application-load-balancer.html)\. Elastic Load Balancing and Global Accelerator work together to transparently add the accelerator for you\. The accelerator is created in your account, with the load balancer as an endpoint\. Using an accelerator provides static IP addresses and improves the availability and performance of your applications\.
**Important**
To create an accelerator, you must have the correct permissions in place\. For more information, see [Permissions required for console access, authentication management, and access control](auth-and-access-control.md#auth_access_required-permissions)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.alb-accelerator.md
|
c48b3533f7c1-0
|
You must update your DNS configuration to direct traffic to the static IP addresses or DNS name for the accelerator\. Traffic won't go through the accelerator to your load balancer until your configuration changes are complete\.
After you create your load balancer by choosing the Global Accelerator add\-on on the Amazon EC2 console, go to the **Integrated services** tab to see the static IP addresses and Domain Name System \(DNS\) name for your accelerator\. You use this information to start routing user traffic to the load balancer over the AWS global network\. For more information about the DNS name assigned to your accelerator, see [Support for DNS addressing in Global Accelerator](about-accelerators.dns-addressing.md)\.
You can view and configure your accelerator by [ navigating to Global Accelerator](https://us-west-2.console.aws.amazon.com/ec2/v2/home?region=us-west-2#GlobalAccelerator:) in the AWS Management Console\. For example, you can see the accelerators that are associated with your account or add additional load balancers to your accelerator\. For more information, see [Viewing your accelerators](about-accelerators.viewing.md) and [ Creating or updating an accelerator](about-accelerators.creating-editing.md)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.alb-accelerator.md
|
7c03f8eb995c-0
|
With AWS Global Accelerator, you pay only for what you use\. You are charged an hourly rate and data transfer costs for each accelerator in your account\. For more information, see [ AWS Global Accelerator Pricing](https://aws.amazon.com/global-accelerator/pricing)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.alb-accelerator.md
|
7e4edacf63a3-0
|
If you'd like to stop routing traffic through Global Accelerator to your load balancer, do the following:
1. Update your DNS configuration to point your traffic directly to the load balancer\.
1. Delete the load balancer from the accelerator\. For more information, see *To remove an endpoint* in [Adding, editing, or removing an endpoint](about-endpoints-adding-endpoints.md)\.
1. Delete the accelerator\. For more information, see [ Deleting an accelerator](about-accelerators.deleting.md)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.alb-accelerator.md
|
7916aff01468-0
|
The information and resources listed here can help you learn more about Global Accelerator\.
**Topics**
+ [Additional AWS Global Accelerator documentation](#related-information.global-accelerator-documentation)
+ [Getting support](#related-information.support)
+ [Tips from the Amazon Web Services Blog](#resources-aws-blog-tips)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/Resources.md
|
de8395d8ac65-0
|
The following related resources can help you as you work with this service\.
+ [AWS Global Accelerator API Reference](https://docs.aws.amazon.com/global-accelerator/latest/api/) – Gives complete descriptions of the API actions, parameters, and data types, and a list of errors that the service returns\.
+ [AWS Global Accelerator product information](http://aws.amazon.com/global-accelerator/) – The primary web page for information about Global Accelerator, including features and pricing information\.
+ [Terms of Use](http://aws.amazon.com/terms/) – Detailed information about our copyright and trademark; your account, license, and site access; and other topics\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/Resources.md
|
790ac44ae9e4-0
|
Support for Global Accelerator is available in several forms\.
+ [Discussion forums](https://forums.aws.amazon.com/forum.jspa?forumID=312) – A community\-based forum for developers to discuss technical questions related to Global Accelerator\.
+ [AWS Support Center](https://console.aws.amazon.com/support/home#/) – This site brings together information about your recent support cases and results from AWS Trusted Advisor and health checks, as well as providing links to discussion forums, technical FAQs, the service health dashboard, and information about AWS support plans\.
+ [AWS Premium Support Information](https://aws.amazon.com/premiumsupport/) – The primary web page for information about AWS Premium Support, a one\-on\-one, fast\-response support channel to help you build and run applications on AWS Infrastructure Services\.
+ [Contact Us](http://aws.amazon.com/contact-us/) – Links for inquiring about your billing or account\. For technical questions, use the discussion forums or support links above\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/Resources.md
|
68b103335b24-0
|
The AWS Blog has a number of posts to help you use AWS services\. For example, see the following blog posts about Global Accelerator:
+ [ AWS Global Accelerator for Availability and Performance](https://aws.amazon.com/blogs/startups/how-to-accelerate-your-wordpress-site-with-amazon-cloudfront/)
+ [ Traffic management with AWS Global Accelerator](https://aws.amazon.com/blogs/networking-and-content-delivery/traffic-management-with-aws-global-accelerator/)
+ [ Analyzing and visualizing AWS Global Accelerator flow logs using Amazon Athena and Amazon QuickSight](https://aws.amazon.com/blogs/networking-and-content-delivery/analyzing-and-visualizing-aws-global-accelerator-flow-logs-using-amazon-athena-and-amazon-quicksight/)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/Resources.md
|
4f04502ea605-0
|
-----
*****Copyright © 2020 Amazon Web Services, Inc. and/or its affiliates. All rights reserved.*****
-----
Amazon's trademarks and trade dress may not be used in
connection with any product or service that is not Amazon's,
in any manner that is likely to cause confusion among customers,
or in any manner that disparages or discredits Amazon. All other
trademarks not owned by Amazon are the property of their respective
owners, who may or may not be affiliated with, connected to, or
sponsored by Amazon.
-----
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/index.md
|
b5d3ed6f4266-0
|
+ [What is AWS Global Accelerator?](what-is-global-accelerator.md)
+ [AWS Global Accelerator components](introduction-components.md)
+ [How AWS Global Accelerator works](introduction-how-it-works.md)
+ [Location and IP address ranges of Global Accelerator edge servers](introduction-ip-ranges.md)
+ [AWS Global Accelerator use cases](introduction-benefits-of-migrating.md)
+ [AWS Global Accelerator Speed Comparison Tool](introduction-speed-comparison-tool.md)
+ [How to get started with AWS Global Accelerator](introduction-get-started.md)
+ [Tagging in AWS Global Accelerator](tagging-in-global-accelerator.md)
+ [Pricing for AWS Global Accelerator](introduction-pricing.md)
+ [Getting started with AWS Global Accelerator](getting-started.md)
+ [Common actions that you can use with AWS Global Accelerator](global-accelerator-actions.md)
+ [Accelerators in AWS Global Accelerator](about-accelerators.md)
+ [Creating or updating an accelerator](about-accelerators.creating-editing.md)
+ [Deleting an accelerator](about-accelerators.deleting.md)
+ [Viewing your accelerators](about-accelerators.viewing.md)
+ [Add an accelerator when you create a load balancer](about-accelerators.alb-accelerator.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/index.md
|
b5d3ed6f4266-1
|
+ [Add an accelerator when you create a load balancer](about-accelerators.alb-accelerator.md)
+ [Bring your own IP addresses (BYOIP) in AWS Global Accelerator](using-byoip.md)
+ [Support for DNS addressing in Global Accelerator](about-accelerators.dns-addressing.md)
+ [Route custom domain traffic to your accelerator](about-accelerators.mapping-your-custom-domain.md)
+ [Listeners in AWS Global Accelerator](about-listeners.md)
+ [Adding, editing, or removing a listener](about-listeners.creating-listeners.md)
+ [Client affinity](about-listeners-client-affinity.md)
+ [Endpoint groups in AWS Global Accelerator](about-endpoint-groups.md)
+ [Adding, editing, or removing an endpoint group](about-endpoint-groups.create-endpoint-group.md)
+ [Adjusting traffic flow with traffic dials](about-endpoint-groups-traffic-dial.md)
+ [Health check options](about-endpoint-groups-health-check-options.md)
+ [Endpoints in AWS Global Accelerator](about-endpoints.md)
+ [Adding, editing, or removing an endpoint](about-endpoints-adding-endpoints.md)
+ [Endpoint weights](about-endpoints-endpoint-weights.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/index.md
|
b5d3ed6f4266-2
|
+ [Endpoint weights](about-endpoints-endpoint-weights.md)
+ [Transitioning endpoints to use client IP address preservation](about-endpoints.transition-to-IP-preservation.md)
+ [Preserve client IP addresses in AWS Global Accelerator](preserve-client-ip-address.md)
+ [How to enable client IP address preservation](preserve-client-ip-address.how-to-enable-preservation.md)
+ [Benefits of client IP address preservation](preserve-client-ip-address.benefits-of-preservation.md)
+ [How the client IP address is preserved in AWS Global Accelerator](preserve-client-ip-address.headers.md)
+ [Best practices for client IP address preservation](best-practices-aga.md)
+ [Supported AWS Regions for client IP address preservation](preserve-client-ip-address.regions.md)
+ [Logging and monitoring in AWS Global Accelerator](monitoring-global-accelerator.md)
+ [Flow logs in AWS Global Accelerator](monitoring-global-accelerator.flow-logs.md)
+ [Using Amazon CloudWatch with AWS Global Accelerator](cloudwatch-monitoring.md)
+ [Using AWS CloudTrail to log AWS Global Accelerator API calls](logging-using-cloudtrail.md)
+ [AWS Global Accelerator security](security.md)
+ [Identity and access management for AWS Global Accelerator](auth-and-access-control.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/index.md
|
b5d3ed6f4266-3
|
+ [Identity and access management for AWS Global Accelerator](auth-and-access-control.md)
+ [Service-linked role for Global Accelerator](using-service-linked-roles.md)
+ [Overview of access and authentication](auth_access_overview.md)
+ [Secure VPC connections in AWS Global Accelerator](secure-vpc-connections.md)
+ [Logging and monitoring in AWS Global Accelerator](logging-and-monitoring.md)
+ [Compliance validation for AWS Global Accelerator](compliance-validation.md)
+ [Resilience in AWS Global Accelerator](disaster-recovery-resiliency.md)
+ [Infrastructure security in AWS Global Accelerator](infrastructure-security.md)
+ [Quotas for AWS Global Accelerator](limits-global-accelerator.md)
+ [AWS Global Accelerator Related information](Resources.md)
+ [Document history](WhatsNew.md)
+ [AWS glossary](glossary.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/index.md
|
92c3aef70299-0
|
AWS Identity and Access Management \(IAM\) is an AWS service that allows you manage access to services and resources securely\. IAM is a feature of your AWS account offered at no additional charge\.
**Note**
Before you start with IAM, review the introductory information on [Authentication and Access Control for AWS Global Accelerator](auth-and-access-control.md)\.
When you first create an AWS account, you begin with a single sign\-in identity that has complete access to all AWS services and resources in the account\. This identity is called the AWS account *root user* and is accessed by signing in with the email address and password that you used to create the account\. We strongly recommend that you do not use the root user for your everyday tasks, even the administrative ones\. Instead, adhere to the [best practice of using the root user only to create your first IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#create-iam-users)\. Then securely lock away the root user credentials and use them to perform only a few account and service management tasks\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
71f8c26411b9-0
|
**To create an IAM user for yourself and add the user to an Administrators group**
1. Use your AWS account email address and password to sign in as the *[AWS account root user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html)* to the IAM console at [https://console\.aws\.amazon\.com/iam/](https://console.aws.amazon.com/iam/)\.
**Note**
We strongly recommend that you adhere to the best practice of using the **Administrator** IAM user below and securely lock away the root user credentials\. Sign in as the root user only to perform a few [account and service management tasks](https://docs.aws.amazon.com/general/latest/gr/aws_tasks-that-require-root.html)\.
1. In the navigation pane of the console, choose **Users**, and then choose **Add user**\.
1. For **User name**, type **Administrator**\.
1. Select the check box next to **AWS Management Console access**, select **Custom password**, and then type the new user's password in the text box\. You can optionally select **Require password reset** to force the user to create a new password the next time the user signs in\.
1. Choose **Next: Permissions**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
71f8c26411b9-1
|
1. Choose **Next: Permissions**\.
1. On the **Set permissions** page, choose **Add user to group**\.
1. Choose **Create group**\.
1. In the **Create group** dialog box, for **Group name** type **Administrators**\.
1. For **Filter policies**, select the check box for **AWS managed \- job function**\.
1. In the policy list, select the check box for **AdministratorAccess**\. Then choose **Create group**\.
1. Back in the list of groups, select the check box for your new group\. Choose **Refresh** if necessary to see the group in the list\.
1. Choose **Next: Tags** to add metadata to the user by attaching tags as key\-value pairs\.
1. Choose **Next: Review** to see the list of group memberships to be added to the new user\. When you are ready to proceed, choose **Create user**\.
You can use this same process to create more groups and users, and to give your users access to your AWS account resources\. To learn about using policies to restrict users' permissions to specific AWS resources, go to [Access Management](https://docs.aws.amazon.com/IAM/latest/UserGuide/access.html) and [Example Policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-0
|
To support multiple users in your AWS account, you must delegate permission to allow other people to perform only the actions that you want to allow\. To do this, create an IAM group with the permissions those people need and then add IAM users to the necessary groups as you create them\. You can use this process to set up the groups, users, and permissions for your entire AWS account\. This solution is best used by small and medium organizations where an AWS administrator can manually manage the users and groups\. For large organizations, you can use [custom IAM roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-custom-url.html), [federation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers.html), or [single sign\-on](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html)\.
In the following procedure, you create three users named **arnav**, **carlos**, and **martha** and attach a policy that grants permission to create an accelerator named **my\-example\-accelerator**, but only within the next 30 days\. You can use the steps provided here to add users with different permissions\.
**To create a delegated user for someone else \(console\)**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-1
|
**To create a delegated user for someone else \(console\)**
1. Sign in to the AWS Management Console and open the IAM console at [https://console\.aws\.amazon\.com/iam/](https://console.aws.amazon.com/iam/)\.
1. In the navigation pane, choose **Users**, and then choose **Add user**\.
1. For **User name**, enter **arnav**\.
1. Choose **Add another user** and enter **carlos** for the second user\. Then choose **Add another user** and enter **martha** for the third user\.
1. Select the check box next to **AWS Management Console access**, and then select **Autogenerated password**\.
1. Clear the check box next to **User must create a new password at next sign\-in** to allow the new user to reset their password after they sign in\.
1. Choose **Next: Permissions**\.
1. Choose **Attach existing policies directly**\. You will create a new managed policy for the users\.
1. Choose **Create policy**\.
The **Create policy** wizard opens in a new tab or browser window\.
1. On the **Visual editor** tab, choose **Choose a service**\. Then choose Global Accelerator\. You can use the search box at the top to limit the results in the list of services\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-2
|
The **Service** section closes, and the **Actions** section opens automatically\.
1. Choose the Global Accelerator actions that you want to allow\. For example, to grants permission to create an accelerator, enter **`globalaccelerator:CreateAccelerator`** in the **Filter actions** text box\. When the list of Global Accelerator actions is filtered, select the check box next to **`globalaccelerator:CreateAccelerator`**\.
The Global Accelerator actions are grouped by access\-level classification to make it easy for you to quickly determine the level of access that each action provides\. For more information, see [Policy Access\-Level Classifications](auth_access_what-are-policies.md#auth_access_policies-access-level)\.
1. If the actions that you selected in the preceding steps do not support choosing specific resources, then **All resources** is selected for you\. In that case, you cannot edit this section\.
If you chose one or more actions that support resource\-level permissions, then the visual editor lists those resource types in the **Resources** section\. Choose **You chose actions that require the **accelerator** resource type** to choose whether you want to enter a specific accelerator for your policy\.
1. If you want to allow the `globalaccelerator:CreateAccelerator` action for all resources, choose **All resources**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-3
|
1. If you want to allow the `globalaccelerator:CreateAccelerator` action for all resources, choose **All resources**\.
If you want to specify a resource, choose **Add ARN**\. Specify the region and account ID \(or account ID\) \(or choose **Any**\), and then enter **my\-example\-accelerator** for the resource\. Then choose **Add**\.
1. Choose **Specify request conditions \(optional\)**\.
1. Choose **Add condition** to grants permission to create an accelerator within the next 7 days\. Assume that today's date is January 1, 2019\.
1. For **Condition Key**, choose **aws:CurrentTime**\. This condition key checks the date and time that the user makes the request\. It returns true \(and therefore allows the **`globalaccelerator:CreateAccelerator`** action only if the date and time are within the specified range\.
1. For **Qualifier**, keep the default value\.
1. To specify the start of the allowed date and time range, for **Operator**, choose **DateGreaterThan**\. Then for **Value**, enter **2019\-01\-01T00:00:00Z**\.
1. Choose **Add** to save your condition\.
1. Choose **Add another condition** to specify the end date\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-4
|
1. Choose **Add** to save your condition\.
1. Choose **Add another condition** to specify the end date\.
1. Follow similar steps to specify the end of the allowed date and time range\. For **Condition Key**, choose **aws:CurrentTime**\. For **Operator**, choose **DateLessThan**\. For **Value**, enter **2019\-01\-06T23:59:59Z**, seven days after the first date\. Then choose **Add** to save your condition\.
1. \(Optional\) To see the JSON policy document for the policy that you are creating, choose the **JSON** tab\. You can switch between the **Visual editor** and **JSON** tabs any time\. However, if you make changes or choose **Review policy** in the **Visual editor** tab, IAM might restructure your policy to optimize it for the visual editor\. For more information, see [Policy Restructuring](https://docs.aws.amazon.com/IAM/latest/UserGuide/troubleshoot_policies.html#troubleshoot_viseditor-restructure) in the *IAM User Guide*\.
1. When you are finished, choose **Review policy**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a8a400d8979b-5
|
1. When you are finished, choose **Review policy**\.
1. On the **Review policy** page, for **Name**, enter **`globalaccelerator:CreateAccelerator`Policy**\. For **Description**, enter **Policy to grants permission to create an accelerator**\. Review the policy summary to make sure that you have granted the intended permissions, and then choose **Create policy** to save your new policy\.
1. Return to the original tab or window, and refresh your list of policies\.
1. In the search box, enter **`globalaccelerator:CreateAccelerator`Policy**\. Select the check box next to your new policy\. Then choose **Next Step**\.
1. Choose **Next: Review** to preview your new users\. When you are ready to proceed, choose **Create users**\.
1. Download or copy the passwords for your new users and deliver them to the users securely\. Separately, provide your users with a [link to your IAM user console page](https://docs.aws.amazon.com/IAM/latest/UserGuide/console.html#user-sign-in-page) and the user names that you just created\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-0
|
You must have physical access to the hardware that will host the user's virtual MFA device in order to configure MFA\. For example, you might configure MFA for a user who will use a virtual MFA device running on a smartphone\. In that case, you must have the smartphone available in order to finish the wizard\. Because of this, you might want to let users configure and manage their own virtual MFA devices\. In that case, you must grant users the permissions to perform the necessary IAM actions\.
**To create a policy to allow credential self\-management \(console\)**
1. Sign in to the AWS Management Console and open the IAM console at [https://console\.aws\.amazon\.com/iam/](https://console.aws.amazon.com/iam/)\.
1. In the navigation pane, choose **Policies**, and then choose **Create policy**\.
1. Choose the **JSON** tab and copy the text from the following JSON policy document\. Paste this text into the **JSON** text box\.
**Important**
This example policy does not allow users to reset their password while signing in\. New users and users with an expired password might try to do so\. You can allow this by adding `iam:ChangePassword` and `iam:CreateLoginProfile` to the statement `BlockMostAccessUnlessSignedInWithMFA`\. However, IAM does not recommend this\.
```
{
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-1
|
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowAllUsersToListAccounts",
"Effect": "Allow",
"Action": [
"iam:ListAccountAliases",
"iam:ListUsers",
"iam:ListVirtualMFADevices",
"iam:GetAccountPasswordPolicy",
"iam:GetAccountSummary"
],
"Resource": "*"
},
{
"Sid": "AllowIndividualUserToSeeAndManageOnlyTheirOwnAccountInformation",
"Effect": "Allow",
"Action": [
"iam:ChangePassword",
"iam:CreateAccessKey",
"iam:CreateLoginProfile",
"iam:DeleteAccessKey",
"iam:DeleteLoginProfile",
"iam:GetLoginProfile",
"iam:ListAccessKeys",
"iam:UpdateAccessKey",
"iam:UpdateLoginProfile",
"iam:ListSigningCertificates",
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-2
|
"iam:UpdateLoginProfile",
"iam:ListSigningCertificates",
"iam:DeleteSigningCertificate",
"iam:UpdateSigningCertificate",
"iam:UploadSigningCertificate",
"iam:ListSSHPublicKeys",
"iam:GetSSHPublicKey",
"iam:DeleteSSHPublicKey",
"iam:UpdateSSHPublicKey",
"iam:UploadSSHPublicKey"
],
"Resource": "arn:aws:iam::*:user/${aws:username}"
},
{
"Sid": "AllowIndividualUserToViewAndManageTheirOwnMFA",
"Effect": "Allow",
"Action": [
"iam:CreateVirtualMFADevice",
"iam:DeleteVirtualMFADevice",
"iam:EnableMFADevice",
"iam:ListMFADevices",
"iam:ResyncMFADevice"
],
"Resource": [
"arn:aws:iam::*:mfa/${aws:username}",
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-3
|
"Resource": [
"arn:aws:iam::*:mfa/${aws:username}",
"arn:aws:iam::*:user/${aws:username}"
]
},
{
"Sid": "AllowIndividualUserToDeactivateOnlyTheirOwnMFAOnlyWhenUsingMFA",
"Effect": "Allow",
"Action": [
"iam:DeactivateMFADevice"
],
"Resource": [
"arn:aws:iam::*:mfa/${aws:username}",
"arn:aws:iam::*:user/${aws:username}"
],
"Condition": {
"Bool": {
"aws:MultiFactorAuthPresent": "true"
}
}
},
{
"Sid": "BlockMostAccessUnlessSignedInWithMFA",
"Effect": "Deny",
"NotAction": [
"iam:CreateVirtualMFADevice",
"iam:DeleteVirtualMFADevice",
"iam:ListVirtualMFADevices",
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-4
|
"iam:DeleteVirtualMFADevice",
"iam:ListVirtualMFADevices",
"iam:EnableMFADevice",
"iam:ResyncMFADevice",
"iam:ListAccountAliases",
"iam:ListUsers",
"iam:ListSSHPublicKeys",
"iam:ListAccessKeys",
"iam:ListServiceSpecificCredentials",
"iam:ListMFADevices",
"iam:GetAccountSummary",
"sts:GetSessionToken"
],
"Resource": "*",
"Condition": {
"BoolIfExists": {
"aws:MultiFactorAuthPresent": "false"
}
}
}
]
}
```
What does this policy do?
+ The `AllowAllUsersToListAccounts` statement enables the user to see basic information about the account and its users in the IAM console\. These permissions must be in their own statement because they do not support or do not need to specify a specific resource ARN, and instead specify `"Resource" : "*"`\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-5
|
+ The `AllowIndividualUserToSeeAndManageOnlyTheirOwnAccountInformation` statement enables the user to manage his or her own user, password, access keys, signing certificates, SSH public keys, and MFA information in the IAM console\. It also allows users to sign in for the first time in an administrator requires them to set a first\-time password\. The resource ARN limits the use of these permissions to only the user's own IAM user entity\.
+ The `AllowIndividualUserToViewAndManageTheirOwnMFA` statement enables the user to view or manage his or her own MFA device\. Notice that the resource ARNs in this statement allow access to only an MFA device or user that has the same name as the currently signed\-in user\. Users can't create or alter any MFA device other than their own\.
+ The `AllowIndividualUserToDeactivateOnlyTheirOwnMFAOnlyWhenUsingMFA` statement allows the user to deactivate only his or her own MFA device, and only if the user signed in using MFA\. This prevents others with only the access keys \(and not the MFA device\) from deactivating the MFA device and accessing the account\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-6
|
+ The `BlockMostAccessUnlessSignedInWithMFA` statement uses a combination of `"Deny"` and `"NotAction"` to deny access to all but a few actions in IAM and other AWS services ***if*** the user is not signed\-in with MFA\. For more information about the logic for this statement, see [NotAction with Deny](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_notaction.html) in the *IAM User Guide*\. If the user is signed\-in with MFA, then the `"Condition"` test fails and the final "deny" statement has no effect and other policies or statements for the user determine the user's permissions\. This statement ensures that when the user is not signed\-in with MFA, they can perform only the listed actions and only if another statement or policy allows access to those actions\.
The `...IfExists` version of the `Bool` operator ensures that if the `aws:MultiFactorAuthPresent` key is missing, the condition returns true\. This means that a user accessing an API with long\-term credentials, such as an access key, is denied access to the non\-IAM API operations\.
1. When you are finished, choose **Review policy**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
a7c9096cfde3-7
|
1. When you are finished, choose **Review policy**\.
1. On the **Review** page, enter **Force\_MFA** for the policy name\. For the policy description, enter **This policy allows users to manage their own passwords and MFA devices but nothing else unless they authenticate with MFA\.** Review the policy **Summary** to see the permissions granted by your policy, and then choose **Create policy** to save your work\.
The new policy appears in the list of managed policies and is ready to attach\.
**To attach the policy to a user \(console\)**
1. In the navigation pane, choose **Users**\.
1. Choose the name \(not the check box\) of the user you want to edit\.
1. On the **Permissions** tab, choose **Add permissions**\.
1. Choose **Attach existing policies directly**\.
1. In the search box, enter **Force**, and then select the check box next to **Force\_MFA** in the list\. Then choose **Next: Review**\.
1. Review your changes and choose **Add permissions**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
75fbb36e3433-0
|
For increased security, we recommend that all IAM users configure multi\-factor authentication \(MFA\) to help protect your Global Accelerator resources\. MFA adds extra security because it requires users to provide unique authentication from an AWS\-supported MFA device in addition to their regular sign\-in credentials\. The most secure AWS MFA device is the U2F security key\. If your company already has U2F devices, then we recommend that you enable those devices for AWS\. Otherwise, you must purchase a device for each of your users and wait for the hardware to arrive\. For more information, see [Enabling a U2F Security Key](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_enable_u2f.html) in the *IAM User Guide*\.
If you don't already have a U2F device, you can get started quickly and at a low cost by enabling a virtual MFA device\. This requires that you install a software app on an existing phone or other mobile device\. The device generates a six\-digit numeric code based upon a time\-synchronized one\-time password algorithm\. When the user signs in to AWS, they are prompted to enter a code from the device\. Each virtual MFA device assigned to a user must be unique\. A user cannot enter a code from another user's virtual MFA device to authenticate\. For a list of a few supported apps that you can use as virtual MFA devices, see [Multi\-Factor Authentication](http://aws.amazon.com/iam/details/mfa/)\.
**Note**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
75fbb36e3433-1
|
**Note**
You must have physical access to the mobile device that will host the user's virtual MFA device in order to configure MFA for an IAM user\.
**To enable a virtual MFA device for an IAM user \(console\)**
1. Sign in to the AWS Management Console and open the IAM console at [https://console\.aws\.amazon\.com/iam/](https://console.aws.amazon.com/iam/)\.
1. In the navigation pane, choose **Users**\.
1. In the **User Name** list, choose the name of the intended MFA user\.
1. Choose the **Security credentials** tab\. Next to **Assigned MFA device**, choose **Manage**\.
1. In the **Manage MFA Device** wizard, choose **Virtual MFA device**, and then choose **Continue**\.
IAM generates and displays configuration information for the virtual MFA device, including a QR code graphic\. The graphic is a representation of the "secret configuration key" that is available for manual entry on devices that do not support QR codes\.
1. Open your virtual MFA app\.
For a list of apps that you can use for hosting virtual MFA devices, see [Multi\-Factor Authentication](http://aws.amazon.com/iam/details/mfa/)\. If the virtual MFA app supports multiple accounts \(multiple virtual MFA devices\), choose the option to create a new account \(a new virtual MFA device\)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
75fbb36e3433-2
|
1. Determine whether the MFA app supports QR codes, and then do one of the following:
+ From the wizard, choose **Show QR code**, and then use the app to scan the QR code\. For example, you might choose the camera icon or choose an option similar to **Scan code**, and then use the device's camera to scan the code\.
+ In the **Manage MFA Device** wizard, choose **Show secret key**, and then enter the secret key into your MFA app\.
When you are finished, the virtual MFA device starts generating one\-time passwords\.
1. In the **Manage MFA Device** wizard, in the **MFA code 1** box, enter the one\-time password that currently appears in the virtual MFA device\. Wait up to 30 seconds for the device to generate a new one\-time password\. Then enter the second one\-time password into the **MFA code 2** box\. Choose **Assign MFA**\.
**Important**
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
75fbb36e3433-3
|
**Important**
Submit your request immediately after generating the codes\. If you generate the codes and then wait too long to submit the request, the MFA device successfully associates with the user but the MFA device is out of sync\. This happens because time\-based one\-time passwords \(TOTP\) expire after a short period of time\. If this happens, you can resync the device\. For more information, see [Resynchronizing Virtual and Hardware MFA Devices](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_sync.html) in the *IAM User Guide*\.
The virtual MFA device is now ready for use with AWS\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/auth_access_getting-started.md
|
05da1fca1e39-0
|
Flow logs enable you to capture information about the IP address traffic going to and from network interfaces in your accelerator in AWS Global Accelerator\. Flow log data is published to Amazon S3, where you can retrieve and view your data after you've created a flow log\.
Flow logs can help you with a number of tasks\. For example, you can troubleshoot why specific traffic is not reaching an endpoint, which in turn helps you diagnose overly restrictive security group rules\. You can also use flow logs as a security tool to monitor the traffic that is reaching your endpoints\.
A flow log record represents a network flow in your flow log\. Each record captures the network flow for a specific 5\-tuple, for a specific capture window\. A 5\-tuple is a set of five different values that specify the source, destination, and protocol for an IP flow\. The capture window is a duration of time during which the flow logs service aggregates data before publishing flow log records\. The capture window is approximately 10 seconds, but can take up to 1 minute\.
CloudWatch Logs charges apply when using flow logs, even when logs are published directly to Amazon S3\. For more information, see *Deliver Logs to S3* at [Amazon CloudWatch Pricing](https://aws.amazon.com/cloudwatch/pricing/)\.
**Topics**
+ [Publishing flow logs to Amazon S3](#monitoring-global-accelerator.flow-logs-publishing-S3)
+ [Timing of log file delivery](#monitoring-global-accelerator.flow-logs.timing)
+ [Flow log record syntax](#monitoring-global-accelerator.flow-logs.records.syntax)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
d439180387ea-0
|
Flow logs for AWS Global Accelerator are published to Amazon S3 to an existing S3 bucket that you specify\. Flow log records are published to a series of log file objects that are stored in the bucket\.
To create an Amazon S3 bucket for use with flow logs, see [Create a Bucket](https://docs.aws.amazon.com/AmazonS3/latest/gsg/CreatingABucket.html) in the *Amazon Simple Storage Service Getting Started Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
9613544af54e-0
|
Flow logs collect flow log records, consolidate them into log files, and then publish the log files to the Amazon S3 bucket at 5\-minute intervals\. Each log file contains flow log records for the IP address traffic recorded in the previous five minutes\.
The maximum file size for a log file is 75 MB\. If the log file reaches the file size limit within the 5\-minute period, the flow log stops adding flow log records to it, publishes it to the Amazon S3 bucket, and then creates a new log file\.
Log files are saved to the specified Amazon S3 bucket using a folder structure that is determined by the flow log's ID, Region, and the date on which they are created\. The bucket folder structure uses the following format:
```
s3-bucket_name/s3-bucket-prefix/AWSLogs/aws_account_id/globalaccelerator/region/yyyy/mm/dd/
```
Similarly, the log file name is determined by the flow log's ID, Region, and the date and time it was created\. File names use the following format:
```
aws_account_id_globalaccelerator_accelerator_id_flow_log_id_timestamp_hash.log.gz
```
Note the following about the folder and file name structure for log files:
+ The timestamp uses the `YYYYMMDDTHHmmZ` format\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
9613544af54e-1
|
+ The timestamp uses the `YYYYMMDDTHHmmZ` format\.
+ If you specify slash \(/\) for the S3 bucket prefix, the log file bucket folder structure will include a double slash \(//\), like the following:
```
s3-bucket_name//AWSLogs/aws_account_id
```
The following example shows the folder structure and file name of a log file for a flow log created by AWS account `123456789012` for an accelerator with an ID of `1234abcd-abcd-1234-abcd-1234abcdefgh`, on November 23, 2018 at 00:05 UTC:
```
my-s3-bucket/prefix1/AWSLogs/123456789012/globalaccelerator/us-west-2/2018/11/23/123456789012_globalaccelerator_1234abcd-abcd-1234-abcd-1234abcdefgh_20181123T0005Z_1fb1234.log.gz
```
A single flow log file contains interleaved entries with multiple 5\-tuple records; that is, `client_ip`, `client_port`, `accelerator_ip`, `accelerator_port`, `protocol`\. To see all the flow log files for your accelerator, look for entries aggregated by the `accelerator_id` and your `account_id`\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
3ff217a64d27-0
|
An IAM principal, such as an IAM user, must have sufficient permissions to publish flow logs to the Amazon S3 bucket\. The IAM policy must include the following permissions:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "DeliverLogs",
"Effect": "Allow",
"Action": [
"logs:CreateLogDelivery",
"logs:DeleteLogDelivery"
],
"Resource": "*"
},
{
"Sid": "AllowGlobalAcceleratorService",
"Effect": "Allow",
"Action": [
"globalaccelerator:*"
],
"Resource": "*"
},
{
"Sid": "s3Perms",
"Effect": "Allow",
"Action": [
"s3:GetBucketPolicy",
"s3:PutBucketPolicy"
],
"Resource": "*"
}
]
}
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
2ee31ad8414f-0
|
By default, Amazon S3 buckets and the objects that they contain are private\. Only the bucket owner can access the bucket and the objects stored in it\. The bucket owner, however, can grant access to other resources and users by writing an access policy\.
If the user creating the flow log owns the bucket, the service automatically attaches the following policy to the bucket to give the flow log permission to publish logs to it:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AWSLogDeliveryWrite",
"Effect": "Allow",
"Principal": {"Service": "delivery.logs.amazonaws.com"},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::bucket_name/optional_folder/AWSLogs/account_id/*",
"Condition": {"StringEquals": {"s3:x-amz-acl": "bucket-owner-full-control"}}
},
{
"Sid": "AWSLogDeliveryAclCheck",
"Effect": "Allow",
"Principal": {"Service": "delivery.logs.amazonaws.com"},
"Action": "s3:GetBucketAcl",
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
2ee31ad8414f-1
|
"Action": "s3:GetBucketAcl",
"Resource": "arn:aws:s3:::bucket_name"
}
]
}
```
If the user creating the flow log does not own the bucket, or does not have the `GetBucketPolicy` and `PutBucketPolicy` permissions for the bucket, the flow log creation fails\. In this case, the bucket owner must manually add the preceding policy to the bucket and specify the flow log creator's AWS account ID\. For more information, see [How Do I Add an S3 Bucket Policy?](https://docs.aws.amazon.com/AmazonS3/latest/gsg/add-bucket-policy.html) in the *Amazon Simple Storage Service Getting Started Guide*\. If the bucket receives flow logs from multiple accounts, add a `Resource` element entry to the `AWSLogDeliveryWrite` policy statement for each account\.
For example, the following bucket policy allows AWS accounts 123123123123 and 456456456456 to publish flow logs to a folder named `flow-logs` in a bucket named `log-bucket`:
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AWSLogDeliveryWrite",
"Effect": "Allow",
"Principal": {"Service": "delivery.logs.amazonaws.com"},
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
2ee31ad8414f-2
|
"Effect": "Allow",
"Principal": {"Service": "delivery.logs.amazonaws.com"},
"Action": "s3:PutObject",
"Resource": [
"arn:aws:s3:::log-bucket/flow-logs/AWSLogs/123123123123/*",
"arn:aws:s3:::log-bucket/flow-logs/AWSLogs/456456456456/*"
],
"Condition": {"StringEquals": {"s3:x-amz-acl": "bucket-owner-full-control"}}
},
{
"Sid": "AWSLogDeliveryAclCheck",
"Effect": "Allow",
"Principal": {"Service": "delivery.logs.amazonaws.com"},
"Action": "s3:GetBucketAcl",
"Resource": "arn:aws:s3:::log-bucket"
}
]
}
```
**Note**
We recommend that you grant the `AWSLogDeliveryAclCheck` and `AWSLogDeliveryWrite` permissions to the log delivery service principal instead of individual AWS account ARNs\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
aa83c5eb73c2-0
|
If you enabled server\-side encryption for your Amazon S3 bucket using AWS KMS\-managed keys \(SSE\-KMS\) with a customer\-managed customer master key \(CMK\), you must add the following to the key policy for your CMK so that flow logs can write log files to the bucket:
```
{
"Sid": "Allow AWS Global Accelerator Flow Logs to use the key",
"Effect": "Allow",
"Principal": {
"Service": [
"delivery.logs.amazonaws.com"
]
},
"Action": "kms:GenerateDataKey*",
"Resource": "*"
}
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
32dfa7b8e1ec-0
|
In addition to the required bucket policies, Amazon S3 uses access control lists \(ACLs\) to manage access to the log files created by a flow log\. By default, the bucket owner has `FULL_CONTROL` permissions on each log file\. The log delivery owner, if different from the bucket owner, has no permissions\. The log delivery account has `READ` and `WRITE` permissions\. For more information, see [Access Control List \(ACL\)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
32dfa7b8e1ec-1
|
more information, see [Access Control List \(ACL\) Overview](https://docs.aws.amazon.com/AmazonS3/latest/gsg/acl-overview.html) in the *Amazon Simple Storage Service Getting Started Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
feb5e2f7268f-0
|
To enable flow logs in AWS Global Accelerator, follow the steps in this procedure\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
b4165d15916b-0
|
1. Create an Amazon S3 bucket for your flow logs in your AWS account\.
1. Add the required IAM policy for the AWS user who is enabling the flow logs\. For more information, see [IAM roles for publishing flow logs to Amazon S3](#monitoring-global-accelerator.flow-logs-publishing-S3.roles)\.
1. Run the following AWS CLI command, with the Amazon S3 bucket name and prefix that you want to use for your log files:
```
aws globalaccelerator update-accelerator-attributes
--accelerator-arn arn:aws:globalaccelerator::012345678901:accelerator/1234abcd-abcd-1234-abcd-1234abcdefgh
--region us-west-2
--flow-logs-enabled
--flow-logs-s3-bucket s3-bucket-name
--flow-logs-s3-prefix s3-bucket-prefix
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
6ed0f26ba3e6-0
|
The log files are compressed\. If you open the log files using the Amazon S3 console, they are decompressed and the flow log records are displayed\. If you download the files, you must decompress them to view the flow log records\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
27bb3b3af2f1-0
|
AWS Global Accelerator delivers log files for your configured accelerator up to several times an hour\. In general, a log file contains information about the requests that your accelerator received during a given time period\. Global Accelerator usually delivers the log file for that time period to your Amazon S3 bucket within an hour of the events that appear in the log\. Some or all log file entries for a time period can sometimes be delayed by up to 24 hours\. When log entries are delayed, Global Accelerator saves them in a log file for which the file name includes the date and time of the period in which the requests occurred, not the date and time when the file was delivered\.
When creating a log file, Global Accelerator consolidates information for your accelerator from all the edge locations that received requests during the time period that the log file covers\.
Global Accelerator begins to reliably deliver log files about four hours after you enable logging\. You might get a few log files before that time\.
**Note**
If no users connect to your accelerator during the time period, you don't receive any log files for that period\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
66afd9ac0370-0
|
A flow log record is a space\-separated string that has the following format:
`<version> <aws_account_id> <accelerator_id> <client_ip> <client_port> <accelerator_ip> <accelerator_port> <endpoint_ip> <endpoint_port> <protocol> <ip_address_type> <packets> <bytes> <start_time> <end_time> <action> <log-status> <globalaccelerator_source_ip> <globalaccelerator_source_port> <endpoint_region> <globalaccelerator_region> <direction> <vpc_id>`
The Version 1\.0 format does not include the VPC identifier, `vpc_id`\. The Version 2\.0 format, which includes `vpc_id`, is generated when Global Accelerator sends traffic to an endpoint with client IP address preservation\.
The following table describes the fields of a flow log record\.
****
| Field | Description |
| --- | --- |
| `version` | The flow logs version\. |
| `aws_account_id` | The AWS account ID for the flow log\. |
| `accelerator_id` | The ID of the accelerator for which the traffic is recorded\. |
| `client_ip` | The source IPv4 address\. |
| `client_port` | The source port\. |
| `accelerator_ip` | The accelerator's IP address\. |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
66afd9ac0370-1
|
| `client_port` | The source port\. |
| `accelerator_ip` | The accelerator's IP address\. |
| `accelerator_port` | The accelerator's port\. |
| `endpoint_ip` | The destination IP address of the traffic\. |
| `endpoint_port` | The destination port of the traffic\. |
| `protocol` | The IANA protocol number of the traffic\. For more information, see [ Assigned Internet Protocol Numbers](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml)\. |
| `ip_address_type` | IPv4\. |
| `packets` | The number of packets transferred during the capture window\. |
| `bytes` | The number of bytes transferred during the capture window\. |
| `start_time` | The time, in Unix seconds, of the start of the capture window\. |
| `end_time` | The time, in Unix seconds, of the end of the capture window\. |
| `action` | The action associated with the traffic: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.html) |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
66afd9ac0370-2
|
| `log-status` | The logging status of the flow log: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/monitoring-global-accelerator.flow-logs.html) |
| `globalaccelerator_source_ip` | The IP address used by the Global Accelerator network interface\. |
| `globalaccelerator_source_port` | The port used by the Global Accelerator network interface\. |
| `endpoint_region` | The AWS Region where the endpoint is located\. |
| `globalaccelerator_region` | The edge location \(point of presence\) that served the request\. Each edge location has a three\-letter code and an arbitrarily assigned number, for example, DFW3\. The three\-letter code typically corresponds with the International Air Transport Association airport code for an airport near the edge location\. \(These abbreviations might change in the future\.\) |
| `direction` | The direction of the traffic\. Denotes traffic coming into the Global Accelerator network \(`INGRESS`\) or returning to the client \(`EGRESS`\)\. |
| `vpc_id` | The VPC identifier\. Included with Version 2\.0 flow logs when Global Accelerator sends traffic to an endpoint with client IP address preservation\. |
If a field does not apply for a specific record, the record displays a '\-' symbol for that entry\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/monitoring-global-accelerator.flow-logs.md
|
bc8f0994d4c8-0
|
With AWS Global Accelerator, you add listeners that process inbound connections from clients based on the ports and protocols that you specify\. Global Accelerator supports both TCP and UDP protocols\.
You define a listener when you create your accelerator, and you can add more listeners at any time\. You associate each listener with one or more endpoint groups, and you associate each endpoint group with one AWS Region\.
**Topics**
+ [Adding, editing, or removing a listener](about-listeners.creating-listeners.md)
+ [Client affinity](about-listeners-client-affinity.md)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-listeners.md
|
aa90c631d650-0
|
You can use the AWS Global Accelerator Speed Comparison Tool to see Global Accelerator download speeds compared to direct internet downloads, across AWS Regions\. This tool enables you to use your browser to see the performance difference when you transfer data using Global Accelerator\. You choose a file size to download, and the tool downloads files over HTTPS/TCP from Application Load Balancers in different Regions to your browser\. For each Region, you see a direct comparison of the download speeds\.
To access the Speed Comparison Tool, copy the following URL into your browser:
```
https://speedtest.globalaccelerator.aws
```
**Important**
Results may differ when you run the test multiple times\. Download times can vary based on factors that are external to Global Accelerator, such as the quality, capacity, and distance of the connection in the last\-mile network that you're using\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-speed-comparison-tool.md
|
5120efb34531-0
|
For each endpoint group, you can set a traffic dial to control the percentage of traffic that is directed to the group\. The percentage is applied only to traffic that is already directed to the endpoint group, not to all listener traffic\.
By default, the traffic dial is set to 100 \(that is, 100%\) for all regional endpoint groups in an accelerator\. The traffic dial lets you easily do performance testing or blue/green deployment testing for new releases across different AWS Regions, for example\.
Here are a few examples to illustrate how you can use traffic dials to change the traffic flow to endpoint groups\.
**Upgrade your application by Region**
If you want to upgrade an application in a Region or do maintenance, first set the traffic dial to 0 to cut off traffic for the Region\. When you complete the work and you're ready bring the Region back into service, adjust the traffic dial to 100 to dial the traffic back up\.
**Mix traffic between two Regions**
This example shows how traffic flow works when you change the traffic dials for two regional endpoint groups at the same time\. Let’s say that you have two endpoint groups for your accelerator—one for the `us-west-2` Region and one for the `us-east-1` Region—and you've set the traffic dials to 50% for each endpoint group\.
Now, say you have 100 requests coming to your accelerator, with 50 from the East Coast of the United States and 50 from the West Coast\. The accelerator directs the traffic as follows:
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoint-groups-traffic-dial.md
|
5120efb34531-1
|
Now, say you have 100 requests coming to your accelerator, with 50 from the East Coast of the United States and 50 from the West Coast\. The accelerator directs the traffic as follows:
+ The first 25 requests on each coast \(50 requests in total\) are served from their nearby endpoint group\. That is, 25 requests are directed to the endpoint group in `us-west-2` and 25 are directed to the endpoint group in `us-east-1`\.
+ The next 50 requests are directed to the opposite Regions\. That is, the next 25 requests from the East Coast are served by `us-west-2`, and the next 25 requests from the West Coast are served by `us-east-1`\.
The result in this scenario is that both endpoint groups serve the same amount of traffic\. However, each one receives a mix of traffic from both Regions\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-endpoint-groups-traffic-dial.md
|
4f6be6f2f54e-0
|
With AWS Global Accelerator, you pay only for what you use\. You are charged an hourly rate and data transfer costs for each accelerator in your account\. For more information, see [ AWS Global Accelerator Pricing](https://aws.amazon.com/global-accelerator/pricing)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/introduction-pricing.md
|
f577384a1297-0
|
The following table lists common AWS Global Accelerator actions that you can use with Global Accelerator resources\. The table also provides links to relevant documentation\.
| Action | Using the Global Accelerator Console | Using the Global Accelerator API |
| --- | --- | --- |
| Create an accelerator | See [Getting started with AWS Global Accelerator](getting-started.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateAccelerator.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateAccelerator.html) |
| Create a listener | See [Adding, editing, or removing a listener](about-listeners.creating-listeners.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateListener.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateListener.html) |
| Create an endpoint group | See [ Adding, editing, or removing an endpoint group](about-endpoint-groups.create-endpoint-group.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateEndpointGroup.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_CreateEndpointGroup.html) |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/global-accelerator-actions.md
|
f577384a1297-1
|
| List your accelerators | See [Viewing your accelerators](about-accelerators.viewing.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_ListAccelerators.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_ListAccelerators.html) |
| Get all information about an accelerator | See [Viewing your accelerators](about-accelerators.viewing.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_DescribeAccelerator.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_DescribeAccelerator.html) |
| Update an accelerator | See [ Creating or updating an accelerator](about-accelerators.creating-editing.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_UpdateAccelerator.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_UpdateAccelerator.html) |
| Delete an accelerator | See [ Creating or updating an accelerator](about-accelerators.creating-editing.md) | See [https://docs.aws.amazon.com/global-accelerator/latest/api/API_DeleteAccelerator.html](https://docs.aws.amazon.com/global-accelerator/latest/api/API_DeleteAccelerator.html) |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/global-accelerator-actions.md
|
495446560609-0
|
AWS Global Accelerator uses an AWS Identity and Access Management \(IAM\)[ service\-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role)\. A service\-linked role is a unique type of IAM role that is linked directly to a service\. Service\-linked roles are predefined by the service and include all of the permissions that the service requires to call other AWS services on your behalf\.
Global Accelerator uses the following IAM service\-linked role:
+ **AWSServiceRoleForGlobalAccelerator**–Global Accelerator uses this role to allow Global Accelerator to create and manage resources required for client IP address preservation\.
When you first create an accelerator in Global Accelerator and add an endpoint group, a role named AWSServiceRoleForGlobalAccelerator is automatically created to allow Global Accelerator create and manage resources necessary for client IP address preservation\. This role is required for using accelerators in Global Accelerator\. The ARN for the AWSServiceRoleForGlobalAccelerator role looks like this:
`arn:aws:iam::123456789012:role/aws-service-role/globalaccelerator.amazonaws.com/AWSServiceRoleForGlobalAccelerator`
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
495446560609-1
|
A service\-linked role makes setting up and using Global Accelerator easier because you don’t have to manually add the necessary permissions\. Global Accelerator defines the permissions of its service\-linked role, and only Global Accelerator can assume the roles\. The defined permissions include the trust policy and the permissions policy\. The permissions policy cannot be attached to any other IAM entity\.
You must remove any associated Global Accelerator resources before you can delete a service\-linked role\. This helps protect your Global Accelerator resources by making sure that you don't remove a service\-linked role that is still required to access active resources\.
For information about other services that support service\-linked roles, see [AWS Services That Work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) and look for the services that have **Yes **in the **Service\-Linked Role** column\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
550fd0c57ffa-0
|
Global Accelerator uses a service\-linked role named **AWSServiceRoleForGlobalAccelerator**\. The following sections describe the permissions for the role\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
512e31a66523-0
|
This service\-linked role allows Global Accelerator to manage EC2 Elastic Network Interfaces and security groups\.
The AWSServiceRoleForGlobalAccelerator service\-linked role trusts the following service to assume the role:
+ `globalaccelerator.amazonaws.com`
The role permissions policy allows Global Accelerator to complete the following actions on the specified resources:
+ Action: `ec2:CreateNetworkInterface` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:DescribeNetworkInterfaces` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:ModifyNetworkInterfaceAttribute` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:DeleteNetworkInterface` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:DeleteSecurityGroup` on `arn:aws:lambda:*:*:function:*` when `ec2:ResourceTag/AWSServiceName` is `GlobalAccelerator`
+ Action: `ec2:CreateSecurityGroup` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:DescribeSecurityGroups` on `arn:aws:lambda:*:*:function:*`
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
512e31a66523-1
|
+ Action: `ec2:DescribeSecurityGroups` on `arn:aws:lambda:*:*:function:*`
+ Action: `elasticloadbalancing:DescribeLoadBalancers` on `arn:aws:lambda:*:*:function:*`
+ Action: `ec2:CreateTags` on `arn:aws:ec2:*:*:security-group/*`
+ Action: `ec2:CreateTags` on `arn:aws:ec2:*:*:network-interface/*`
You must configure permissions to allow an IAM entity \(such as a user, group, or role\) to delete the Global Accelerator service\-linked role\. For more information, see [Service\-Linked Role Permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
36974f5a9eff-0
|
You don't manually create the service\-linked role for Global Accelerator\. The service creates the role for you automatically the first time that you create an accelerator\. If you remove your Global Accelerator resources and delete the service\-linked role, the service creates the role again automatically when you create a new accelerator\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
22f4df6f2b82-0
|
Global Accelerator does not allow you to edit the AWSServiceRoleForGlobalAccelerator service\-linked role\. After the service has created a service\-linked role, you cannot change the name of the role because various entities might reference the role\. However, you can edit the description of a role by using IAM\. For more information, see [Editing a Service\-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
662a595edb18-0
|
If you no longer need to use Global Accelerator, we recommend that you delete the service\-linked role\. That way you don’t have unused entities that are not actively monitored or maintained\. However, you must clean up the Global Accelerator resources in your account before you can manually delete the roles\.
After you have disabled and deleted your accelerators, then you can delete the service\-linked role\. For more information about deleting accelerators, see [ Creating or updating an accelerator](about-accelerators.creating-editing.md)\.
**Note**
If you have disabled and deleted your accelerators but Global Accelerator hasn't finished updating, service\-linked role deletion might fail\. If that happens, wait for a few minutes, and then try the service\-linked role deletion steps again\.
**To manually delete the AWSServiceRoleForGlobalAccelerator service\-linked role**
1. Sign in to the AWS Management Console and open the IAM console at [https://console\.aws\.amazon\.com/iam/](https://console.aws.amazon.com/iam/)\.
1. In the navigation pane of the IAM console, choose **Roles**\. Then select the check box next to the role name that you want to delete, not the name or row itself\.
1. For **Role** actions at the top of the page, choose **Delete role**\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
662a595edb18-1
|
1. For **Role** actions at the top of the page, choose **Delete role**\.
1. In the confirmation dialog box, review the service last accessed data, which shows when each of the selected roles last accessed an AWS service\. This helps you to confirm whether the role is currently active\. If you want to proceed, choose **Yes, Delete** to submit the service\-linked role for deletion\.
1. Watch the IAM console notifications to monitor the progress of the service\-linked role deletion\. Because the IAM service\-linked role deletion is asynchronous, after you submit the role for deletion, the deletion task can succeed or fail\. For more information, see [Deleting a Service\-Linked Role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
652522ce5885-0
|
Global Accelerator supports using service\-linked roles in AWS Regions where Global Accelerator is supported\.
For a list of the AWS Regions where Global Accelerator and other services are currently supported, see the [AWS Region Table](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/using-service-linked-roles.md
|
2465f9db7a52-0
|
AWS Global Accelerator publishes data points to Amazon CloudWatch for your accelerators\. CloudWatch enables you to retrieve statistics about those data points as an ordered set of time\-series data, known as *metrics*\. Think of a metric as a variable to monitor, and the data points as the values of that variable over time\. For example, you can monitor traffic through an accelerator over a specified time period\. Each data point has an associated time stamp and an optional unit of measurement\.
You can use metrics to verify that your system is performing as expected\. For example, you can create a CloudWatch alarm to monitor a specified metric and initiate an action \(such as sending a notification to an email address\) if the metric goes outside what you consider an acceptable range\.
Global Accelerator reports metrics to CloudWatch only when requests are flowing through the accelerator\. If requests are flowing through the accelerator, Global Accelerator measures and sends its metrics in 60\-second intervals\. If there are no requests flowing through the accelerator or there is no data for a metric, the metric is not reported\.
For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/)\.
**Topics**
+ [Global Accelerator metrics](#cloudwatch-metrics-global-accelerator)
+ [Metric dimensions for accelerators](#cloudwatch-metric-dimensions-aga)
+ [Statistics for Global Accelerator metrics](#cloudwatch-metric-statistics)
+ [View CloudWatch metrics for your accelerators](#view-metric-data)
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
df1fdfa99543-0
|
The `AWS/GlobalAccelerator` namespace includes the following metrics\.
| Metric | Description |
| --- | --- |
| NewFlowCount | The total number of new TCP and UDP flows \(or connections\) established from clients to endpoints in the time period\. **Reporting criteria**: There is a nonzero value\. **Statistics**: The only useful statistic is `Sum`\. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html) |
| ProcessedBytesIn | The total number of incoming bytes processed by the accelerator, including TCP/IP headers\. This count includes traffic to endpoints, minus health check traffic\. **Reporting criteria**: There is a nonzero value\. **Statistics**: The only useful statistic is `Sum`\. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html) |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
df1fdfa99543-1
|
| ProcessedBytesOut | The total number of outgoing bytes processed by the accelerator, including TCP/IP headers\. This count includes traffic from endpoints, minus health check traffic\. **Reporting criteria**: There is a nonzero value\. **Statistics**: The only useful statistic is `Sum`\. [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html) |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
555e72dc052f-0
|
To filter the metrics for your accelerator, use the following dimensions\.
| Dimension | Description |
| --- | --- |
| Accelerator | Filters the metric data by accelerator\. Specify the accelerator by the accelerator id \(the final portion of the accelerator ARN\)\. For example, if the ARN is `arn:aws:globalaccelerator::012345678901:accelerator/1234abcd-abcd-1234-abcd-1234abcdefgh`, you specify the following: **1234abcd\-abcd\-1234\-abcd\-1234abcdefgh**\. |
| Listener | Filters the metric data by listener\. Specify the listener by the listener id \(the final portion of the listener ARN\)\. For example, if the ARN is `arn:aws:globalaccelerator::012345678901:accelerator/1234abcd-abcd-1234-abcd-1234abcdefgh/listener/0123wxyz`, you specify the following: **0123wxyz**\. |
| EndpointGroup | Filters the metric data by endpoint group\. Specify the endpoint group by the AWS Region, for example, **us\-east\-1** \(all lowercase\)\. |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
555e72dc052f-1
|
| SourceRegion | Filters the metric data by source region, which is the geographic area of the AWS Regions where your application endpoints are running\. Source region is one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html) \*Excluding South Korea and India |
| DestinationEdge | Filters the metric data by destination edge, which is the geographic area of the AWS edge locations that serve your client traffic\. Destination edge is one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/global-accelerator/latest/dg/cloudwatch-monitoring.html) \*Excluding South Korea and India |
| TransportProtocol | Filters the metric data by transport protocol: UDP or TCP\. |
| AcceleratorIPAddress | Filters the metric data by the IP address of the accelerator: that is, one of the static IP addresses assigned to an accelerator\. |
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
419ab469fbe9-0
|
CloudWatch provides statistics based on the metric data points published by Global Accelerator\. Statistics are aggregations of metric data over a specified period of time\. When you request statistics, the returned data stream is identified by the metric name and dimension\. A dimension is a name/value pair that uniquely identifies a metric\. For example, you can request the processed bytes out for an accelerator where the bytes are served from AWS edge locations in Europe \(destination edge is "EU"\)\.
The following are examples of metric/dimension combinations that you might find useful:
+ View the amount of traffic served \(such as ProcessedBytesOut\) by each of your two accelerator IP addresses to validate that your DNS configuration is correct\.
+ View the geographical distribution of your user traffic and monitor how much of it is local \(for example, North America to North America\) or global \(for example, Australia or India to North America\)\. To determine this, view the metrics ProcessedBytesIn or ProcessedBytesOut with the dimensions DestinationEdge and SourceRegion set to specific values\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
207ac47cb51c-0
|
You can view the CloudWatch metrics for your accelerators using the CloudWatch console or the AWS CLI\. In the console, metrics are displayed as monitoring graphs\. The monitoring graphs show data points only if the accelerator is active and receiving requests\.
You must view CloudWatch metrics for Global Accelerator in the US West \(Oregon\) Region, both in the console or when using the AWS CLI\. When you use the AWS CLI, specify the US West \(Oregon\) Region for your command by including the following parameter: `--region us-west-2`\.
**To view metrics using the CloudWatch console**
1. Open the CloudWatch console at [ https://us\-west\-2\.console\.aws\.amazon\.com/cloudwatch/home?region=us\-west\-2](https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2)\.
1. In the navigation pane, choose **Metrics**\.
1. Select the **GlobalAccelerator** namespace\.
1. \(Optional\) To view a metric across all dimensions, type its name in the search field\.
**To view metrics using the AWS CLI**
Use the following [list\-metrics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html) command to list the available metrics:
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
207ac47cb51c-1
|
```
aws cloudwatch list-metrics --namespace AWS/GlobalAccelerator --region us-west-2
```
**To get the statistics for a metric using the AWS CLI**
Use the following [get\-metric\-statistics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/get-metric-statistics.html) command to get statistics for a specified metric and dimension\. Note that CloudWatch treats each unique combination of dimensions as a separate metric\. You can't retrieve statistics using combinations of dimensions that were not specifically published\. You must specify the same dimensions that were used when the metrics were created\.
The following example lists the total processed bytes in, per minute, for your accelerator serving from the North America \(NA\) destination edge\.
```
aws cloudwatch get-metric-statistics --namespace AWS/GlobalAccelerator \
--metric-name ProcessedBytesIn \
--region us-west-2 \
--statistics Sum --period 60 \
--dimensions Name=Accelerator,Value=1234abcd-abcd-1234-abcd-1234abcdefgh Name=DestinationEdge,Value=NA \
--start-time 2019-12-18T20:00:00Z --end-time 2019-12-18T21:00:00Z
```
The following is example output from the command:
```
{
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
207ac47cb51c-2
|
```
The following is example output from the command:
```
{
"Label": "ProcessedBytesIn",
"Datapoints": [
{
"Timestamp": "2019-12-18T20:45:00Z",
"Sum": 2410870.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:47:00Z",
"Sum": 0.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:46:00Z",
"Sum": 0.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:42:00Z",
"Sum": 1560.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:48:00Z",
"Sum": 0.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:43:00Z",
"Sum": 1343.0,
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
207ac47cb51c-3
|
"Timestamp": "2019-12-18T20:43:00Z",
"Sum": 1343.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:49:00Z",
"Sum": 0.0,
"Unit": "Bytes"
},
{
"Timestamp": "2019-12-18T20:44:00Z",
"Sum": 35791560.0,
"Unit": "Bytes"
}
]
}
```
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/cloudwatch-monitoring.md
|
256a261ada77-0
|
An *accelerator* in AWS Global Accelerator directs traffic to optimal endpoints over the AWS global network to improve the availability and performance of your internet applications that have a global audience\. Each accelerator includes one or more listeners\. A listener processes inbound connections from clients to Global Accelerator, based on the protocol and port \(or port range\) that you configure\.
When you create an accelerator, by default, Global Accelerator provides you with a set of two static IP addresses\. If you bring your own IP address range to AWS \(BYOIP\), you can instead assign static IP addresses from your own pool to use with your accelerator\. For more information, see [Bring your own IP addresses \(BYOIP\) in AWS Global Accelerator](using-byoip.md)\.
**Important**
The IP addresses are 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 *delete* an accelerator, you lose the Global Accelerator static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them\. As a best practice, ensure that you have permissions in place to avoid inadvertently deleting accelerators\. You can use IAM policies with Global Accelerator, for example, tag\-based permissions, to limit the users who have permissions to delete an accelerator\. For more information, see [ Tag\-based policies](auth-and-access-control.md#access-control-manage-access-tag-policies)\.
|
https://github.com/siagholami/aws-documentation/tree/main/documents/aws-global-accelerator-dev-guide/doc_source/about-accelerators.md
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.