Hey everyone! I'm currently using MySQL on AWS RDS with a small production load. Right now, I'm on a db.t3.micro instance, but I've been considering upgrading to a db.t4g.small because of its pricing efficiency. However, I've encountered a confusing issue: when I try to create a new database with a Multi-AZ setup, I only see T4G options if I select the free tier and a single-instance deployment. I want to set up a Multi-AZ DB cluster with three T4G instances, which would give me two cores and 2GB of RAM, but that doesn't seem feasible without going through the free tier first. Has anyone else faced this issue? What could be the reason T4G instances are only available under certain conditions? Thanks in advance!
4 Answers
Here are some useful links for more information that might help:
- [AWS Databases](https://aws.amazon.com/products/databases/)
- [AWS RDS](https://aws.amazon.com/rds/)
- [AWS DynamoDB](https://aws.amazon.com/dynamodb/)
- [AWS Aurora](https://aws.amazon.com/aurora/)
- [AWS Redshift](https://aws.amazon.com/redshift/)
- [AWS DocumentDB](https://aws.amazon.com/documentdb/)
- [AWS Neptune](https://aws.amazon.com/neptune/)
Try looking up more details there!
Have you checked which availability zone you're trying to deploy in? Sometimes the options for instances can vary based on that!
You might want to consider using Aurora as an alternative. It could simplify things and might provide the performance you're looking for without the hassle of the RDS intricacies.
Honestly, it seems like this is more about the AWS UI not being very intuitive for database setups. I can actually see T4G instances for production with Multi-AZ deployment, but the options can feel limited or opinionated based on the scenario they think you should choose. It's there, you just have to play around a bit!
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads