Amazon Aurora DSQL Pricing

Data transfer costs

The pricing below is based on data transferred “in” and “out” of Aurora.

AWS customers receive 100GB of data transfer out to the internet free each month, aggregated across all AWS Services and Regions (except China and GovCloud). The 100 GB free tier for data transfer out to the internet is global and does not apply separately or individually to AWS Regions.

Except as otherwise noted, prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a billing address in Japan, use of AWS is subject to Japanese Consumption Tax.

Amazon RDS Extended Support costs

• RDS Extended Support pricing per hour

  Select to see details on Amazon RDS Extended Support costs

  The RDS Extended Support price you are charged depends on the engine version, AWS Region, and the number of calendar years since standard support expired for that version. To learn more about when year 1 and 2 or year 3 pricing begins for a specific engine major version, go to the Amazon Aurora documentation.

  Partial hours are billed in one-second increments with a 10-minute minimum charge following a billable status change such as creating, starting, or modifying.

  *Amazon RDS Extended Support year 3 pricing is only available for Amazon Aurora PostgreSQL-Compatible Edition.

RDS Extended Support pricing example

If you have an instance on Aurora PostgreSQL-Compatible 12, this version reaches end of standard support on February 28, 2025. If you deploy in US East (Ohio), you will be charged $0.100 per vCPU-hr between March 1, 2025 to February 28, 2027. Starting March 1, 2027, you will be charged $0.200 per vCPU-hr.

Aurora pricing examples

Example 1: Aurora Serverless v2 pricing with Aurora Standard

Example 2: Aurora Serverless v2 pricing with Aurora I/O-Optimized

Examples of using Aurora Standard Reserved Instances with Aurora I/O-Optimized

You can reuse your existing Aurora Standard Reserved Instances (RI) with Aurora I/O-Optimized. To fully utilize the benefits of your RI discounts with Aurora I/O-Optimized, you can purchase 30% additional RIs similar to your current RIs. The table below shows examples of how to estimate additional RIs when using Aurora I/O-Optimized. If the required RIs are a fraction, you can take advantage of the size flexibility available with RIs to get to a whole number as shown below. In the examples below, current RIs refer to the Aurora Standard RIs you have today and additional RIs refer to the number of Aurora Standard RIs you must purchase to maintain your current RI discounts when using Aurora I/O-Optimized. If you choose not to purchase additional RIs, On-Demand rates will apply.

Examples using database storage and I/O operations:

Let’s assume you have an Aurora database and you start with a 1,000 GB database at the beginning of the month (30-day period) that is growing 2% or 20 GB daily. Let’s also assume the same database reads 350 data pages from storage per second to satisfy the queries running on it. Finally, let’s assume your application makes changes to the database affecting an average of 100 data pages per second. We want to calculate the storage and I/O cost of running this workload with Aurora Standard and Aurora I/O-Optimized storage in US East (N. Virginia).

Example 1: Pricing with Aurora Standard

Example 2: Pricing with Aurora I/O-Optimized

For this workload, you will get 19.8% storage cost savings with Aurora I/O-Optimized.

Examples using Aurora Global Database

Let’s assume you have an Aurora Global Database where the primary Region has two instances, consuming 80 GB of storage and performing 45 million write I/O operations and 5 million read I/O operations per month. Say the secondary Region has one instance serving 5 million read I/O operations per month. We want to calculate the cost of running a Global Database with US East (N. Virginia) as the primary Region and US West (Oregon) as the secondary Region.

Example 1: Pricing with Aurora Standard

Example 2: Pricing with Aurora I/O-Optimized

Example using Backtrack

Let’s assume your Aurora database is generating 10,000,000 change records per hour and you want to backtrack up to 10 hours in the past. We want to calculate the backtrack cost for this scenario in US East (N. Virginia).

Examples using Data API

Example 1: Data API pricing with mixed INSERTS and read requests

Data API is called to query Aurora PostgreSQL-Compatible with the ExecuteStatement API call. There are 4.1 million API requests a month in total. 2.1 million of the of the 4.1M requests are inserts into Aurora. Each has data in an API payload size of 64 KB/request. 2 million of the 4.1M total requests read Aurora data. Of these, 1 million had a data returned payload of less than 32KB and 1 million had a payload size between 32.01KB up to 64KB.

Example 2: Data API pricing with free tier

Data API is called to query Aurora PostgreSQL-Compatible with the ExecuteStatement API call. There are 300,000 API requests a month. All of the API requests return 64 KB of data payload so each request will be charged as 64 KB / 32 KB = 2 requests. 

Example 3: Data API pricing using all request types

Data API is called to query Aurora PostgreSQL-Compatible using all five API Calls (BeginTransaction. CommitTransaction, RollbackTransaction, ExecuteStatement, BatchExecuteStatement. There are 1.2 billion API requests a month. None of the requests return or send more than 32KB of data payload. 

Example using snapshot or cluster export

Let’s assume you have a 100 GB snapshot and you use filtering to select a 10 GB table from this snapshot to export to Amazon S3.