-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(apprunner): support vpc ingress connection #30623
base: main
Are you sure you want to change the base?
Conversation
5b3e3e1
to
6e66ff9
Compare
@Mergifyio update |
☑️ Nothing to do
|
|
||
public constructor(scope: Construct, id: string, props: VpcIngressConnectionProps) { | ||
super(scope, id, { | ||
physicalName: props.vpcIngressConnectionName, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you check if it deploys with vpcIngressConnectionName: undefined
?
If not, we should lazily generate one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Luca Pizzini <lpizzini7@gmail.com>
@lpizzinidev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 👍
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Issue # (if applicable)
Closes #22850.
Reason for this change
To support VPC Ingress Connection for making App Runner Service private and only accessible from within a VPC.
Description of changes
isPubliclyAccessible
property to theService
classVpcIngressConnection
classDescription of how you validated changes
Add unit tests and integ tests
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license