Architecting for IOPS and throughput performance on AWS Outposts racks
Compute Blog
This article explains how to configure EC2 instances and EBS storage on AWS Outposts racks to meet IOPS and throughput requirements for on-premises workloads.
- EBS-optimized instances (c5, m5, r5, g4dn, c7i, m7i, r7i, c8i, m8i, r8i) provide dedicated bandwidth to minimize storage I/O contention
- gp2 volumes deliver 3 IOPS per GiB up to 16,000 IOPS; gp3 volumes support up to 16,000 IOPS and 1,000 MiB/s throughput on second-generation racks
- Calculate required IOPS by matching instance maximum IOPS with combined attached volume IOPS; gp3 requires significantly less storage than gp2 for same performance
- Monitor EBS performance using CloudWatch metrics (VolumeReadOps, VolumeWriteOps, VolumeTotalReadTime, VolumeTotalWriteTime) and set alarms at 70% threshold
- RDS databases on Outposts require careful sizing of instance type, EBS volume type, and storage size to avoid performance bottlenecks
Proper sizing of EC2 instances and EBS storage prevents performance bottlenecks and ensures optimal IOPS and throughput delivery for database and application workloads on Outposts.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Mar 4
2025
2025
Architecting for seamless on-premises connectivity with AWS Outposts servers
Mar 3
2025
2025
Announcing AWS Outposts racks for high throughput, network-intensive workloads (Preview)
Apr 19
2024
2024
Architecting for Disaster Recovery on AWS Outposts Racks with AWS Elastic Disaster Recovery
Aug 20
2025
2025
Multi-rack and multiple logical AWS Outposts architecture considerations for resiliency
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.