(aws-ec2): Add `InterfaceVpcEndpointAwsService.SCHEDULER` for EventBridge Scheduler
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
Research direction
Start with packages/aws-cdk-lib/aws-ec2/lib/vpc-endpoint.ts and review the neighboring InterfaceVpcEndpointAwsService constants. Add the Scheduler service constant described in the issue, then verify that the aws-ec2 tests pass and that the exposed constant represents the scheduler endpoint and is usable by VPC interface endpoints.
Written by the indexing model from the issue text.
Description
Describe the feature
aws-cdk-lib/aws-ec2 exposes static InterfaceVpcEndpointAwsService constants for most AWS services (EVENTBRIDGE, STEP_FUNCTIONS, LAMBDA, etc.), but has no constant for EventBridge Scheduler (com.amazonaws.<region>.scheduler).
Users must currently construct it manually:
this.vpc.addInterfaceEndpoint('SchedulerEndpoint', {
service: new InterfaceVpcEndpointAwsService('scheduler'),
});
Use Case
VPC-attached Lambdas that call the EventBridge Scheduler API (aws-sdk-scheduler) need an interface VPC endpoint (or NAT egress).
Adding a supported constant would match the ergonomics of other services and avoid the surprise that Scheduler is not covered by EVENTBRIDGE (which points at events, a separate service).
Proposed Solution
Add to packages/aws-cdk-lib/aws-ec2/lib/vpc-endpoint.ts:
public static readonly SCHEDULER = new InterfaceVpcEndpointAwsService('scheduler');
Region availability per AWS docs: https://docs.aws.amazon.com/scheduler/latest/UserGuide/using-vpc-endpoints.html
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
AWS CDK Library version (aws-cdk-lib)
2.258.1
AWS CDK CLI version
2.1135.1 (build 6551740)
Environment details (OS name and version, etc.)
Amazon Linux 2
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 71
Contributor guide
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.
More from aws/aws-cdk
-
@aws-cdk/aws-bedrock-agentcore-alpha bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
@aws-cdk/aws-rds effort/small feature-request p2
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
@aws-cdk/aws-cloudwatch effort/medium feature-request p2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
@aws-cdk/aws-s3-deployment bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
@aws-cdk/aws-lambda-nodejs effort/medium feature-request p2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100