When considering hosting a static website on AWS, the go-to solution often involves combining CloudFront with S3. However, if your project entails stringent privacy requirements and is intended solely for internal users, configuring CloudFront with these constraints can be both complex and challenging.
This blueprint provides a detailed example of hosting a static website internally on AWS, utilizing an Internal Application Load Balancer (ALB), an S3 VPC Endpoint Interface, and a Private S3 Bucket. This setup ensures enhanced privacy and internal access control.
You are encouraged to tailor this blueprint to fit your specific requirements.
Additionally, contributions through pull requests for further improvements are always welcome.
- Route53 Hosted Domain
- ACM Certificate
- VPC with Private Subnets
First, you will need to adapt the parameters in the Makefile.
Then, run the following command:
$ make deploy
You will have to deploy your static website into the created S3 bucket that is named with your DomainName variable. Done ✅.
$ make tear-down
- 🏴☠️ AWS Security Boutique: zoph.io
- 💌 AWS Security Digest Newsletter
- 🐦 𝕏/Twitter: zoph