AWS

Practice choosing the right AWS service family by job: traffic, compute, data, access, signals, operations, cost, and recovery.

Practice tracing a failing orders API request through DNS, an ALB, subnets, routes, security groups, target health, and app evidence.

Practice placing the orders API in a VPC, reading subnet and route-table evidence, and choosing public, private, outbound, and endpoint paths.

Practice keeping application resources private while still giving them the outbound and AWS service paths they need.

Practice reading routed packet paths, narrow security group references, subnet NACL guardrails, and evidence-driven AWS network diagnostics.

Practice tracing an ALB request path, reading target health evidence, and choosing safe checks for orders API failures.

Practice connecting Route 53 records, ALB entry points, ACM certificates, and HTTPS listener evidence for an orders API.

Practice choosing EC2, ECS on Fargate, and Lambda by reading workload shape, traffic paths, scaling behavior, and failure evidence for devpolaris-orders-api.

Practice operating devpolaris-orders-api on EC2 by reading AMI, instance type, subnet, security group, startup, systemd, log, disk, and patching evidence.

Practice turning a container image into a steady ECS service, then diagnosing Fargate task definitions, services, networking, roles, ports, and logs for devpolaris-orders-api.

Practice choosing Lambda for bounded event work, reading event and invocation evidence, and deciding when a service is simpler for devpolaris-orders-api.

Practice choosing the AWS compute shape that matches the workload, operating model, traffic path, and failure evidence for DevPolaris services.

Practice matching object, relational, key-value, attached-storage, and recovery-copy shapes to the right AWS storage service.

Practice bucket, key, object, access, versioning, lifecycle, and missing object diagnosis for DevPolaris file data.

Practice relational data fit, ECS to RDS connectivity, schema operations, backups, and connection failure diagnosis.

Practice choosing DynamoDB for key-based access, designing keys, using conditional writes, and diagnosing table failures.

Practice choosing block or shared file storage, reading mounted volume evidence, and diagnosing compute-attached storage bugs.

Practice choosing S3, RDS, DynamoDB, EBS, or EFS from data shape, ownership, access, and recovery requirements.

Practice recovery maps, backup choices, retention windows, safe deletion review, and data recovery diagnosis.

Practice choosing logs, metrics, traces, alarms, and audit evidence when production behavior is hidden behind AWS services.

Practice reading log groups, streams, structured app logs, workload log paths, searches, and first useful errors.

Practice reading AWS service metrics, dashboards, and alarms as operating signals for DevPolaris.

Practice using correlation IDs, trace context, spans, and AWS tracing tools to follow slow or failed checkout requests across AWS services.

Practice reading releases as runtime contracts, artifacts, evidence, health, capacity, and rollback targets.

Practice task definition revisions, ECS service updates, target health, completed deployment evidence, and rollback targets.

Practice runtime config contracts, ECS value delivery, secret safety, config validation, and safe diagnosis.

Practice capacity decisions, queues, workers, schedules, concurrency, and controls that buy time during AWS incidents.

Practice pairing AWS cost shapes with resilience tradeoffs before changing resources.

Practice using tags, Cost Explorer, budgets, ownership, and spend-jump diagnosis.

Practice tuning AWS compute, database, storage, logs, queues, workers, and autoscaling from evidence without cutting needed resilience.

Practice joining AWS runtime, load balancer, ECS, IAM, logs, alarms, and rollback evidence during one production incident.

Practice RTO, RPO, recovery strategies, backups, restores, bad-write recovery, failover thinking, and recovery drills.