21–30 of 56 posts
Is it common to have a dev environment on AWS? I just use it for production and maybe staging. Staging is scheduled to run during office hours.
Is it common to have a dev environment on AWS? I just use it for production and maybe staging. Staging is scheduled to run during office hours.
Also if you add terraform/ansible and all that jazz to the table. Where else? Infra team needs dev/stage as well.
Just published a tiny CLI utility to save some bucks on AWS development environment while I'm not really working. https://github.com/aramalipoor/aws-cost-saver The idea is to stop/shutdown any resources (such as EC2 instances, RDS databases, ECS tasks, etc.) when you're done for the day and restore them back up next time you continue. Currently it's in a very early stage, a hobby side-project :) Ideally I'm thinking…
Just published a tiny CLI utility to save some bucks on AWS development environment while I'm not really working. https://github.com/aramalipoor/aws-cost-saver The idea is to stop/shutdown any resources (such as EC2 instances, RDS databases, ECS tasks, etc.) when you're done for the day and restore them back up next time you continue. Currently it's in a very early stage, a hobby side-project :) Ideally I'm thinking…
Im very interested in learning about your work flows, like how does a typical day look like? I do all my work on a local pc and only use servers for production. So im interesting in how/why you use the cloud stack
It looks like a nice tool doing it's job well :-) I'd also consider services like provisioned DynamoDB tables or Kinesis streams in this context because there you can also waste lots of money depending on your setup. For example, you could decrease the provisioned read/write capacity for a DynamoDB table or decrease the shards of a Kinesis stream over night. I've discussed these topics in a blog post, in the context…
Is it common to have a dev environment on AWS? I just use it for production and maybe staging. Staging is scheduled to run during office hours.
I guess depends on the size of the company. How else would you constantly test integrations between different services? Especially if some services can't be easily ran on the laptop. Also if you add terraform/ansible and all that jazz to the table. Where else? Infra team needs dev/stage as well.
I find it price gouging that AWS doesn't already implement this on their own within their pricing structure and that you need a 3rd party tooling to do this.
It allows you to create automatic start and stop schedules for your Amazon EC2 and Amazon RDS instances. It uses a combination of CloudWatch/Lambda/DynamoDB to check against tagged instances.
Earlier quoted context omitted.
This is amazing.... Edit: I wonder if you could put this inside of a lambda with just a role.
Thanks. Agree with you, having it in a Lambda with a scheduled trigger or even manual trigger will be really useful.
Depending on my mood I either use the web page or some simple curl aliases to start and stop an instance.