Deploying a Static Website with HTTPS using CDK, TypeScript, CloudFront, S3, ACM and Route 53
ฝัง
- เผยแพร่เมื่อ 2 พ.ค. 2023
- Learn how to deploy a static website using a combination of AWS services, including CloudFront, S3, ACM, and Route 53, with the help of CDK and TypeScript. By following the steps outlined in the video, users can learn how to create a secure HTTPS website and configure Route 53 DNS records to point to their newly deployed website.
Code for the deployment is saved in public git repository at: github.com/stormit-cloud/cdk-...
Necessary steps are also described at:
github.com/stormit-cloud/cdk-...
Prerequisites:
AWS CLI: docs.aws.amazon.com/cli/lates...
NodeJS: nodejs.org/en/download
AWS CDK: aws.amazon.com/getting-starte...
TypeScript CDK: docs.aws.amazon.com/cdk/v2/gu...
Hands-on tutorial in AWS Management console:
www.stormit.cloud/blog/setup-...
More about other AWS services at www.stormit.cloud/blog/ - วิทยาศาสตร์และเทคโนโลยี
Have any questions about AWS? Drop them in the comments below 👇 and our experts will be happy to help. For more insights and tutorials on Cloud Computing, check out our blog: www.stormit.cloud/blog/. Let's master the cloud together!
I just forked your repo and it works perfect. Thanks!
Hello, thank you for reaching out and for your kind words! Explore more insightful content related to AWS on our blog at www.stormit.cloud/blog/
Why we do cdk deploy again it says that "bucket it's already exists" and ask to delete bucket to again make "cdk deploy"?
Hi, I've tested this, and I didn't receive this message when attempting to redeploy the architecture. Why do you need to use 'cdk deploy' again?
Doesn't this still leave your bucket as public though?
Hi, yes, it will leave the S3 bucket public. However, when you use S3 for static website hosting, making it private is not possible. You won't be able to use OAC or OAI. For more information, please refer to our blog post: www.stormit.cloud/blog/cloudfront-origin-access-control/#oac-use-s3-website
DnsValidatedCertificate is deprecated from few months now. Thanks for the tutorial with a deprecated class. Super helpful :|
Hi, thank you for your comment. We are using the deprecated class (DnsValidatedCertificate) because, currently, there isn't a better alternative available to solve this. The underlying reason is that this infrastructure require a certificate in a different region (us-east) than the rest of the infrastructure is actually deployed (eu-west). You can find further details about this matter in the following discussion: github.com/aws/aws-cdk/discussions/23952 .