AWS Global Accelerator launches port overrides
AWS Global Accelerator announces the ability to override the destination ports used to route traffic to an application endpoint. This allows you to map a list of external destination ports — that your users send traffic to — to a list of internal destination ports that you want an application endpoint to receive traffic on. By default, an accelerator routes user traffic to endpoints in AWS Regions using the protocol and port ranges that you specify when you create a listener. For example, if you define a listener that accepts TCP traffic on ports 80 and 443, the accelerator routes traffic to those ports on an endpoint.
AWS Global Accelerator announces the ability to override the destination ports used to route traffic to an application endpoint. This allows you to map a list of external destination ports — that your users send traffic to — to a list of internal destination ports that you want an application endpoint to receive traffic on. By default, an accelerator routes user traffic to endpoints in AWS Regions using the protocol and port ranges that you specify when you create a listener. For example, if you define a listener that accepts TCP traffic on ports 80 and 443, the accelerator routes traffic to those ports on an endpoint.
Starting today, when you create or update an endpoint group associated to a listener, you can define different destination ports that you want the application endpoints to receive traffic on. For example, you might want your users to send traffic to external ports 80 and 443, but then have your endpoints receive traffic on ports 1080 and 1443, respectively.
You can configure port overrides for each of your accelerator’s endpoint groups by using the AWS Management Console, AWS Command Line Interface (CLI), and by working with API operations programmatically. To learn more, visit the AWS Global Accelerator documentation.