diff options
| author | JJ <nicetry@noemail.com> | 2025-03-19 14:56:26 +0000 |
|---|---|---|
| committer | JJ <nicetry@noemail.com> | 2025-03-19 14:56:26 +0000 |
| commit | 16f52b7bef745097f7076dde76715db378b54343 (patch) | |
| tree | cfcacda8adced2059dcc120d2bc2446d3c4f960a /content/notes/aws-solutions-architect/7.ec2-placement-groups.md | |
first commit
Diffstat (limited to 'content/notes/aws-solutions-architect/7.ec2-placement-groups.md')
| -rw-r--r-- | content/notes/aws-solutions-architect/7.ec2-placement-groups.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/content/notes/aws-solutions-architect/7.ec2-placement-groups.md b/content/notes/aws-solutions-architect/7.ec2-placement-groups.md new file mode 100644 index 0000000..85f4f55 --- /dev/null +++ b/content/notes/aws-solutions-architect/7.ec2-placement-groups.md @@ -0,0 +1,16 @@ +--- +title: 07 - ec2 placement-groups +course: ["aws solutions architect"] +--- + +# EC2 Placement Groups + +Placement groups allow you to define where your EC2 instances are deployed on AWS infrastructure. + +A placement group is either: + +1. _A cluster_: puts your instances in a low latency group in the same AZ. This helps with networking as instances are close to one another. Drawback is if the AZ fails, they all fail. **use case**: Good for big data jobs, apps that need low latency between instances. +2. _Spread_: Think of this as opposite to clusters. Each instance is on different hardware across different AZs. This means reduced failure risk. Limited to 7 AZ per placement group. **Use case**: maximum high availability. +3. _Partition_: spreads instances across different partitions within an AZ. Each partition represents a rack in AWS. Instances are distributed across different hardware racks and AZs in same region. **use cases**: Big data application, which are petition aware. + + |