I want to redirect Internet traffic from my domain (e.g., example.com) to another domain (e.g., example.net). How can I do this?

Use the following procedure to redirect your domain. In this example, we redirect example.com to example.net.
 
Requirements
  • A hosted zone for the domain example.com is hosted in Amazon Route 53.
  • You have permissions to add resource records to the hosted zone of example.com.
  • You have permissions to create an Amazon S3 bucket.
  • You are able to create an S3 bucket with the exact name for example.com.
Note: The sites must be HTTP, because the redirect cannot connect to S3 over HTTPS.
 
  1. In the Amazon S3 console, create an S3 bucket with the exact name as example.com.
    Note: S3 bucket names must be globally unique. If the bucket name you need is already in use, this solution cannot be used.
  2. Choose the bucket you just created, and then choose Properties. Expand the Static Website Hosting dropdown menu, and then select Redirect all requests to another host name.
  3. In the Redirect all requests to another host name field, enter example.net and then choose Save.
  4. In the Route 53 console, select the hosted zone named example.com.
  5. Create a resource record for example.com with the following values:
    Record Type: Choose A IPv4 address.
    Alias: Choose Yes.
    Alias Target: Select the blank value field, expand the drop down menu, and then choose your S3 bucket under header S3 Website Endpoints.
    Routing Policy: Choose Simple.
    Evaluate Health Target: Choose No and then choose Create.
    Note: The drop-down menu might take a few moments to populate your bucket name.
You should now be able to redirect example.com to example.net. You can confirm this by browsing to example.com or CURL to example.com. You should see “301 Moved Permanently” in your curl output, redirecting to example.net.

domain redirect, Route 53, Simple Storage Service, S3, S3 bucket, HTTP, HTTPS


Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2016-12-09