Someone else created an S3 bucket with your subdomain's name? Krishan walks through how to stop traffic going to the wrong account and reroute it, either with a new subdomain or by setting up CloudFront as an alternate domain.
0:00 Introduction
0:33 Why this issue occurs
0:59 Delete the existing DNS record
1:23 Option 1: Use a different subdomain name
2:19 Create a Route 53 record for the new subdomain
2:56 Option 2: Set up an alternate domain in CloudFront
3:22 Add subdomain as alternate domain name
3:48 Assign a TLS certificate
4:22 Create Route 53 record for CloudFront distribution
4:54 Report malicious buckets to AWS Trust & Safety
5:12 Closing
For more information, see the Knowledge Center article:
https://repost.aws/knowledge-center/route-53-stop-routing-different-account
This video is part of the AWS Knowledge Center series: trusted, expert-reviewed answers to common questions across AWS services.
Subscribe to AWS: https://go.aws/subscribe
Create a free AWS account: https://go.aws/signup
Try AWS for free: https://go.aws/free
Connect with an expert: https://go.aws/contact
Explore more: https://go.aws/more
Next steps:
Explore on AWS in Analyst Research: https://go.aws/reports
Discover, deploy, and manage software that runs on AWS: https://go.aws/marketplace
Join the AWS Partner Network: https://go.aws/partners
Learn more on how Amazon builds and operates software: https://go.aws/library
Do you have technical AWS questions?
Ask the community of experts on AWS re:Post: https://go.aws/3lPaoPb
Why AWS?
Amazon Web Services is the world’s most comprehensive and broadly adopted cloud, enabling customers to build anything they can imagine. We offer the greatest choice of innovative cloud capabilities and expertise, on the most extensive global infrastructure with industry-leading security, reliability, and performance.
#AWS #AmazonWebServices #CloudComputing