Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Client VPN + Local docker-compose amazon-ecs-local-container-endpoints 169.254.170 being routed through VPN
0
I followed this guide to set up a local dev env with Docker-compose + local IAM auth. Additionally, I am trying to connect to a resource inside our VPC using the AWS client VPN (split tunnel mode).
When running each of these individually, there are no issues. However, when combining them, the requests being made to the local ECS endpoint for auth (169.254.170/24) is being redirected through the VPN and failing to pull back valid creds.
Is it possible to keep all 169.254.170/24 traffic local? Is it possible to use a different ip range for the local container?
