aws-samples / aws-samples/trading-latency-benchmark
Allow deployment in existing infra
- Dominant language
- C
- Stars
- 95
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the feature
Add support to specify existing VPC/subnets for deployment.
### Use Case
Currently the tool creates a new TradingBenchmarkVPC to deploy the instances in. I would like to be able to specify existing VPCs to deploy the instances in.
### Proposed Solution
Implement an option to specify VPC and subnet parameters for the tool to use for EC2 deployment.
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [x] This feature might incur a breaking change
### Language
Typescript
Contributor guide
Research direction
Start by locating the deployment entry point and the code that creates TradingBenchmarkVPC and EC2 resources. Trace how VPC and subnet settings are currently selected, then verify the completed change by deploying with existing VPC and subnet parameters without creating a new VPC.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100