使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款
AWS re:Postre:Post

AWS Global Accelerator Response IP does not Match Accelerator IP

0

I have a Global Accelerator (52.223.XXX.XXX) with an Endpoint targeting my EC2 instance (3.134.XXX.XXX). When clients send UDP traffic via the Global Accelerator, the response IP is that of the EC2 instance rather than the Global Accelerator. Since the client application expects the response IP to match the request IP, it does not work correctly. I have no control over the client application. Is there some way to configure the services to behave how I need it to? To be clear:

  • Current behavior: Client sends UDP traffic to 52.223.XXX.XXX (Global Accelerator) and receives a response from 3.134.XXX.XXX (EC2 instance).
  • Wanted behavior: Client sends UDP traffic to 52.223.XXX.XXX (Global Accelerator) and receives a response from 52.223.XXX.XXX (Global Accelerator).
  • Toni_S 專家
    2 年前

    Are you using Standard accelerator or custom routing accelerator?

主題
網路與內容交付運算
標籤
AWS Global AcceleratorAmazon EC2網路與內容交付
語言
English
rePost-User-2870327
已提問 2 年前檢視次數 362 次
2 個答案
0

What is your Endpoint Type configuration? It should be EC2 Instance and not Elastic IP.

Smellyspice
已回答 2 年前
  • rePost-User-2870327
    2 年前

    Thanks for the response. The Endpoint Type is set to the EC2 Instance. After some more testing, it seems the response IP is inconsistent. Sometimes the response comes from the Global Accelerator, while other times it comes from the EC2 instance. Could it be a routing problem?

0

We are using GA for DNS (UDP and TCP) and it works as expected. I would check the behaviour of your application. If your app is replying to existing inbound UDP traffic, it would use the GA IPs. If your app is trying to establish new connections outbound as a result of inbound packets from GA, then you would see the IP of the instance.

Smellyspice
已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋，同時有助於提問者的專業成長。

回答問題指南

相關內容