AWS Route53 Domain and SSL Certificate using Hosted Zones and ACM in 2025.
“Hey everyone, welcome back to EsthyTech! If you’ve been following along, in the last video we explored how to create a Route 53 health check. Today, I’m taking it one step further — we’re going to set up a custom domain in AWS using Route 53, and secure it with an SSL certificate through AWS Certificate Manager. Whether you bought your domain on AWS or somewhere else, I’ll walk you through everything step by step. So stick around, because by the end of this video, your domain will be secured and ready to integrate with services like API Gateway, CloudFront, or even S3 websites.”
Hosted Zone Basics
“First things first, let’s talk about hosted zones. A hosted zone is basically a container in Route 53 where all the DNS records for your domain live. If you purchased your domain through AWS, Route 53 automatically sets this up for you. But if you purchased elsewhere, don’t worry , you just need to create one manually.”
Creating a Hosted Zone
“Head into Route 53, go to ‘Hosted Zones,’ and click Create Hosted Zone. Enter your domain name, and since we want the domain to be publicly available, choose Public Hosted Zone. Once it’s created, you’ll see a list of name servers. If your domain is with another provider, make sure to copy these name server values over to your registrar so traffic routes correctly.”
Requesting an SSL Certificate
“Now that the hosted zone is ready, let’s secure it with an SSL certificate. For that, we’ll use AWS Certificate Manager or ACM. Good news: public SSL certificates from ACM are free! Just remember, if you’re planning to use the certificate with CloudFront, it has to be created in the US East (N. Virginia) region.”
Adding Domains and Subdomains
“Inside ACM, request a certificate and enter your domain. You can also add subdomains like www.example.com or even a wildcard like *.example.com to cover all future subdomains. This flexibility ensures your certificate works across multiple endpoints.”
Domain Validation
“Next comes validation. ACM needs to confirm that you actually own the domain. The easiest method is DNS validation, where ACM gives you CNAME records to add to Route 53. Since our hosted zone is already set up, we can simply let AWS create those records automatically. Once that’s done, the certificate will move from Pending Validation to Issued.”
Verification and Next Steps
“You can check the status in both ACM and Route 53. Once issued, the certificate is active and ready to secure your services. With this setup, you can now link your custom domain to API Gateway, CloudFront, S3, EC2, and more.”
“And that’s it! You’ve just set up your custom domain and secured it with an SSL certificate on AWS. In the next video, I’ll show you how to actually connect this domain to an API Gateway so your applications can use it.
If you found this video helpful, don’t forget to hit that Like button, subscribe to the channel, and tap the bell so you never miss a tutorial. And if you have any questions, drop them in the comments — I’d love to help you out.
#aws route53#aws certificate manager#aws acm ssl#aws ssl certificate#aws hosted zone#route53 hosted zone setup#aws domain setup#aws dns tutorial#aws cloudfront ssl#api gateway custom domain#aws tutorial 2025#esthytech#cloud computing tutorial#aws step by step#domain and ssl setup#education
Playlists
• How to Launch an EC2 Instance in AWS | Ste...
• AWS CLI Configuration from Scratch: IAM Gr...
Chapters,
-0:00 – 0:30 Intro
-0:30 – 6:30+ Main Content
-6:30 – End Outro:
Social media
www.linkedin.com/in/egbe22
Document
https://docs.google.com/presentation/...
Thanks for watching,
Информация по комментариям в разработке