Please enable JavaScript.
Coggle requires JavaScript to display documents.
EC2: Associate - Coggle Diagram
EC2: Associate
IP
Public
Unique globally
Easy geo-location
Private
Unique across network
NAT + Internet Gateway required to access WWW
Only certain ranges of IPs can be used
Elastic IP
Fixed IP for EC2 instance
Public IPv4 address
Can only attach to 1 instance at a time
Can remap in case of instance failure
Max 5 per account
Avoid if possible
Can use random public IP and map DNS to it
Can us Load Balancer
Placement groups
Control instance placement
Strategies
Cluster
Single AZ
Pros
Low latency network
Cons
Rack failure = all instances fail
Use cases
Big data jobs
Low latency high bandwidth
Spread
Spread across AZs
Pros
Reduce simultaneous failure risk
Instances on different physical hardware
Cons
Limited 7 instances per AZ per group
Use case
Critical applications (failures should be isolated)
Partition
Partition = set of instances on rack
Up to 7 partitions per AZ
Can span multiple AZs in one region
Partition failures are isolated
Instances can read partition metadata
Use cases
HDFS
HBase
Cassandra
Kafka
Elastic Network Interface (ENI)
Virtual network card
Attributes
1 Primary private IPv4
1+ secondary IPv4
1 Elastic IPv4 per private IPv4
1 Public IPv4
1+ Security groups
1 MAC address
Can attach and detach to EC2 for failover
Bound to AZ
Hibernate
In memory state preserved
Written to root EBS
Faster boot time
Root EBS must be encrypted
Use cases
Long running processes
Saving RAM state
Services that take long to initialize
Supported families: C3, C4, C5, I3, M3, M4, R3, R4, T2, T3
RAM size must be < 150GB
Bare metal instances not supported
AMI: Amazon Linux 2, Ubuntu, RHEL, CentOS, Windows
Root volume cannot be instance store
Available for on-demand, reserved, spot
Cannot be hibernated for > 60 days