I have a Google Doc containing a bunch of recipes that I have gathered up over the years. Finally (Corona cooking!) it has got a little unwieldy, so a more convenient way to browse the recipes would be really nice. Of course, there are probably a tonne of really great apps for handling that, but it was the perfect excuse to get familiar with OpenAPI 3.0…
Long story short, check out this Github repo, where I pushed the code (so far).
In a recent project at work I stumbled across an annoying gotcha with AWS Batch. In case you don’t know what AWS Batch is there are more details here. In short, it’s a fairly simple way to scale out workloads that happen on an irregular basis. In our case, create a Docker image with everything needed and then run Batch when you have data to analyse. At the end of the day you end up with something similar in functionality to a SGE/PBS/SLURM (insert HPC queueing system here…) HPC cluster, which in previous roles I found were often used for this type of batch job.
AWS is such a powerful tool to get things done quickly, and often cheaply. But it’s still a lurking worry for many that costs could quickly spiral out of control. Since I’m hosting my website here I’d like to know if costs change considerably, so I can act fast to save my credit card if I need to!
This is by no means meant as a comprehensive guide on how to do this, I’m pretty certain that your AWS account manager can help with reading material for that!
In the previous blog post I talked about how I created the static pages for hosting on AWS S3. Since you’re reading this, you might be interested in how I registered the domain and got things deployed. If you want to see how I think you can do this best, read the article backwards since this is the solution that I used in the end. Read from the front of the article if you want to know how I got there!
