Lesson 053 · AWS Learning Path

AWS 053: Project scenario, final architecture, exact sample values, permissions, and cost boundary

Anil Jalela · Published Aug 17, 2025 · 7 min read

The problem

A team uses Project scenario, final architecture, exact sample values, permissions, and cost boundary 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 Project scenario, final architecture, exact sample values, permissions, and cost boundary. 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 project objective;
2. explain fixed region;
3. explain address plan;
4. explain access model;
5. explain cost boundary;

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

The final architecture is a learning system, not a production reference. It deliberately uses one short-lived public-subnet instance for inexpensive outbound access while keeping inbound rules empty. Production would add private placement, managed ingress, multi-AZ capacity, patching, observability, backup, and deployment controls.

The learner maintains a resource ledger from the first VPC action. Names help humans, IDs prove exact dependencies, and tags connect resources to the project and cleanup owner.

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 T0 - no resource creation. 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 Billing, Budgets and confirm the course alert before architecture approval.
2. Open VPC and EC2 dashboards in ap-south-1 and confirm the starting inventory.
3. Open Service Quotas for EC2 and VPC and record relevant applied values without requesting increases.

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

Run the identity and Region preflight before approving the project.

aws sts get-caller-identity --region ap-south-1 --query Arn --output text
aws ec2 describe-vpcs --region ap-south-1 --query 'Vpcs[].{Id:VpcId,Name:Tags[?Key==`Name`]|[0].Value}' --output table

The caller must be non-root and the inventory must not contain a conflicting nw-p04 project. Redact the account portion of the ARN.

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

Create p04-plan.md with the final diagram, exact name and CIDR table, allowed services, prohibited cost items, IAM permissions, resource ledger template, verification points, failure injections, retain/delete decisions, and a signed review gate. No resource may be created until the instructor approves this artifact.

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. Why no NAT gateway?

Expected direction: Its hourly and processing cost is unnecessary for the selected short public-subnet lab path.

1. Why no inbound SSH?

Expected direction: Session Manager is the approved administration path.

1. What is the project VPC CIDR?

Expected direction: 10.42.0.0/16.

1. What makes cleanup reliable?

Expected direction: A dependency ledger, exact IDs, and reverse-order verification.

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

• AWS Well-Architected Framework
• AWS Pricing Calculator
• Amazon VPC concepts