route53

Update 29/01/2019 Since AWS Amplify is out, please find newer version [here]({{ site.baseurl }}/cloud/Migration-to-Amplify/) Update 09/02/2018 I’ve updated this article to remove the EC2 used for draft check (for CostSaving), I’m now using S3 bucket with a custom _config.yml. Requirement: Before reading this article, please find those how-to to publish simple static Jekyll website to S3 using ACM SSL and CloudFront CDN. here, here, or here I know, you will told me, why are you using such workload to publish simple blog, It sounds crazy!...

In this post, you will find how to update AWS Route53 from your current public IP (ISP) and how to use EC2 instance metadata to change your DNS A Record. Requirements To use this script, you will need: awscli (pip install awscli) dig (apt-get install dnsutils) Update Route53 with your current home Public IP First, I was facing an issue with my current ISP with non-static IP address, so I found a useful script to update AWS Route53 daily from my RaspberryPi....