Add NAT Gateway and private subnets #23
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jvntf I had generated those private isolated subnets for RDS and we are no longer using them that way. Let's just delete them/replace them with the private subnets you created in this PR. Do you mind removing them? |
|
removed @anayeaye |
jvntf
changed the title
anayeaye
approved these changes
Feb 10, 2022
|
This strategy is dropped in favor of creating 2 lambdas, one connected to the internet to query CMR / s3 and generate COGs, and one to connected to the database (member of VPC). No NAT required. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #22
i believe that private subnets will automatically get a route table with a route to the nat gateway
@anayeaye and i just discussed explicitly defining the RDS security group like so, after which we can add rules in this workflow for lambdas in the same group to be able to access the RDS instance