1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
As described in the following document, we thought that a NAT Gateway might be necessary to access public external services, etc.
https://aws.amazon.com/jp/blogs/aws/new-for-app-runner-vpc-support/
When connected to a VPC, all outbound traffic from your AppRunner service will be routed based on the VPC routing rules. Services will not have access to the public internet (including AWS APIs) unless allowed by a route to a NAT Gateway. You can also set up VPC endpoints to connect to AWS APIs such as Amazon Simple Storage Service (Amazon S3) and Amazon DynamoDB to avoid NAT traffic.
Relevant content
- asked 3 years ago
- Accepted Answerasked 2 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
So I have to create a public NAT Gateway with elastic IP for that public subnet which I included in the VPC connector settings, right ?
Yes, a NAT Gateway must be created. After creating the NAT Gateway, add a route to the NAT Gateway to the route table of the subnet used for the VPC connector.
Thank you! I've created a public NAT gateway and add routing of subnet IP block to that NAT gateway, however still apprunner instance can't access to the internet. Should I add some extra configuration to the NAT gateway to connect internet ?
I've connected the apprunner instance to a new private subnet, then added a NAT gateway to the private subnet to a public subnet. Now it's working smoothly