Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Don't route S3 traffic to a nat-gateway #423

Merged
merged 3 commits into from
Jul 14, 2017

Conversation

CyberDem0n
Copy link
Contributor

We have S3 endpoint configured in every account.

Alexander Kukushkin added 3 commits July 12, 2017 14:38
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.
We have S3 endpoint configured in every account.
@tuxlife tuxlife requested review from Raffo and apfeiffer85 July 14, 2017 13:23
@tuxlife
Copy link
Contributor

tuxlife commented Jul 14, 2017

👍

1 similar comment
@Raffo
Copy link
Contributor

Raffo commented Jul 14, 2017

👍

@tuxlife tuxlife merged commit e4c7dc3 into zalando-stups:master Jul 14, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants