AmazonNeptune
storage-snapshot
BackupUsage
Backup storage for Neptune is the storage associated with your automated database backups and any customer-initiated database cluster snapshots. Increasing your backup retention period or taking database cluster snapshots increases the backup storage consumed. Backup storage, as well as snapshots you store after your database cluster is deleted, will continue to accrue charges.
GraphSnapshot
system-operation
StorageIOUsage
Storage consumed by your Neptune database is billed by I/Os consumed (in addition to storage) are billed in per million request increments. You pay only for the I/Os your Neptune database consumes and there is no provisioning done in advance.
database-storage
StorageUsage
General storage usage for your Neptune database, billed based on the total gigabytes of storage used for your data and indexes.
OptimizedStorageUsage
Charges for using optimized storage designed to support high-performance Neptune databases, ensuring scalability and durability.
database-instance
InstanceUsage
Standard instance usage for running your Neptune database. This includes the hourly charge for the instance type you've selected.
- USW2-InstanceUsage:db.t3.medium
- InstanceUsage:db.r5.large
- InstanceUsage:db.t3.medium
- InstanceUsage:db.r6g.4xl
- InstanceUsage:db.r5.2xl
- UGW1-InstanceUsage:db.t3.medium
- USW2-InstanceUsage:db.r5.large
- APS2-InstanceUsage:db.t3.medium
- UGW1-InstanceUsage:db.r6g.large
- UGW1-InstanceUsage:db.r6g.xl
- USW2-InstanceUsage:db.r5.xl
- USE2-InstanceUsage:db.r6g.xl
- USE2-InstanceUsage:db.t3.medium
- APN1-InstanceUsage:db.r6g.large
- APN1-InstanceUsage:db.r5.large
- InstanceUsage:db.r6g.2xl
- APS3-InstanceUsage:db.r5.4xl
- APS3-InstanceUsage:db.r5.2xl
- APS3-InstanceUsage:db.r5.xl
- APS3-InstanceUsage:db.r6g.xl
- InstanceUsage:db.r5.xl
- USE2-InstanceUsage:db.r5.large
- USW2-InstanceUsage:db.r5.2xl
- USW2-InstanceUsage:db.r5.4xl
- EUC1-InstanceUsage:db.t3.medium
- EUW2-InstanceUsage:db.t3.medium
- InstanceUsage:db.t4g.medium
- USE2-InstanceUsage:db.r6g.large
- InstanceUsage:db.r6g.xl
- USW1-InstanceUsage:db.r6g.xl
- EU-InstanceUsage:db.r5.large
- EU-InstanceUsage:db.t3.medium
- InstanceUsage:db.r6g.8xl
InstanceUsageIOOptimized
This billing code represents the cost for using IO-optimized Neptune database instances, designed for high-throughput and low-latency graph database workloads.
- InstanceUsageIOOptimized:db.r6g.xl
- InstanceUsageIOOptimized:db.t3.medium
- USE2-InstanceUsageIOOptimized:db.t3.medium
- EU-InstanceUsageIOOptimized:db.r6g.large
- EU-InstanceUsageIOOptimized:db.r6g.2xl
- EU-InstanceUsageIOOptimized:db.t3.medium
- InstanceUsageIOOptimized:db.r6g.4xl
- EU-InstanceUsageIOOptimized:db.r5.large
data-transfer
AWS-Out-Bytes
The amount of data (in bytes) 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.
serverless
ServerlessUsage
Usage of Neptune's serverless mode, allowing you to pay only for the actual database resources consumed, with automatic scaling to handle workload changes. Neptune Serverless measures database capacity in Neptune Capacity Units (NCUs) billed per second. 1 NCU has approximately two GiB of memory with corresponding CPU and networking, similar to what is used in Neptune instances.
ServerlessIOOptimizedUsage
Charges for IO-optimized operations when using Neptune's serverless offering, which adjusts automatically based on your database's workload.
neptune-memory-optimized-graph
MemoryOptimizedGraphUsage
Usage of memory-optimized instances for Neptune, ideal for graph workloads requiring large memory footprints for faster processing and query results.
cpu-credits
CPUCredits
CPU Credits are consumed when Neptune burstable instance types (T4g and T3 instance types) exceed their baseline performance. These credits ensure that your database can handle occasional spikes in demand without additional configuration.