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).
  • Are you using Standard accelerator or custom routing accelerator?

2 Answers
0

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

answered 4 months ago
  • 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.

answered 4 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions