Uploading to S3
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.Read more...
Moving to Wyam
I'm in the process of rejigging out my web portfolio (website, email servers etc), and since my day job involves using AWS, I figured now was a good time to begin moving there. I'm also about to embark on some electronics projects, and I wanted to have somewhere to write about what I'm doing. I really don't use my personal site much, so I figured I wanted something simple and static(ish) that I could serve from S3, perhaps with a lambda function or two at some point.
Having seen what other people are doing with the likes of Jekyll, I thought I'd go for a statically generated site too. Being a .NET developer, I wondered what there was in the way of site generator engines that ran on top of .NET Core. A quick search found Wyam, and a Blog post from Scott Hanselman exploring it a little.
That was good enough for me.Read more...