Articles → AWS → Placement Groups In AWS
Placement Groups In AWS
Purpose
Different Strategies Of The Placement Group
- Cluster → In this strategy, the EC2 instances are placed close to each other in the same availability zone
- Partition → In this strategy, the EC2 instances are grouped in a segment called Partition. Each partition does not share the same underlying hardware
- Spread → In this strategy, the small group of EC2 instances is placed on distinct hardware
| Clustered | Spread | Partition |
---|
What | Instances are placed into a low-latency group within a single AZ | Instances are spread across underlying hardware | Instances are grouped into logical segments called partitions which use distinct hardware |
When | Need low network latency and/or high network throughput | Reduce the risk of simultaneous instance failure if underlying hardware fails | Need control and visibility into instance placement |
Pros | Get the most out of enhanced networking Instances | Can span multiple AZs | Reduces the likelihood of correlated failures for large workloads. |
Cons | Finite capacity: recommend launching all you might need upfront | Maximum of 7 instances running per group, per AZ | Partition placement groups are not supported by Dedicated Hosts |
How To Create The Placement Group?
Click to Enlarge
Click to Enlarge
Field | Value |
---|
Name | < Custom placement group name> |
Placement strategy | Cluster | Spread | Partition |
Number of partitions | < Number of partitions > |
Spread level | Host (Outposts only) | Rack (No restrictions)This field is visible only if “Spread” is selected in “Placement strategy”. |
Click to Enlarge
Click to Enlarge
Click to Enlarge
Click to Enlarge
How To Assign A Placement Group To An EC2 Instance?
Click to Enlarge