Amazon EMR on EC2 improves cluster launch experience with intelligent subnet selection
News
This article announces an improvement to Amazon EMR on EC2 for launching instance fleet clusters with enhanced subnet selection, reducing failures caused by IP address shortages.
Specifically, the article covers:
- Amazon EMR now employs subnet filtering at cluster launch to select a subnet with sufficient IP addresses to launch all instance fleets
- If no subnet can host the entire cluster, EMR prioritizes launching core and primary instance fleets and sends a CloudWatch warning
- If no subnet can host core and primary fleets, EMR fails the cluster launch and sends a critical CloudWatch event
- This improvement is available on EMR 5.12.1 and later releases for instance fleet clusters using allocation strategies
- It is available in all AWS regions where EMR on EC2 is offered, including AWS GovCloud
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
Aug 19
2024
2024
Amazon EMR support prioritized and capacity-optimized-prioritized allocation strategies for EC2 instances
Oct 25
2024
2024
Analyze Amazon EMR on Amazon EC2 cluster usage with Amazon Athena and Amazon QuickSight
Nov 21
2024
2024
Run high-availability long-running clusters with Amazon EMR instance fleets
Feb 21
2024
2024
Deploying an EMR cluster on AWS Outposts to process data from an on-premises database
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.