AWS Global Accelerator

验证：未记录

适用版本: 未记录
验证范围: 尚未登记验证记录。

本文缩写（英文全称与中文含义）

缩写	英文全称／名称	中文含义
ALB	Application Load Balancer	应用负载均衡器
AWS	Amazon Web Services	亚马逊云服务
BYOIP	Bring Your Own IP	自带 IP 地址到云平台
CDN	Content Delivery Network	内容分发网络
DNS	Domain Name System	域名系统
EC2	Elastic Compute Cloud	AWS 云服务器服务
HTTP	Hypertext Transfer Protocol	超文本传输协议
HTTPS	Hypertext Transfer Protocol Secure	使用 TLS 加密的 HTTP
IP	Internet Protocol	网际协议；IP 地址是网络寻址标识
L4	Layer 4	网络第四层，传输层
NACL	Network Access Control List	网络访问控制列表
NLB	Network Load Balancer	网络负载均衡器
SG	Security Group	安全组
TCP	Transmission Control Protocol	传输控制协议
TLS	Transport Layer Security	传输层安全协议
TTL	Time To Live	存活时间；具体指缓存有效期或记录过期时间
UDP	User Datagram Protocol	用户数据报协议
VPC	Virtual Private Cloud	虚拟私有云网络
WAF	Web Application Firewall	Web 应用防火墙

1. Important Points#

AWS Global Accelerator 提供固定 Anycast static IP，把用户流量从最近的 AWS edge location 接入，再走 AWS global network 转发到健康的 regional endpoint。

Global Accelerator 用来做:
    public static IP for ALB / NLB / EC2 / Elastic IP endpoint
    multi-region active-active / active-passive traffic routing
    faster failover without relying only on DNS TTL
    TCP / UDP application acceleration
    bring your own IP address when required

Global Accelerator 不是:
    CDN
    HTTP cache
    TLS termination service
    WAF replacement
    DNS service replacement
    private VPC connectivity service

核心理解：

client
    -> Global Accelerator static anycast IPs
        -> nearest AWS edge location
            -> AWS global network
                -> endpoint group in selected AWS Region
                    -> healthy endpoint: ALB / NLB / EC2 / Elastic IP

2. Core Concepts#

Concept	Meaning
accelerator	Global Accelerator 主资源，提供固定 static IPs
static IP	客户端访问的入口 IP，通常给 DNS A record 指向它
listener	定义 protocol / port，比如 TCP 443 或 UDP 443
endpoint group	一个 AWS Region 里的 endpoint 集合
endpoint	实际后端入口，比如 ALB、NLB、EC2 instance、Elastic IP
traffic dial	region 级别流量比例，常用于切流 / failover
endpoint weight	同一个 endpoint group 内 endpoint 的权重
health check	判断 endpoint 是否健康，健康才接收流量

3. When To Use#

ALB 需要固定公网 IP:
    Global Accelerator -> ALB
    DNS A record -> Global Accelerator static IPs

multi-region app:
    one accelerator
    endpoint group: ap-east-1
    endpoint group: ap-northeast-1
    traffic dial / endpoint health 控制流量

TCP / UDP service:
    Global Accelerator listener TCP/UDP
    endpoint usually NLB / EC2 / Elastic IP

不想被 DNS cache 影响 failover:
    Global Accelerator 用 Anycast IP + health routing
    endpoint unhealthy 后可以更快把流量转到健康 endpoint

4. Service Configuration#

accelerator#

Item	Recommendation
IP address type	use AWS-owned static IP unless BYOIP is required
DNS	create A record pointing to accelerator static IPs or alias if supported by your DNS flow
Tags	`env`, `service`, `owner`, `cost-center`

listener#

listener controls:
    protocol: TCP / UDP
    port range: example 80, 443, 5000-6000
    client affinity: usually NONE unless source-IP stickiness is required

endpoint group#

endpoint group controls one Region:
    region
    health check path / port / protocol when applicable
    traffic dial percentage
    endpoint list

traffic dial examples:
    100: region can receive full traffic
    0: region receives no traffic
    50: region receives half of its normal share

endpoint#

endpoint can be:
    Application Load Balancer
    Network Load Balancer
    EC2 instance
    Elastic IP address

endpoint weight:
    controls traffic split inside the same endpoint group
    useful for blue/green or weighted migration

5. Global Accelerator vs CloudFront vs Route 53#

Service	Best For	Key Difference
Global Accelerator	static IP + TCP/UDP acceleration + regional failover	no cache, L4-style entry, Anycast IP
CloudFront	HTTP/HTTPS CDN, cache, edge security	caches content, supports HTTP behavior policies
Route 53	DNS routing	DNS answer can be affected by TTL / resolver cache

需要 CDN / cache:
    use CloudFront

需要 ALB 固定 IP:
    use Global Accelerator in front of ALB

只需要 DNS routing:
    use Route 53 latency / weighted / failover records

需要更快 failover and static IP:
    use Global Accelerator

6. Common Architecture#

static ip for alb#

client
    -> DNS A record
        -> Global Accelerator static IPs
            -> listener TCP 443
                -> endpoint group ap-east-1
                    -> public ALB
                        -> target group

active passive multi region#

accelerator
    listener TCP 443
        endpoint group ap-east-1:
            traffic dial = 100
            endpoint = primary ALB
        endpoint group ap-northeast-1:
            traffic dial = 0 or low weight
            endpoint = standby ALB

7. Pricing Shape#

main cost components:
    accelerator hourly charge
    data transfer premium for traffic processed by Global Accelerator
    normal endpoint cost, such as ALB / NLB / EC2 / data transfer

cost check:
    Global Accelerator is not just a DNS feature
    compare against Route 53 routing if static IP / fast failover / TCP UDP acceleration is not required

8. Common Pitfalls#

Global Accelerator 的健康检查必须反映应用是否能接流量；端口可连接并不能证明业务已经就绪。

thinking it is CloudFront:
    Global Accelerator does not cache static files or terminate HTTP behavior

using it only for DNS convenience:
    if no static IP or fast failover requirement, Route 53 may be enough

forgetting backend security:
    endpoint still needs SG / NACL / app security

assuming every private app can use it:
    Global Accelerator is for internet-facing acceleration, not private VPC-only access

ignoring health check design:
    health check endpoint must reflect real app readiness, not just port open

not checking cost:
    hourly + data transfer premium can be meaningful for high traffic workloads