aws / aws/aws-cdk

aws-ec2: L2 Construct for EC2 Instance Connect Endpoint

Open
#31,896 3 comments 0 reactions 0 assignees View on GitHub
@aws-cdk/aws-ec2 effort/medium feature-request p2
Dominant language
TypeScript
Stars
12.9k
Forks
4.6k
Avg merge
1d 19h
Merged PRs (30d)
71

Description

### Describe the feature

An L1 construct is available, however an L2 construct would be handy.

L1 Construct:
https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.CfnInstanceConnectEndpoint.html

Original issue where L1 construct was added:
https://github.com/aws/aws-cdk/issues/26226

### Use Case

Tunnel into private subnets via a bastion host without needing to expose the ssh port publicly.

Being able to manage the EC2 Instance Connect Endpoint ergonomically with CDK rather than manually managing the resource or using Cfn L1 constructs.

### Proposed Solution

_No response_

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.163.1

### Environment details (OS name and version, etc.)

MacOS Sonoma

Contributor guide

Open the contributing guide

Research direction

Start with the AWS CDK L1 construct linked in the issue and compare it with existing EC2 L2 constructs in the aws_ec2 library. Review issue #26226 for the resource's original context; done means providing an ergonomic L2 construct for managing an EC2 Instance Connect Endpoint through CDK rather than the L1 construct.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.