I’ve looked pretty hard at moving my fairly large Postgres RDS to Aurora and the pricing is just very scary. I have a single 100GB instance running on fairly minimal hardware and serving a Django site with 6k monthly visitors. My usage is pretty concentrated during 9-6pm EST as I mainly serve US law firms and investment funds. Any idea if that will end up costing me a fortune to go Aurora? I’m worried about all of those requests in a short amount of time leading to it spinning up a lot of instances.
Aurora's autoscaler is fully in your control. Aurora Serverless is usage-based, but regular Aurora is just an AWS-optimized Postgres distro. You should not receive any surprise billing based on scaling, unless you specifically configure it to do so. Based on those usage patterns you explained you could do a scheduled scaling event that would scale up your Aurora cluster to have more capacity during business hours. If its a read-heavy workload then read replicas are a cheap and easy way to scale.
I don't think AWS RDS scales like that with "a lot of instances". The only time you would have so many instances is from how many read replicas you setup, and if you have a standby instance. RDS isn't like an EC2 ASG. I might be wrong though ='(
At your current scale, just adding a slave for redundancy and hot take over should be enough?
There's also the aurora serverless way which may be interesting since your workload is only a few hours a day. Scale up automatically during the peak and wind down the rest of the time.
[+] [-] geoduck14|5 years ago|reply
I feel like a fool.
[+] [-] iav|5 years ago|reply
[+] [-] reilly3000|5 years ago|reply
[+] [-] kyriakos|5 years ago|reply
[+] [-] x86_64Ubuntu|5 years ago|reply
Source: An AWS Certs Scrub
[+] [-] feydaykyn|5 years ago|reply
There's also the aurora serverless way which may be interesting since your workload is only a few hours a day. Scale up automatically during the peak and wind down the rest of the time.
[+] [-] pbalau|5 years ago|reply
Define a fortune.
[+] [-] alphabettsy|5 years ago|reply
[+] [-] chrishynes|5 years ago|reply