Amazon RDS converter: extract Subnets#26621
Merged
marcoandredinis merged 1 commit intomasterfrom May 22, 2023
Merged
Conversation
When parsing Amazon RDS databases extract the Subnets. Why do we need them? We are going to allow for automatic deployment of Database Services using Amazon ECS w/ Fargate. To do so, we must provide the subnets which our container can connect to. So, we need to get the Subnets associated with the Amazon RDS database in order to pass them when creating the Amazon ECS Service. Related issue: #25521
marcoandredinis
force-pushed
the
marco/add_aws_subnets_rds
branch
from
c3ce152 to
142d741
Compare
espadolini
approved these changes
May 22, 2023
lxea
approved these changes
May 22, 2023
|
@marcoandredinis See the table below for backport results.
|
marcoandredinis
added a commit
that referenced
this pull request
May 22, 2023
When parsing Amazon RDS databases extract the Subnets. Why do we need them? We are going to allow for automatic deployment of Database Services using Amazon ECS w/ Fargate. To do so, we must provide the subnets which our container can connect to. So, we need to get the Subnets associated with the Amazon RDS database in order to pass them when creating the Amazon ECS Service. Related issue: #25521
marcoandredinis
added a commit
that referenced
this pull request
May 23, 2023
When parsing Amazon RDS databases extract the Subnets. Why do we need them? We are going to allow for automatic deployment of Database Services using Amazon ECS w/ Fargate. To do so, we must provide the subnets which our container can connect to. So, we need to get the Subnets associated with the Amazon RDS database in order to pass them when creating the Amazon ECS Service. Related issue: #25521
Closed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
When parsing Amazon RDS databases extract the Subnets.
Why do we need them?
We are going to allow for automatic deployment of Database Services using Amazon ECS w/ Fargate.
To do so, we must provide the subnets which our container can connect to.
So, we need to get the Subnets associated with the Amazon RDS database in order to pass them when creating the Amazon ECS Service.
Related issue:
#25521