Sharing Capacity Blocks for ML Across Your AWS Organization
Compute Blog
This article explains how to share EC2 Capacity Blocks for ML across AWS Organization accounts using AWS RAM to optimize GPU utilization and reduce costs.
- Share reserved GPU capacity across teams based on actual demand, not rigid schedules
- Eliminate idle GPU resources and scheduling conflicts between ML teams
- Only standard Capacity Blocks eligible for sharing; UltraServer blocks not supported
- Enable AWS RAM sharing in management account with required IAM permissions
- Create resource shares and associate Capacity Blocks to specific accounts or OUs
- Consumer accounts automatically gain access within same AWS Organization
- Owner pays upfront reservation cost; consumers pay OS licensing and instance charges
- Monitor utilization with CloudWatch alarms and SNS email notifications
- CloudTrail logs track which accounts consume instances and when
Sharing Capacity Blocks for ML improves resource efficiency, reduces over-provisioning, and maximizes ROI on reserved GPU compute across your organization.
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
Feb 5
2026
2026
Amazon EC2 capacity blocks for ML can be shared across multiple accounts
Apr 29
2025
2025
How to use Capacity Blocks for ML with AWS Batch
Jan 11
2024
2024
Enhancing ML workflows with AWS ParallelCluster and Amazon EC2 Capacity Blocks for ML
Sep 18
2025
2025
Announcing Capacity Blocks support for AWS Parallel Computing Service
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.