Looks like my main web server instance is costing less than $2 a month on a T3 Micro. That’s a spot instance with a fairly high bidding price set so that it’s very unlikely to ever be outbid and is still the cheapest way to provision EC2 capacity.
By the same token, my database server is also a T3 micro instance and that’s looking to cost just under $7 a month on demand – same uptime as the web server so you can see there’s a $5 saving.
The bamboo server is having to run on a medium server and that’s used around $27 this month. Don’t you just love java?
Still got $300 of credit in my account so there’s no massive rush to move off the on demand instances right now. Maybe I should think about it though.
Workmail is $4 per user per month plus tax. Route53 is $0.50 per domain per month, there’s no getting around that. If I can keep my monthly bills less than $30 a month that would certainly keep my wallet happy.
Need to do a fair bit more work with bamboo to see if I can get it running on something a little less powerful or spot instance it. We’ll see.
Not a single server outage in the last three weeks. Which is great, it means that I’ve gotten everything set up properly as far as server updates, security groups and maintenance are concerned.
Bamboo seems to be doing what it’s meant to do and is rebooting the servers nightly. Everything seems to be working properly with regards to database backups and everything. I need to double check what the monthly cost is looking like when I start to run out of promotional credit at the end of this year. Could be quite costly.
Just one week until I start my new job. Excited is an understatement. Can’t wait to get going. My playing around with bamboo was in preparation for this, and it seems to be running pretty well – it’s updating and rebooting both of my ec2 instances nightly using AWS tasks and emailing me using SES to let me know whether the job has passed or failed.
Everything seems fairly stable. Bamboo itself is the biggest server I’ve got running in ec2, but it’s Java – and Java likes to eat all of the RAM so, it is what it is.
Make sure that bamboo isn’t backed off to the RDS instance you deleted, and if it is, make sure you take that final snapshot so that you can easily move it over. Oh, also be aware that mariadb isn’t compatible with bamboo unless you throw in some startup arguments.
Since we’ve got a dedicated DB server, not running as a spot instance now (so it shouldn’t just disappear whenever the hell it wants) and we’re not running RDS, I’ve re-implemented nightly sql backups to S3.
The only way to use Amazon’s free SSL certificates is if you pipe them through something like cloudformation, use them with cloudfront or a load balancer.
Tried that for December and it turns out its fairly expensive to run an ELB for a month – it’s all fine and dandy whilst I’ve got EDU credit to burn through but I can’t afford $20 a month to shortcut an easy way to SSL cert up the site.
I started to look at certbot and lets encrypt as an automatic way of getting a cert in place, changed my apache config and here we are – running through a straight connection on port 443 to the web server.
To be fair, it was a little silly having a load balancer in front of a single web server, but I didn’t have the time to do anything else with it.
I’ve got a little bit of time now, so setting things up properly.
It’s always a good idea not to forget your password. Especially to your blog, especially when you haven’t posted to it for months.
So, yeah, it’s also a good idea to not remember your password and then be fooled by it not working because you’ve locked your account out yet there’s no visual feedback of having done so.
I find more and more that I’m just letting my phone randomly create a password for me/store it in my keychain – seems better that way, plus when I do actually start forgetting important things it won’t matter, because my phone will for all intents and purposes be me anyway.