Use small, explainable projects to distinguish study, guided labs, and independent delivery.
Publish a small non-sensitive site using S3 and CloudFront in a practice account.
Architecture, HTTPS setup, access decisions, cache behavior, deployment steps, and cost/cleanup notes.
Why should the origin not be publicly writable? How would you diagnose stale content?
Deploy a minimal app, restrict access, and collect logs and health signals.
Network rules, least-privilege role, CloudWatch observations, one controlled failure, and a recovery record.
How do you distinguish DNS, network, application, and permission failures?
Recreate a small lab with infrastructure as code and exercise a restore procedure.
Versioned configuration, test output, RTO/RPO assumptions, secrets handling, and resource teardown.
What did you restore and actually measure? What remains untested?
Program-specific details are transcribed from a user-supplied Batch 3 image reviewed on 23 October 2026. No official current intake announcement or application link was independently verified. This site is not affiliated with or endorsed by the program organizers.
AWS describes this as foundational, high-level cloud knowledge, not proof of production engineering.
AWS recommends at least one year of hands-on design experience. It is a possible later direction, not an automatic promotion.
N3 concerns everyday Japanese comprehension to a certain degree. An N3 target is not an earned certificate or a guarantee of workplace fluency.