How to set cname for S3 bucket using Amazon Route 53?

I create a personal website for myself, and I decided to host it on Amazon S3. I am also trying to use Amazon Route 53 for a name server, but I am having problems with its operation. I am trying to configure a CNAME that points my domain name (bret-truchan.com) into a bucket.

My bucket name is bret-truchan.com. It is configured as a website, and endpoint browsing works just fine: http://bret-truchan.com.s3-website-us-east-1.amazonaws.com/

I added four Amazon name servers to my DNS through the DNS provider console.

Here is my bucket setting:

My amazon bucket setup

Here are my Amazon Route 53 entries:

My Amazon Route 53 record sets

CNAME. , CNAME *.bret-truchan.com. . , CNAME. , CNAME , .

enter image description here

ping:

ping test

! !

+5
3

, ping - . ICMP- - , - . , , - -, (, Amazon) DROP .

:

$ host bret-truchan.com
$ host www.bret-truchan.com
www.bret-truchan.com is an alias for bret-truchan.com.s3-website-us-east-1.amazonaws.com.
bret-truchan.com.s3-website-us-east-1.amazonaws.com is an alias for s3-website-us-east-1.amazonaws.com.
s3-website-us-east-1.amazonaws.com has address 207.171.163.1
$ HEAD www.bret-truchan.com
404 Not Found
Date: Sat, 19 Nov 2011 02:35:15 GMT
Server: AmazonS3
Client-Date: Sat, 19 Nov 2011 02:35:15 GMT
Client-Peer: 207.171.163.213:80
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
X-Amz-Error-Code: NoSuchBucket
X-Amz-Error-Detail-BucketName: www.bret-truchan.com
X-Amz-Error-Message: The specified bucket does not exist
X-Amz-Id-2: MKHMddVEYia5cV0iU33QLg7vt6FgM69jyu+jKjTsh1aVuUR8seGwQQT2sfZrSlu9
X-Amz-Request-Id: 6681133093178B5F

, , www.bret-truchan.com - , bret-truchan.com. , 404.

ping, , Amazon.

+6

, Google, AWS.

2.1:

-, . , - example.com Amazon S3, example.com. - www.example.com, www.example.com. example.com www.example.com.

+2

bret-truchan.com. .

I ran into the same question and it sorted it out for me. It would be nice if you could easily rename the bucket and should not recreate it. Small touches like this will make AWS much less awkward.

+1
source

All Articles