This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't route S3 traffic to a nat-gateway (#423)
* Custom routing to predefined NAT when run in DMZ without public ip We have a use-case when we want to run instances in DMZ or public subnet but without public ips. Elastic ip would be assigned later to one of the instances. Without public ip instance will not be able to initialize (download docker, push logs, use AWS api, etc...). To solve this problem we need to create a separate routing table for outgoing https traffic. Such traffic would be routed to a custom nat gateway. Mappings between subnets and nat gateways would come from UserData and populated by senza. * Don't route S3 traffic to a nat-gateway We have S3 endpoint configured in every account.
- Loading branch information