rust-lang / rust-lang/simpleinfra
Migrate bastion to the new VPC
Nobody has claimed this yet.
- Dominant language
- HCL
- Stars
- 178
- Forks
- 107
- Avg merge
- 15h 57m
- Merged PRs (30d)
- 38
Description
Bastion lives in a separate vpc (the legacy one) compared to the rds (the "new") one, so the security group is needed to allow access to rds from outside the vpc.
if the bastion were to be migrated to the new vpc there would be no need anymore as bastion <-> rds would be intra-vpc traffic
More context on zulip
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Zulip discussion, then locate the infrastructure definitions for the bastion, legacy VPC, new VPC, RDS, and the related security group. Done means the bastion uses the new VPC and the cross-VPC RDS access requirement is removed without breaking access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100