feat: Add EC2 Instance Connect Endpoint support #1255
Draft
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.
Description
Added support for EC2 Instance Connect Endpoint (EICE) in the VPC module.
This allows users to securely SSH or RDP into instances in private subnets without using a bastion host or exposing public IPs.
Also added a fully self-contained example under
examples/ec2-instance-connect-endpoint/.Motivation and Context
AWS recently introduced EC2 Instance Connect Endpoint, which simplifies secure connectivity to private subnets.
Currently, the VPC module does not support this resource natively, requiring users to define it manually.
This feature:
create_instance_connect_endpointfor optional usageCloses: #1253
Breaking Changes
No breaking changes.
create_instance_connect_endpoint = falseby default)How Has This Been Tested?
examples/ec2-instance-connect-endpoint/demonstrating usagecd examples/ec2-instance-connect-endpoint terraform init terraform apply terraform destroyExample Usage