CODEWITHSUNDEEP
http-redirectamazon-web-servicesamazon-s3dns
Steve
Steve

Reputation: 133

Pointing 1and1 domain to an S3 bucket

I've registered my domain about a month ago (It's a .com, so I need to wait 60 days before being allowed to transfer the domain, which I will do as I'm fed up with 1and1's service)

I created an Amazon S3 bucket with my domain name: example.com and www.example.com.

All my Amazon S3 settings are in order, I've enabled website hosting, I have an index document...

In 1and1, I've set my redirect destination for example.com to my S3 bucket endpoint.

When I hit save: "Operation Failed, The redirect URL is invalid."

What am I doing wrong?

Upvotes: 2

Views: 3490

Answers (2)

Michael - sqlbot
Michael - sqlbot

Reputation: 179374

You do not have to wait 60 days.

There are two different services that are commonly confused because providers often market then together: domain registrar services and domain hosting.

You can change your hosting provider at any time, by changing the configuration options with the current registrar. This change typically takes effect almost immediately, though conventional wisdom is that it may require up to 48 hours to take effect globally.

Create a new "hosted zone" in Route 53 for your domain. Take note of the four "awsdns" name servers that Route 53 assigns.

Log in to your registrar's admin portal and find the option the change your authoritative name server configuration. Replace the registrar's default name servers with the four provided by Route 53.

You will then use the Route 53 console to create your DNS records, including the appropriate "Alias" records pointing your domain to the S3 web site endpoint.

After the 60 days, you can change the registrar to Route 53, or any other registrar you like, continuing to use the authoritative name servers assigned to your domain by Route 53.

Route 53 is the simplest option for DNS hosting when you are using S3 for static website hosting (or CloudFront or Elastic Load Balancer) simply because of the tight integration provided by Alias records, which offer capabilities that CNAMEs can't and other DNS hosting providers can't, because they don't have direct access to the operational internals of AWS.

Upvotes: 3

Gidon Wise
Gidon Wise

Reputation: 1916

It sounds like you configured your domain name to use a Redirect instead of a CNAME record. Create a CNAME record to your AWS domain.

Here are some instructions:

http://help.1and1.com/domains-c36931/manage-domains-c79822/dns-c37586/enter-a-cname-record-for-your-domain-a643600.html

Sometimes people don't want to create CNAMEs for their root domain and prefer to redirect from example.com to www.example.com

Upvotes: 0

Related Questions