New serverless pattern - APIGW Private Custom Domain Name with Internet-Enabled Lambda using NAT Gateway in Terraform #2746
+1,068
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello @julianwood and @marcojahn, Any update on this? |
parikhudit
reviewed
Sep 20, 2025
There was a problem hiding this comment.
The diagram & wordings seem inaccurate as per the flow defined.
parikhudit
reviewed
Sep 20, 2025
There was a problem hiding this comment.
- title does not meet maximum length of 75
- description does not meet maximum length of 150
- language is not one of values: TypeScript,Node.js,Python,Java,Go,Rust,.NET,OpenAPI,YAML,
- gitHub.template.templateURL: Please remove the projectFolder value from the templateFile
parikhudit
reviewed
Sep 20, 2025
Comment on lines
+20
to
+33
| 1. Create a new directory, navigate to that directory in a terminal and clone the GitHub repository: | ||
| CMD : git clone https://github.com/aws-samples/serverless-patterns | ||
|
|
||
| 2. Change directory to the pattern directory: | ||
| CMD : cd serverless-patterns/private-apigw-custom-domain-private-restapi-public-lambda-terraform | ||
|
|
||
| 3. From the command line, initialize terraform to download and install the providers defined in the configuration: | ||
| CMD : terraform init | ||
|
|
||
| 4. Review the resources that will be created: | ||
| CMD : terraform plan | ||
|
|
||
| 5. From the command line, apply the configuration in the main.tf file: | ||
| CMD : terraform apply -auto-approve |
There was a problem hiding this comment.
Nit: Please use appropriate markup for commands
parikhudit
reviewed
Sep 20, 2025
| upper = false | ||
| } | ||
|
|
||
|
|
There was a problem hiding this comment.
Nit: scope for uniform pattern of number of new lines (across the file)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #2747, if available:
Description of changes:
This architecture demonstrates how to build a private API accessible only from within a VPC using API Gateway private endpoints, where the API is protected by custom domain names and SSL certificates. The solution includes a Lambda function running in private subnets that can access the internet through NAT Gateways, and an EC2 instance configured with Session Manager for secure management, all while maintaining network isolation and security best practices through VPC endpoints.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.