Aurora Plus Cost
Malka Sedano
Amazon Relational Database Service (Amazon RDS) for MySQL is a fully managed, open source, relational database that makes it easier to set up, operate, and scale MySQL databases in the cloud. Amazon RDS for MySQL provides you with the flexibility to customize your databases for your needs, including:
New AWS customers can get started with RDS for MySQL for free as part of the AWS Free Tier. The RDS for MySQL Free Tier includes 750 hours on a selection of Single-AZ instance databases, 20 GB of General Purpose SSD (gp2) storage, and 20 GB of storage for automated database backups each month for one year.
Running your DB instance as a Multi-AZ deployment provides high availability and advanced data durability. When you create a Multi-AZ deployment, RDS for MySQL provisions and maintains a standby instance in a different AZ.
RDS for MySQL will perform an automatic failover to one of the standby DB instances in the event of a planned or unplanned outage that affects the primary DB instance. The two standby DB instances serve read-only workloads.
On-Demand database (DB) Instances let you pay for compute capacity by the hour your DB instance runs. On-Demand DB Instances have no long-term commitments, freeing you from the complexities and costs of planning, purchasing, and maintaining hardware as well as transforming what are commonly large fixed costs into much smaller variable costs.
Amazon RDS for MySQL T4g and T3 DB instances run in Unlimited mode, which means that you will be charged if your average CPU utilization over a rolling 24-hour period exceeds the baseline of the instance. CPU Credits are charged at $0.075 per vCPU-Hour. The CPU Credit pricing is the same for all T4g and T3 instance sizes across all regions and is not covered by Reserved Instances.
You may designate database instances as a Reserved Instance by calling to the Purchasing API or selecting the Reserved Instance option in the AWS console. When you designate a database instance as a Reserved Instance, you must designate a Region, instance type, and quantity for the applicable Reserved Instances. The Reserved Instances may only be used in the designated Region.
AWS may terminate the Reserved Instance pricing program at any time. In addition to being subject to Reserved Instance pricing, Reserved Instances are subject to all data transfer and other fees applicable under the AWS Customer Agreement or other agreement with AWS governing your use of AWS services.
*This is the average monthly payment over the course of the Reserved Instance term. For each month, the actual monthly payment will either equal the actual number of hours in that month multiplied by the hourly usage rate or the number of seconds used in that month multiplied by the hourly usage rate, divided by 3600. The formula you use will depend on the RDS for MySQL instance type you run.
The hourly usage rate is equivalent to the total average monthly payments over the term of the Reserved Instance divided by the total number of hours (based on a 365-day year) over the term of the Reserved Instance.
When you purchase a Reserved Instance, you are billed for every hour during the entire Reserved Instance term you select, regardless of whether the instance is running. The effective hourly price shows the amortized hourly instance cost. This takes the total cost of the Reserved Instance over the entire term, including any upfront payment, and spreads it out over each hour of the Reserved Instance term.
General Purpose gp2 volumes provide you the ability to select from 20 GiB to 64 TiB with a baseline storage performance of 3 IOPS for each GiB. Volumes below 1 TiB in size also have the ability to burst to 3,000 IOPS for extended periods of time. You will be charged for the storage you provision. However, you will not be charged for the I/Os you consume.
General Purpose gp3 volumes provide you the ability to select from 20 GiB to 64 TiB of storage capacity. With gp3 volumes, you can configure storage, IOPS and throughput independently and will be charged for the resources you consume above the baseline. gp3 volumes have a baseline performance of 3,000 IOPS and 125 MB/s throughput.
General Purpose gp2 volumes provide you the ability to select from 20 GiB to 64 TiB of storage capacitywith a baseline storage performance of 3 IOPS for each GiB. Volumes below 1 TiB in size also have theability to burst to 3,000 IOPS for extended periods of time. You will be charged for the storage youprovision. However, you will not be charged for the I/Os you consume.
Amazon RDS io2 Block Express volumes, our next-generation Provisioned IOPs storage, provides high performance, high throughput, and consistent sub-millisecond latency for your production database workloads.
Amazon RDS io2 Block Express volumes are the next generation Provisioned IOPs storage, designed for all your critical database workloads that demand high performance, high throughput, and consistently low latency.
RDS for MySQL provides you the ability to select from 20 GiB to 3 TiB of associated magnetic storage capacity for your primary data set. Magnetic storage is supported for backward compatibility. We recommend that you use General Purpose SSD or Provisioned IOPS SSD for any new storage needs.
For Multi-AZ deployments, when you update your database, write I/O usage will double as Amazon RDS synchronously replicates your data to the standby DB instance. Read I/O usage will remain the same when reading from the database.
A Dedicated Log Volume is an additional storage volume specifically for database redo logs and binlogs that is separate from the volume containing the database tables, making transaction write logging more efficient and consistent. A Dedicated Log Volume is ideal for databases with large allocated storage, high I/O per second (IOPS) requirements, or latency sensitive workloads.
Backup storage is the storage associated with your automated database backups and any customer-initiated DB snapshots. Increasing your backup retention period or taking DB snapshots increases the backup storage consumed by your database.
The Amazon RDS snapshot export provides an automated method to export data within an RDS for MySQL snapshot to Amazon S3 in Parquet format. The Parquet format is up to 2x faster to unload and consumes up to 6x less storage in Amazon S3 compared to text formats. You can analyze the exported data using AWS services such as Amazon Athena, Amazon EMR, and Amazon SageMaker.
Suppose you have a 100GB snapshot and you use filtering to select a 10GB table from this snapshot to export to Amazon S3. To export this data, you would pay 100GB * $0.013 per GB of snapshot size. Subsequent exports of data from the same snapshot are not incremental.
Additional charges apply for encrypting or decrypting data with AWS Key Management Service (KMS). Find more about these charges on the KMS pricing page. Charges also apply for storing exported data in Amazon S3 and for PUT requests made against your S3 bucket. Find more about these charges on the S3 pricing page.
The Amazon RDS for MySQL zero-ETL integration with Amazon Redshift (Preview) provides access to analytics and machine learning (ML) capabilities on petabytes of transactional data. With the RDS for MySQL zero-ETL integration with Amazon Redshift, you are able to remove the need to build and manage complex data pipelines that perform extract, transform, and load (ETL) operations.
You pay for RDS for MySQL and Amazon Redshift resources used to create and process the change data created as part of a zero-ETL integration. These resources include Amazon RDS snapshot export costs to seed and resynchronize your Amazon Redshift data warehouses, change data capture (CDC) data transfer costs for ongoing replication of data changes from source to target, regular RDS I/O and storage used to process change data, and regular Amazon Redshift storage and compute costs for the replicated data.
You have an RDS for MySQL 8.0.28 database and an Amazon Redshift data warehouse running in the US East (N. Virginia) Region. This RDS for MySQL DB instance currently uses 50 GB of General Purpose SSD (gp3) storage capacity that includes provisioned baseline IOPS, has automated backups enabled, and has MySQL binary logging turned on.
When you create a zero-ETL integration with Amazon Redshift for your RDS for MySQL DB instance, a snapshot of the data (50 GB) is created and exported to seed an Amazon Redshift data warehouse. The next day, you change the primary key of a table in your RDS for MySQL DB instance, which results in a resynchronization of the snapshot export to Amazon Redshift. Over the course of 30 days, the database processes 5 GB of data changes.
In this example, the cost to use RDS for MySQL zero-ETL integration with Amazon Redshift in US East (N. Virginia) in the 30 days is 50 GB x ($0.10/GB) initial export plus 50 GB x ($0.10/GB) resynchronization costs plus 5 GB x ($2.00/GB) CDC data transfer, for a total of $20.00. In addition to these costs for the zero-ETL integration, you are responsible for charges from the normal use of Amazon RDS and Amazon Redshift to process the replicated data, such as I/O, storage, and compute costs.