ClusterLabs / ClusterLabs/resource-agents
VPC endpoint support
- Dominant language
- Shell
- Stars
- 519
- Forks
- 608
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 7
Description
I wonder if it is possible to add support for VPC url endpoints to aws-vpc-move-ip. It checks against the standard service url, for example ec2.amazonaws.com, but if traffic needs to be kept inside the VPC it would be better to check against the EC2 VPC endpoint like for example vpce-abc123-xyz789.ec2.us-east-1.vpce.amazonaws.com. This will benefit setups where internet access is restricted.
Thank you,
Noe
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the aws-vpc-move-ip agent and trace where it checks the standard EC2 service URL, ec2.amazonaws.com. Compare that path with the VPC endpoint example in the issue and inspect the repository’s existing tests or validation for this agent. Done means restricted-VPC setups can use the endpoint while standard URL behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, shell
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100