James Thorpe

Dec 30, 2019 AWS DNS

I used to have a fairly static home IP, with a DNS entry pointed at it that I manually updated on the rare occasion it actually changed. We moved in March '18, and with the move came a new internet provider - the IP now changes frequently. I've finally got around to sorting out a dynamic DNS for those times I need it.

Dec 10, 2018 AWS Site

In my last post, I looked at how I configured and started using Wyam to build my new site. After finishing up that post and getting things working locally, I then figured out how to get things served from AWS.

I created a new S3 bucket, with the same name as my domain (james.pawsforthorpe.co.uk), and configured the properties on it to include static website hosting. This gives it an AWS domain - in my case, http://james.pawsforthorpe.co.uk.s3-website.eu-west-2.amazonaws.com/. A quick CNAME entry in my DNS settings later, and I was up and running. At this point, I was still manually uploading files through the AWS console website - this now needed to change.

Being a .NET house, we use the AWS Powershell Tools at work to do some programmatic things - I didn't see any reason to do any different here. First job was to create an IAM user to allow programmatic access. Best practices are to limit permission to exactly what's needed.