Instructor: Eng. Essa Abu Sharif | Moderator: Ahmed
0. Session Agenda
Continuing EBS (encryption, snapshots, AMIs, RAID), a quick note on AWS Batch, then a deep dive into Elastic Load Balancing (target groups, listeners, health checks, HA subnet design, SSL/TLS, client IP preservation, sticky sessions, path/host-based routing) with an extended design assignment.
1. EBS — Modify, Encryption, and General Recap
1.1 Modifying a Live Volume
- EBS volumes can be modified while the instance is running — resize (grow only, never shrink), change volume type, or change performance tier — no need to detach/stop.
- Cannot shrink a volume — only increase size.
- Best practice reminder: take a Snapshot before modifying, in case something goes wrong (safety net, not a strict requirement).
1.2 EBS Encryption — Where It Happens
Encryption/decryption for an EBS volume happens on the EC2 host (the instance side), not on the EBS storage side itself — data is encrypted before it leaves the host, travels encrypted over the network, and is stored encrypted on the EBS volume.
- This means encryption effectively covers the entire path: from the EC2 instance, across the network, to the EBS volume at rest — a full "in transit + at rest" guarantee for that specific hop.
- Uses a CMK (Customer Master Key) from KMS — can be:
- AWS-Managed Key (
aws/ebs default) — simplest, no control over rotation/permissions, AWS manages it fully.
- Customer-Managed Key — full control: rotation schedule, access policy (who can/cannot use it).
- Symmetric vs Asymmetric: EBS/KMS currently primarily uses Symmetric keys (better performance, supports rotation) — Asymmetric key support in KMS is newer (~1-1.5 years old at time of recording) and not the default recommendation unless specifically required; check the AWS KMS documentation link for current details, as this can evolve.
2. EBS Snapshots
2.1 What a Snapshot Is
A Snapshot = a point-in-time backup of an EBS volume, stored in S3 — but you cannot browse it directly in your own S3 console; it's managed entirely through the EC2/EBS console interface.
- Purpose: protect against data loss, and serve as the basis for creating new volumes (in the same or a different AZ/region).
2.2 Snapshot Scheduling — Two Methods