Lesson 073 · AWS Learning Path

AWS 073: Attach, format, mount, persist, snapshot, and restore an EBS volume

Anil Jalela · Published Sep 6, 2025 · 7 min read

The problem

A team uses Attach, format, mount, persist, snapshot, and restore an EBS volume as a label or Console setting without proving the identity, scope, behavior, failure boundary, cost, or operational result. The configuration appears complete but the real requirement remains untested.

Final outcome

The learner will inspect, explain, test, and document Attach, format, mount, persist, snapshot, and restore an EBS volume. The submission must connect the Console and CLI view to the same AWS control, state what the evidence proves, diagnose one likely failure, and make a requirement-based architecture decision.

Learning outcomes

You will be able to:

1. explain lab volume;
2. explain attachment;
3. explain filesystem safety;
4. explain persistence;
5. explain snapshot and restore;

1. distinguish successful configuration from successful workload behavior;
2. preserve redacted evidence and complete the stated cleanup or retention decision.

Mental model

requirement
   -> identity and permission
   -> account, Region, and resource scope
   -> configuration or request
   -> observable state
   -> workload result
   -> failure evidence
   -> cleanup or controlled retention

Never begin with a create button or a copied command. Start with the result that must be proven and the boundary that must remain protected.

Core facts

How to reason about it

This lab is destructive if the wrong device is selected. Match EC2 volume ID, attachment, Linux device serial, size, and absence of a filesystem before formatting. Stop on any mismatch.

Snapshot completion and restored-volume attachment are control-plane states. File visibility and application consistency are data-plane evidence. Record both.

Use the following decision table as a starting point, then change the answer when the scenario changes.

Prerequisites, permissions, Region, and cost

Run this lesson as the approved non-root course identity. Begin with aws sts get-caller-identity, confirm the private account record, and set the fixed project Region before any regional query. IAM resources are global within an account, while STS endpoints and the services reached by an identity can be regional.

Use only the read or change actions required for this lesson. An AccessDenied result is evidence to analyse, not permission to switch to root or attach AdministratorAccess. Record the action, resource, principal type, request context, and smallest justified correction.

The listed cost tier is T1 - free or near-free with immediate cleanup. Free Tier eligibility and credits are account-specific. Before a mutating lab, identify every resource that can charge, estimate its duration, start a timer, and write the reverse cleanup order. A budget reports cost after billing data arrives and is not a real-time stop control.

AWS Management Console method

1. Open EC2, Volumes, create nw-p04-data-1 as 4 GiB encrypted gp3 in the instance AZ, tag it, and attach it.
2. Use Session Manager to identify, format, mount, write, and persist the filesystem, then create a tagged snapshot.
3. Restore nw-p04-data-restore from the completed snapshot, attach and verify it, then perform reverse cleanup.

For every step record the service page, selected account and Region, exact object, visible state, and why that state matters. A Console label or green status is not enough unless it is tied to the final workload outcome.

AWS CLI or API evidence

Match control-plane IDs with Linux block-device and filesystem evidence.

lsblk -o NAME,SERIAL,SIZE,FSTYPE,MOUNTPOINTS
findmnt /mnt/p04-data
sudo blkid
cat /mnt/p04-data/recovery-marker.txt

The serial, filesystem, mount, UUID, and marker must identify the intended original or restored volume. Redact resource IDs in shared evidence.

Before running the command, replace every placeholder, explain each option, and decide whether the operation is read-only or mutating. Capture the exit code immediately. Redact account IDs, ARNs, public addresses, request identifiers, and personal data before sharing.

The CLI and Console are clients of AWS APIs. Matching state across them increases confidence, but neither substitutes for data-plane or application verification.

Practical work

Retain nw-p04-web-1 from AWS 072 through AWS 079, but stop it between study sessions. Record EC2 and public-IPv4 cost only while running and root-volume cost while retained. Set a 90-minute running-resource timer. Prove same-AZ placement, map the data-volume ID to the Linux device, create an XFS filesystem only on the verified empty device, mount it at /mnt/p04-data, persist by UUID, snapshot a recovery marker, restore and verify a second copy, then delete every temporary data volume and snapshot. Stop the instance after evidence collection unless AWS 074 starts immediately. Do not terminate the project instance until AWS 080.

The evidence package must include:

• non-root principal type, account verified privately, and Region;
• exact intended and observed state;
• one Console observation and the matching CLI or API result;
• one successful result and one denied, failed, or counterexample result;
• what each result does not prove;
• cost state and elapsed lab time;
• cleanup evidence or a named retained-state owner and next lesson.

Verification standard

Use three levels of proof:

1. Control plane: the object or policy exists with the intended configuration.
2. Data plane or behavior: the request, packet, session, storage path, or application does what the requirement states.
3. Operations: monitoring, failure diagnosis, cost, ownership, and cleanup are known.

A control-plane response can precede final readiness. Use waiters or state polling where supported, then test the actual behavior. If a request times out, do not assume it failed. Inspect state and use documented idempotency before retrying a mutation.

Troubleshooting method

Keep the original symptom and timestamp. State one hypothesis, make one reversible change, repeat the original test, and record rollback. Never open a management port to the world, expose credentials, disable TLS verification, format an unknown disk, or add broad permissions as a generic fix.

Architecture and certification decisions

Professional-level questions provide competing valid features. Identify the requirement that decides between them: human or workload identity, same-account or cross-account access, regional or zonal scope, stateful or stateless filtering, durable or ephemeral data, latency, RTO/RPO, cost, or operational ownership.

Explain why the selected option fits and why each plausible alternative fails one stated requirement. Do not rely on feature memorization or reproduce protected certification questions.

Knowledge check

1. Can an EBS volume attach across AZs?

Expected direction: No. Restore or create a volume in the target AZ.

1. Why inspect before mkfs?

Expected direction: Formatting destroys existing filesystem metadata.

1. Why use UUID in fstab?

Expected direction: Device names can change.

1. What charges after instance stop?

Expected direction: Retained EBS volumes and snapshots.

Cost, cleanup, and retained state

Retain only the state explicitly required by the next P04 lesson and record it in the private resource ledger.

Cleanup evidence includes the final state query, not only a successful delete response. Search related resources, other Regions used by the lab, retained storage, public IPv4 addresses, logging destinations, and service-managed dependencies. Schedule a later billing review because cost data can lag.

Completion gate

Pass when the practical artifact explains the real problem, matches Console and CLI evidence, answers every knowledge check, diagnoses one failure without broadening access, records cost, and proves cleanup or approved retention. The learner must defend one decision orally and name the requirement that would change it.

Official sources

• Attach an EBS volume
• Make an EBS volume available
• Restore a volume from a snapshot