Contents

AmazonRDS

Each grouping represents a specific way Amazon Relational Database Service (Amazon RDS) measures and bills for resource consumption. Click into a code for additional specifications.

Storage Snapshot

Aurora:BackupUsage

The amount of storage (per GB-Month) used for Aurora automated backups and customer-initiated snapshots. Up to 100% of the database cluster size for backup storage and snapshots created within the backup retention period are free of charge.

Billing Codes

RDS:ChargedBackupUsage

The amount of storage (per GB-Month) used for RDS automated backups and customer-initiated snapshots. Up to 100% of the database cluster size for backup storage and snapshots created within the backup retention period are free of charge.

Billing Codes

RDSCustom:ChargedBackupUsage

The amount of storage (per GB-Month) used for RDS automated backups and customer-initiated snapshots Custom. Up to 100% of the database cluster size for backup storage and snapshots created within the backup retention period are free of charge.

Billing Codes

Aurora:BackupUsage-LimitlessPreview

The amount of storage (per GB-Month) used for Aurora Limitless Preview (now generally available) automated backups and customer-initiated snapshots. Up to 100% of the database cluster size for backup storage and snapshots created within the backup retention period are free of charge.

Billing Codes

System Operation

Aurora:StorageIOUsage

The number of I/O operations for Aurora Standard. An I/O operation includes database page reads (in 16 KB units for Aurora MySQL and 8 KB units for Aurora PostgreSQL) and writes (in 4 KB units). You are not charged for I/O operations with Aurora I/O-Optimized.

Billing Codes

Aurora:SnapshotExportToS3

The amount of data (per GB) exported automatically from Aurora snapshots to S3. Charges are for the full size of the snapshot for every export, even if the data has already been sent to S3.

Billing Codes

RDS:SnapshotExportToS3

The amount of data (per GB) exported automatically from RDS snapshots to S3. Charges are for the full size of the snapshot for every export, even if the data has already been sent to S3.

Billing Codes

Aurora:BacktrackUsage

The backtrack feature allows a user to rewind a database to a previous point in time without having to restore from a backup. Charges are calculated by multiplying the number of change records generated per hour by the number of hours for which backtrack is enabled.

Billing Codes

RDS:CDC-DataTransfer

When using the zero-ETL integration with Redshift as a feature of RDS for MySQL, you are charged for the amount of Change Data Capture (CDC) data (in bytes) transferred from RDS to Redshift.

Billing Codes

Database Storage

Aurora:StorageUsage

The amount of storage consumed (per GB-Month) in Aurora Standard.

Billing Codes

RDS:Multi-AZ-PIOPS-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ Provisioned IOPS (io1) deployments.

Billing Codes

RDS:PIOPS-Storage

The amount of storage provisioned (per GB-Month) for RDS Single-AZ Provisioned IOPS (io1) deployments.

Billing Codes

RDS:GP2-Storage

The amount of storage provisioned (per GB-Month) for RDS Single-AZ General Purpose SSD (gp2) deployments.

Billing Codes

RDS:GP3-Storage

The amount of storage provisioned (per GB-Month) for RDS Single-AZ General Purpose SSD (gp3) deployments.

Billing Codes

RDS:Mirror-GP3-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ (SQL Server Mirror) General Purpose SSD (gp3) deployments.

Billing Codes

Aurora:IO-OptimizedStorageUsage

The amount of storage consumed (per GB-Month) in Aurora IO-Optimized.

Billing Codes

RDS:Multi-AZ-GP3-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ General Purpose SSD (gp3) deployments.

Billing Codes

RDS:Multi-AZ-GP2-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ General Purpose SSD (gp2) deployments.

Billing Codes

RDS:Mirror-GP2-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ (SQL Server Mirror) General Purpose SSD (gp2) deployments.

Billing Codes

RDS:Multi-AZ-StorageUsage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ magnetic deployments.

Billing Codes

RDS:StorageUsage

The amount of storage provisioned (per GB-Month) for RDS Single-AZ magnetic deployments.

Billing Codes

RDS:PIOPS-Storage-IO2

The amount of storage provisioned (per GB-Month) for RDS Single-AZ Provisioned IOPS (io2) deployments.

Billing Codes

RDS:Multi-AZ-PIOPS-Storage-IO2

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ Provisioned IOPS (io2) deployments.

Billing Codes

RDS:Mirror-PIOPS-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ (SQL Server Mirror) IOPS (io1) deployments.

Billing Codes

RDS:Multi-AZCluster-GP3-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ Cluster General Purpose SSD (gp3) deployments.

Billing Codes

RDS:Multi-AZCluster-PIOPS-Storage

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ Cluster IOPS (io1) deployments.

Billing Codes

Aurora:IO-OptimizedStorageUsage-LimitlessPreview

The amount of storage consumed (per GB-Month) in Aurora IO-Optimized Limitless Preview (now generally available).

Billing Codes

RDS:Multi-AZCluster-PIOPS-Storage-IO2

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ Cluster IOPS (io2) deployments.

Billing Codes

RDS:Mirror-PIOPS-Storage-IO2

The amount of storage provisioned (per GB-Month) for RDS Multi-AZ (SQL Server Mirror) IOPS (io2) deployments.

Billing Codes

Data Transfer

DataTransfer-In-Bytes

The amount of data (per GB) transferred into AWS from the internet. Data transferred into AWS does not incur a fee.

Billing Codes

DataTransfer-Out-Bytes

The amount of data (per GB) transferred out of AWS to the internet.

Billing Codes

AWS-In-Bytes

The amount of data (per GB) transferred into AWS. Data transferred into AWS does not incur a fee. If there are two regions in the prefix, the first represents the source region, and the second represents the destination region. If there is only one region in the prefix, the prefix represents the AWS source region.

Billing Codes

AWS-Out-Bytes

The amount of data (per GB) transferred out of AWS. If there are two regions in the prefix, the first represents the source region, and the second represents the destination region. If there is only one region in the prefix, the prefix represents the AWS source region.

Billing Codes

DataTransfer-xAZ-In-Bytes

The amount of data (per GB) transferred into an AWS Availability Zone from another Availability Zone within the same region. Each Inter-AZ data transfer also has a line item for DataTransfer-xAZ-Out-Bytes in which the cost is applied.

Billing Codes

CloudFront-In-Bytes

The amount of data (per GB) transferred into an AWS region from CloudFront. Each CloudFront data transfer also has a line item for CloudFront-Out-Bytes in which the cost is applied.

Billing Codes

CloudFront-Out-Bytes

The amount of data (per GB) transferred out of an AWS region to CloudFront.

Billing Codes

DataTransfer-xAZ-Out-Bytes

The amount of data (per GB) transferred out of an AWS Availability Zone to another Availability Zone within the same region.

Billing Codes

CloudFrontChina-Out-Bytes

The amount of data (per GB) transferred out of an AWS region to CloudFront China.

Billing Codes

CloudFrontChina-In-Bytes

The amount of data (per GB) transferred into an AWS region from CloudFront China. Each CloudFront China data transfer also has a line item for CloudFrontChina-Out-Bytes in which the cost is applied.

Billing Codes

DataXfer-In

The amount of AWS Direct Connect data (per GB) transferred in over a virtual interface. Each AWS Direct Connect data transfer also has a line item for DataXfer-Out in which the cost is applied. If there is a postfix of `dc.3` that indicates the data was transferred over a private virtual interface. Otherwise, the data was transferred over a public virtual interface. The first region in the prefix represents the source region, and the second represents the destination region.

Billing Codes

DataXfer-Out

The amount of AWS Direct Connect data (per GB) transferred out over a virtual interface. If there is a postfix of `dc.3` that indicates the data was transferred over a private virtual interface. Otherwise, the data was transferred over a public virtual interface. The first region in the prefix represents the source region, and the second represents the destination region.

Billing Codes

ServerlessV2

Aurora:ServerlessV2Usage

The number of Aurora capacity unit (ACU) hours for Aurora Serverless v2. Each ACU corresponds to approximately 2 GB of memory and corresponding CPU and networking resources. Scaling works by setting the minimum and maximum number of ACUs to scale between.

Billing Codes

Aurora:ServerlessV2IOOptimizedUsage

The number of Aurora capacity unit (ACU) hours for Aurora Serverless I/O-Optimized v2. Each ACU corresponds to approximately 2 GB of memory and corresponding CPU and networking resources. Scaling works by setting the minimum and maximum number of ACUs to scale between.

Billing Codes

Database Instance

InstanceUsage

The number of DB instance-hours for an Aurora Standard Single-AZ deployment instance. Reserved Instances are charged at either the discounted rate or $0 if fully prepaid (All Upfront). There is a minimum charge of 10 usage minutes if you create, start, or modify a DB instance class.

Billing Codes

Multi-AZUsage

The number of DB instance-hours for an RDS Multi-AZ deployment instance. There is a minimum charge of 10 usage minutes if you create, start, or modify a DB instance class.

Billing Codes

MirrorUsage

The number of DB instance-hours for an RDS Multi-AZ (SQL Server Mirror) deployment instance. There is a minimum charge of 10 usage minutes if you create, start, or modify a DB instance class.

Billing Codes

InstanceUsageIOOptimized

The number of DB instance-hours for an Aurora I/O-Optimized Single-AZ deployment instance. Reserved Instances are charged at either the discounted rate or $0 if fully prepaid (All Upfront). There is a minimum charge of 10 usage minutes if you create, start, or modify a DB instance class.

Billing Codes

Multi-AZClusterUsage

The number of DB instance-hours for an RDS Multi-AZ Cluster deployment instance. There is a minimum charge of 10 usage minutes if you create, start, or modify a DB instance class.

Billing Codes

Provisioned IOPS

RDS:Multi-AZ-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ Provisioned IOPS (io1) deployments.

Billing Codes

RDS:PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Single-AZ Provisioned IOPS (io1) deployments.

Billing Codes

RDS:GP3-PIOPS

The amount of IOPS consumed (per IOPS-Month) over the included baseline of 3,000 IOPS per month for RDS Single-AZ General Purpose SSD (gp3) deployments.

Billing Codes

RDS:Mirror-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ (SQL Server Mirror) Provisioned IOPS (io1) deployments.

Billing Codes

RDS:Multi-AZ-GP3-PIOPS

The amount of IOPS consumed (per IOPS-Month) over the included baseline of 3,000 IOPS per month for RDS Multi-AZ General Purpose SSD (gp3) deployments.

Billing Codes

RDS:IO2-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Single-AZ Provisioned IOPS (io2) deployments.

Billing Codes

RDS:Multi-AZ-IO2-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ Provisioned IOPS (io2) deployments.

Billing Codes

RDS:Mirror-GP3-PIOPS

The amount of IOPS consumed (per IOPS-Month) over the included baseline of 3,000 IOPS per month for RDS Multi-AZ (SQL Server Mirror) General Purpose SSD (gp3) deployments.

Billing Codes

RDS:Multi-AZCluster-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ Cluster Provisioned IOPS (io1) deployments.

Billing Codes

RDS:Multi-AZCluster-IO2-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ Cluster Provisioned IOPS (io2) deployments.

Billing Codes

RDS:Mirror-IO2-PIOPS

The amount of IOPS provisioned (per IOPS-Month) for RDS Multi-AZ (SQL Server Mirror) Provisioned IOPS (io2) deployments.

Billing Codes

Aurora Global Database

Aurora:ReplicatedWriteIO

The Aurora Global Database feature allows an Aurora database to be distributed across multiple Regions. ReplicatedWriteIO charges apply for the number of replicated write I/O operations between the primary Region and each secondary Region in the Global Database, applicable to both Aurora Standard and Aurora I/O-Optimized. Additional charges include duplicate costs for instances, storage, I/O usage, cross-Region data transfer, and any other paid Aurora features.

Billing Codes

Performance Insights

PI_LTR_FMR:Provisioned

The Performance Insights feature provides visibility into the performance of an RDS database. For RDS provisioned instances 7 days of retention are included at no cost or you can enable it for 1-24 months. Charges are per vCPU per month (with the first month billed at a higher rate than the subsequent months). This line item corresponds to charges for additional retention months beyond the first month.

Billing Codes

PI_LTR_AMR:Provisioned

The Performance Insights feature provides visibility into the performance of an RDS database. For RDS provisioned instances 7 days of retention are included at no cost or you can enable it for 1-24 months. Charges are per vCPU per month (with the first month billed at a higher rate than the subsequent months). This line item corresponds to charges for the first month.

Billing Codes

PI_API

The Performance Insights feature provides visibility into the performance of an RDS database. 1 million API requests are included at no cost. Remaining API call requests are charged per API request.

Billing Codes

PI_LTR_FMR:Serverless

The Performance Insights feature provides visibility into the performance of an RDS database. For Aurora Serverless v2 instances 7 days of retention are included at no cost or you can enable it for 1-24 months. Charges are per Aurora capacity unit (ACU) per month (with the first month billed at a higher rate than the subsequent months). This line item corresponds to charges for additional retention months beyond the first month.

Billing Codes

PI_LTR_AMR:Serverless

The Performance Insights feature provides visibility into the performance of an RDS database. For Aurora Serverless v2 instances 7 days of retention are included at no cost or you can enable it for 1-24 months. Charges are per Aurora capacity unit (ACU) per month (with the first month billed at a higher rate than the subsequent months). This line item corresponds to charges for the first month.

Billing Codes

Other

ExtendedSupport:Yr1-Yr2

The Extended Support feature enables the use of a database version after the community end-of-life through AWS providing fixes and support for things like security issues and bugs. The cost is per vCPU per hour for provisioned instances, depending on the version and years since community end-of-life.

Billing Codes

RDS:Data-API-Usage

The Data API feature for Aurora allows you to run SQL queries to access Aurora. Charges are per API request (in 32 KB units). If the number of requests exceeds 1 billion in a month the remaining requests will be charged at a lower rate.

Billing Codes

Serverless

Aurora:ServerlessUsage

The number of Aurora capacity unit (ACU) hours for Aurora Serverless v1. Each ACU corresponds to approximately 2 GB of memory and corresponding CPU and networking resources. Scaling works by setting the minimum and maximum number of ACUs to scale between.

Billing Codes

RDSProxy

RDS:Proxy-ASv2-Usage

The RDS Proxy feature pools and shares database connections to improve application availability and performance. For Aurora Serverless v2, charges are for the number of Aurora capacity unit (ACU) hours of the underlying instance.

Billing Codes

RDS:ProxyUsage

The RDS Proxy feature pools and shares database connections to improve application availability and performance. Charges are per hour per vCPU.

Billing Codes

CPU Credits

CPUCredits

The number of CPU credits used or earned by burstable performance instances. CPU credits are consumed when the instance operates above its baseline CPU performance and earned during periods of low utilization.

Billing Codes

Provisioned Throughput

RDS:GP3-Throughput

The amount of throughput (per MB/s-month) over the 125 MB/s baseline for an RDS Single-AZ General Purpose SSD (gp3) deployment instance.

Billing Codes

RDS:Mirror-GP3-Throughput

The amount of throughput (per MB/s-month) over the 125 MB/s baseline for an RDS Multi-AZ (SQL Server Mirror) General Purpose SSD (gp3) deployment instance.

Billing Codes

RDS:Multi-AZ-GP3-Throughput

The amount of throughput (per MB/s-month) over the 125 MB/s baseline for an RDS Multi-AZ General Purpose SSD (gp3) deployment instance.

Billing Codes

Limitless

Aurora:IO-OptimizedLimitlessACUUsage-LimitlessPreview

The number of Aurora capacity unit (ACU) hours for the Aurora IO-Optimized Limitless Preview (now generally available). Each ACU corresponds to approximately 2 GB of memory and corresponding CPU and networking resources. Scaling works by setting the minimum and maximum number of ACUs to scale between.

Billing Codes

Aurora:IO-OptimizedLimitlessACUUsage-Limitless

The number of Aurora capacity unit (ACU) hours for Aurora IO-Optimized Limitless. Each ACU corresponds to approximately 2 GB of memory and corresponding CPU and networking resources. Scaling works by setting the minimum and maximum number of ACUs to scale between.

Billing Codes

DT-Data Transfer

DataTransfer-AZ-In-Bytes

The amount of data (per GB) transferred in from the same Availability Zone. Data transferred within the same Availability Zone does not incur a fee.

Billing Codes

DataTransfer-AZ-Out-Bytes

The amount of data (per GB) transferred out to the same Availability Zone. Data transferred within the same Availability Zone does not incur a fee.

Billing Codes