What is "CreateDBInstance:0014" and "CreateDBInstance" API operations for "RDS:ChargedBackupUsage (GB-Month)" usage type?

Question

Hi there,

I'm checking what usage in AWS is not tagged with the 3 tags I usually have (Env, Role, State) and I see the following.
Could you help me to get from where it's coming since I've all of my instances tagged and the option that copy tags to snapshot is also enabled?

![Enter image description here](/media/postImages/original/IMu18KPn3dQ6-czrFH6lz6_g)

Val · Answer

The subject and body appear to be asking 2 different questions. I assume you're interested in knowing why RDS:ChargedBackupUsage is untagged. I am aware of 2 possible cases: 
1/ orphaned snapshots have no DB instance to refer to, hence no reference to instance tags either. In Cost Explorer and Cost and Usage Report, costs for RDS orphaned snapshots aggregated in a single, untagged item.
2/ Short-lived instances (less than one hour) might not get time to export tags. As a result, tags might not get applied to snapshots of short-lived instances.

If you have an AWS support option, I recommend opening a support case and support engineer can look into your AWS account and help trace those untagged charges back to specific snapshots / instances.

SteveC · Answer

Just for reference to others trying to understand each of the types of charges.

```
  CreateDBInstance:0002   MySQL                                                
  CreateDBInstance:0003   Oracle Standard Edition 1 (Bring Your Own License)  
  CreateDBInstance:0004   Oracle Standard Edition  (Bring Your Own License)   
  CreateDBInstance:0005   Oracle Enterprise Edition (Bring Your Own License)  
  CreateDBInstance:0006   Oracle Standard Edition 1                            
  CreateDBInstance:0008   SQL Standard Edition (Bring Your Own License)       
  CreateDBInstance:0009   SQL Enterprise Edition (Bring Your Own License)     
  CreateDBInstance:0010   SQL Express Edition                                  
  CreateDBInstance:0011   SQL Web Server                                       
  CreateDBInstance:0012   SQL Standard Edition                                 
  CreateDBInstance:0014   PostgreSQL                                           
  CreateDBInstance:0015   SQL Enterprise Edition                               
  CreateDBInstance:0016   Aurora MySQL                                         
  CreateDBInstance:0018   MariaDB                                              
  CreateDBInstance:0019   Oracle Standard Edition 2 (Bring Your Own License)  
  CreateDBInstance:0020   Oracle Standard Edition 2                            
  CreateDBInstance:0021   Aurora PostgreSQL                                    
  CreateDBInstance:0022   Amazon Neptunen
  CreateDBInstance:0023   Amazon DocumentDB
  CreateDBInstance:0028   IBM Db2 (Bring Your Own License)
  CreateDBInstance:0402   SQL Server SE (AWS-provided media)
  CreateDBInstance:0403   SQL Server Ent (AWS-provided)
```

It however is misleading, we have about $200 per day within this cost API operation, however I can assure you that we don't create instances every day. It's as if the usage is also dumped into this category?

Nutri · Answer

Guys, does anyone even understand what exactly this CreateDBInstance:0014 means?
Why do I have two db.t3.small databases on one account and this operation takes $3 per day there, and on another account one database db.t3.micro, but here it is already $12.5 per day?
When I switched to RDS in the official pricing, I saw a price of $0.021 per hour, which is approximately $0.50 per day. Why such an overprice?

What is "CreateDBInstance:0014" and "CreateDBInstance" API operations for "RDS:ChargedBackupUsage (GB-Month)" usage type?

Add your answer

Relevant content