VPC name doesn’t appear while creating RDS

Sometimes I feel like that while learning AWS



Because there are so many small details to learn and in my opinion those details not written well (For me the best RED BOLD ARIALBLACK). If you here and you are reading that article probably you have the same problem that we face with the same situation. Be sure that I steal so much time from me but I’ll be your hero. Let’s start.

If I explain that situation.

I was creating my first RDS instance to learn it by using Ansible module. I was using default-VPC and default-subnet-group etc, It was working well It has been created RDS smoothly. But when I changed my environment with another VPC ID, I couldn’t. You know as every person I googled it, tried every option in Stackoverflow and Github issues. Even reading all that articles doesn’t help to fix.

After that attempts, I decided to use Amazon Console.

As you know while creating RDS there is 4 step

  • Create RDS Instance in console
    • Step 1: Select Engine
    • Options about SQL Engine (Postgre, MySQL etc)
    • Step 2: Production?
      • Environment information (Production or Dev-Test)
    • Step 3: Specify DB Details
      • DB Instance Class
        • Instance type (Reason of Fail)
        • Disk Size
        • Disk Type
        • SQL Password, Username, Identifier
    • Step 4: Configure Advanced Settings
      • Network & Security
        • VPC name
        • Subnet Group
        • VPC Security Groups
        • Database Name
        • Retention Period
        • etc

WTF that there wasn’t my VPC in Listbox.

There is just 1 way to fix it RTFM. So I started to read all documents about RDS. After a long time, In this article, there was my precious exception about VPC.

A VPC can have an instance tenancy attribute of either default or dedicated. All default VPCs have the instance tenancy attribute set to default, and a default VPC can support any DB instance class.

If you choose to have your DB instance in a dedicated VPC where the instance tenancy attribute is set to dedicated, the DB instance class of your DB instance must be one of the approved Amazon EC2 dedicated instance types. For example, the m3.medium EC2 dedicated instance corresponds to the db.m3.medium DB instance class. For more information about the instance types that can be in a dedicated instance, go to Amazon EC2 Dedicated Instances on the EC2 pricing page. For information about instance tenancy in a VPC, go to Using EC2 Dedicated Instances in the Amazon Virtual Private Cloud User Guide.



As a poor man, I was trying db.t2.micro in Dedicated VPC. After I increased DB instance size, I would select my VPC.

Another words, money solved all problems.

I hope that small kid on video and me going to learn how to swim, even those are different oceans.