Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DMZ network #3

Closed
at0S opened this issue Sep 11, 2020 · 1 comment · Fixed by #6
Closed

DMZ network #3

at0S opened this issue Sep 11, 2020 · 1 comment · Fixed by #6
Assignees
Labels
enhancement New feature or request

Comments

@at0S
Copy link
Owner

at0S commented Sep 11, 2020

Description

Underlying services will self-manage private components (as there is fit/requirement), here we need to figure out the buffer zone, which will protect us from the hostilities of the Internet; implement it, and document the effort.

@at0S at0S added the enhancement New feature or request label Sep 11, 2020
@at0S at0S self-assigned this Sep 11, 2020
@at0S at0S added this to Backlog in Common infrastructure Sep 11, 2020
@at0S
Copy link
Owner Author

at0S commented Sep 23, 2020

Done when:

  1. There is an Internet-connected VPC.
  2. Able to bootstrap an instance into the DMZ network and it is possible to fetch data from the https://goolge.com via curl.
  3. Internet routes are available for downstream infrastructure, e.g consumable by terraform managed infra in the current repository.

@at0S at0S moved this from Backlog to Ready for work in Common infrastructure Sep 23, 2020
@at0S at0S closed this as completed in #6 Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Common infrastructure
  
Ready for work
Development

Successfully merging a pull request may close this issue.

1 participant