flaviostutz / flaviostutz/cdk-practical-constructs

apigateway: Add resource policy for VPCE

Open
#53 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
7
Forks
7
PR merge metrics
No merged PRs in 30d

Description

## Problem being solved
Configuring VPCE for APIGW might not be enough to disable invocations from other networks. We need to investigate this and create a resource policy to prevent this.

Check best practices here: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-private-apis.html#:~:text=Restrict%20access%20to%20your%20private,can%20invoke%20your%20private%20API.

"Restrict access to your private API to specific VPCs or VPC endpoints. Add aws:SourceVpc or aws:SourceVpce conditions to your API's resource policy to restrict access."

## Proposal
Create resource policy for apigw restricting the access only to the configure VPCEs

Contributor guide

Open the contributing guide

Research direction

Read the linked AWS private API best-practices guidance and locate the API Gateway construct in this repository. Trace how configured VPCEs are supplied, then inspect any existing construct tests or examples for synthesized-policy expectations. Done means the generated resource policy restricts invocation to the configured VPCEs and the behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
api, cloud, security
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.