technology

Adding Cloudfront

You should now be reading Take the First Step via Amazon Cloudfront. There is no significant benefit at this point, but the move to Cloudfront is a necessary prelude to adding a SSL certificate.

The move was pretty easy:

  1. Create the distribution in cloudfront
  2. Update Route53 to point to cloudfront rather than s3
  3. Wait for the good news:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
$ dig ideoplex.com

; <<>> DiG 9.8.3-P1 <<>> ideoplex.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60651
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ideoplex.com.			IN	A

;; ANSWER SECTION:
ideoplex.com.		46	IN	A	54.230.52.82
ideoplex.com.		46	IN	A	54.192.55.193
ideoplex.com.		46	IN	A	54.230.53.75
ideoplex.com.		46	IN	A	54.192.54.180
ideoplex.com.		46	IN	A	54.192.55.198
ideoplex.com.		46	IN	A	54.230.53.79
ideoplex.com.		46	IN	A	54.230.52.175
ideoplex.com.		46	IN	A	54.230.52.164

;; Query time: 30 msec
;; SERVER: 10.0.1.1#53(10.0.1.1)
;; WHEN: Sat Sep 12 15:06:15 2015
;; MSG SIZE  rcvd: 158

Unfortunately, I didn’t think about Cloudfront caching. By default, Cloudfront will cache objects for 24 hours. That’s a long time to wait for new posts.