I'm using MySQL on AWS RDS for my production workload and currently have a db.t3.micro instance. I wanted to scale up to db.t4g.small since my traffic is light and I'd like to utilize the T4G options. However, I'm running into a problem. The only time I see T4G instances available is when I choose the 'Free tier' and 'Single-AZ DB instance deployment'. When I attempt to create a 'Multi-AZ DB cluster deployment', the T4G options seem to vanish. I initially thought about switching to a Multi-AZ setup to have a main node and a read replica, but it looks like T4G is only accessible under specific configurations. Can anyone explain why T4G only shows up in the free tier and how I might be able to achieve a proper deployment without needing a lot of resources?
4 Answers
You might want to check the engine version you are using as that could also impact the availability of instance types. Make sure it’s compatible with the T4G class you're aiming for.
Just a thought, which availability zone are you trying to deploy in? Sometimes availability can affect the types of instances shown to you.
It sounds like you're encountering the limitations of AWS's interface. Depending on the specific settings you choose, AWS may only display certain instance types like T4G based on the configurations they think are best. Make sure you're selecting 'Multi-AZ DB instance deployment' to see all your options. It seems that T4G does become available in production setups too, but it might be dependent on the selected instance size and capacity planning on your part.
Have you considered using Aurora? It could save you a lot of the hassle involved with managing the instances directly. Aurora handles scaling for you and might fit your needs without the complexities of figuring out the instance types.
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads