RDS Set Up and AZ Issues

Question

I was told by an AWS Rep that I could limit costs from RDS by restricting the subnets my db had access to.
My db worked before I did this, so I know it is the problem, but in a caviler manner, I deleted my subnets besides the one I wanted my new db in.

Now I get the following error when attempting to create, despite having since created subnets in all the availability zones listed in the error.

"You can't create a db.t3.micro database instance because no subnets exist in availability zones with sufficient capacity for VPC and storage type : gp2 for db.t3.micro. Please first create at least one new subnet; choose from these availability zones: us-east-1d, us-east-1b, us-east-1a, us-east-1c, us-east-1f."

Any Idea?

Answer

Hi, what is the tenancy of your vpc?
dedicated or default?

Answer

For RDS you need a minimum of 2 subnets configured. Ensure you have updated your subnet group’s configuration

Your error message also reads your CIDR range is too small. I’d check the number of free IP addresses available.

Your VPC must have at least two subnets. These subnets must be in two different Availability Zones in the AWS Region where you want to deploy your DB instance. A subnet is a segment of a VPC's IP address range that you can specify and that you can use to group DB instances based on your security and operational needs.

Answer

The number of subnets in your db subnet group do not impact the price. More subnets gives RDS more flexibly in placement of your instances.

RDS Set Up and AZ Issues

Relevant content