AWS SysOps Administrator (SOA) study notes


Hello, world. Penned down some keywords after passing my recent AWS SOA exam, and then expanded on ’em below. Perhaps you’ll find ’em useful then.


RAID 0 (striped) vs. 1 (mirrored); i.e., the lower the number, the higher the risk, see

Just like EC2 instances, EBS volumes reside in a specific AZ of a Region; i.e., they can only be attached to a running instances within the same AZ. To switch AZs, use snapshots, see


AMIs can be referred to as being backed by EBS, or ephemeral/instance store. Ephemeral/instance AMIs are stored in S3; i.e., terminating an EC2 instance running the S3-based AMI means that data in the root volume is gone forever, see

EBS optimized; i.e., minimizing contention between EBS I/O and other traffic from your EC2 instance, see

Cluster-type placement groups: low-latency grouping (of EC2 instances) within a single AZ, see


Automated Backups allow users to restore to data within about 5 minutes of the current time, see


TA, as its name suggests, allows users to accelerate file transfers to S3, for when users are underutilizing available Internet bandwidth at upload time, see


Tenancy is typically default (i.e., shared) tenancy. Users cannot change from default to dedicated/host, and vice-versa, see

IPv4 CIDR blocks can range from large (/16 netmask, 65k addresses) to small (/28 netmask, 16 addresses), see

Direct Connect, use private (virtual interface) to connect to your VPC, public for services that aren’t in a VPC (e.g., Glacier), see

Within VPCs, there is a “local” route allowing communication between subnets using private IP addresses only, see <,>.


Active Directory and AWS, see <,>.

Windows EC2 instances can be configured using EC2Config (2.2.10+) to export data to CloudWatch, see