Aws

As you probably know, this website is based on an amazing static website generator Hugo. I’ve been more than happy ever since I switched to it more than two years ago. In the beginning, I deployed website directly from my local machine to the S3 and then invalidated Cloudfront cache as described in the article. This has been working well, but I had to automate it. Website is in Git and sometimes when I’d do something to it I would build and deploy the website, but sometimes forget to push to Git (as we all do, right?...

Background Few months ago (less than 3), I’ve switched my website from Wordpress to Hugo. There I described the process of setting up Cloudfront distribution to serve as a CDN and a simple web-server for the content backed by S3 bucket. One of the challenges was how to serve nested paths (eg. /about-me/) as Cloudfront doesn’t know for “directory index” concept. You can only set index for / uri. To tackle that issue, I’ve used Lambda@Edge function called standard-redirects-for-cloudfront I’ve found on the internet....

I’ve since evolved this script a bit and have published it on GitHub: https://github.com/ivantomica/AWSVault To log in into AWS I prefer to use small function which calls aws-vault utility and gets URL to login to specific AWS account and then opens that AWS account in its own container tab in Firefox. Reason for this is that my natural habitat is terminal, or textual interface in general, so invoking thing from there instead of doing 20 clicks through interface somehow feels better to me....

There is this nice utility which helps you with managing AWS credentials called aws-vault. It is quite nice to use it as it allows ad-hoc login as a specific profile via web browser, without the need for entering your credentials or performing 3 step process to log in, just: aws-vault login profile Where “profile” is specific AWS profile, and voila, you’re in. Besides that, it also keeps your credentials safe in one of the supported backends....