Set up WWW Domain Redirect

Chapter Comments
1

From @jayair on Mon Apr 10 2017 01:09:47 GMT+0000 (UTC)

Link to chapter - http://serverless-stack.com/chapters/setup-www-domain-redirect.html

Copied from original issue: https://github.com/AnomalyInnovations/serverless-stack-com/issues/66

2

From @pjamieson on Mon Jul 03 2017 20:01:42 GMT+0000 (UTC)

Rather than create a second CloudFront Distribution, why not just add the alias www.[my-domain].com to the Route53 Record Sets for [my-domain]ā€“pointing to the first distributionā€“then add www.[my-domain].com to that first distributionā€™s Alternate Domain Names? That seems to work fine. Am I missing something?

3

From @jayair on Mon Jul 03 2017 20:33:01 GMT+0000 (UTC)

@pjamieson The reason we set up a redirect on our alternate domain is for SEO purposes. Not necessarily for ranking but because we donā€™t want two versions of our domain active. By re-directing one (the www or apex domain) to the other we are telling the search engines to use one as opposed to both. I hope that makes sense.

4

From @pjamieson on Mon Jul 03 2017 20:45:12 GMT+0000 (UTC)

Thanks, @jayair. That makes sense.

5

From @jayair on Mon Jul 03 2017 21:12:26 GMT+0000 (UTC)

@pjamieson Just added a small note to the chapter https://github.com/AnomalyInnovations/serverless-stack-com/commit/9b67ea34af928bf38025b882b2e6181a6df082cf.

6

From @x11joe on Sat Nov 11 2017 12:02:09 GMT+0000 (UTC)

Iā€™m getting the following error on this step, com.amazonaws.services.cloudfront.model.CNAMEAlreadyExistsException: One or more of the CNAMEs you provided are already associated with a different resource. (Service: AmazonCloudFront; Status Code: 409; Error Code: CNAMEAlreadyExists; Request ID: e21a6bde-c6d7-11e7-9415-837f645450a5), any ideas?

My bucket name is definitely different, so not sureā€¦

7

From @jayair on Sat Nov 11 2017 19:37:26 GMT+0000 (UTC)

@x11joe This usually has to do with a CloudFront distribution having a CNAME already listed as the one you are trying to add. On which screen are you seeing this?

8

From @x11joe on Sat Nov 11 2017 20:10:14 GMT+0000 (UTC)

I am seeing this on the part where you say ā€¦ Scroll down to the Alternate Domain Names (CNAMEs) and use the www version of our domain name here.

It shows up at the bottom, Iā€™ll try and get a screenshot.

ā€¦

Wellā€¦ this is going to sound stupid but I tried just now and its working all the sudden?? Maybe this happened because I was doing test with the domain name prior on another serverless tutorial and it takes like 24 hours for it to remove itā€™s self? Not sure. Maybe this post will help someone.

9

From @jayair on Sat Nov 11 2017 20:14:39 GMT+0000 (UTC)

@x11joe Yeah this can happen. Both the domain setting part and the CloudFront distributions take some time to apply their changes.

10

From @johnnybigert on Mon Nov 27 2017 15:09:01 GMT+0000 (UTC)

I just registered a domain (letā€™s call it ā€œmysite.comā€) and it shows the Notes app correctly. The s3 url and the cloudflare distribution url also show the Notes app. When trying to get the redirect from www.mysite.com to work, I get the following behavior:

http://www-xxx-notes-app-client.s3-website-us-east-1.amazonaws.com redirects correctly to mysite.com. However, http://www.mysite.com/ and xxx.cloudfront.net (which is the www cloudfront distribution url) both give

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
  <Code>AccessDenied</Code>
  <Message>Access Denied</Message>
  <RequestId>xxx</RequestId>
  <HostId>xxx</HostId>
</Error>

I have looked through the settings of the s3 redirect bucket, the www cloudfront distribution and the hosted zone record sets and they seem correct. Any ideas what to do?

2 Likes
11

Iā€™ve just run into this myself and was wondering if you resolved it.

Thanks

12

Which issue are you referring to?

13

I have exactly the same problem, did you find the solution?
many thanks.

14

I think @rjison9000 refers to the ā€˜Access Deniedā€™ problem.

15

Whats the issue you are having?

16

I have already solved my problem with this https://github.com/AnomalyInnovations/serverless-stack-com/issues/66#issuecomment-347220022

thank you very much

2 Likes
17

if its only in effect a redirect, we could avoid route 53 and cloudfront and save ourselves some money a month by doing it from the registrars website, no?

18

You could but the cost for this extremely small.

19

Why create a CloudFront distribution for the www redirect? Is it necessary?

Or could you have the alias record point directly to the S3 bucket?

Thanks.

20

I think you could. We used the CF for the sake of completeness.