This page provides a live view of all AWS infrastructure components supporting the ECommerce Web App production environment. It is intended as the first stop during incident response: rather than navigating the AWS console service by service, this page surfaces the operational state of every component in a single view.

Data is retrieved directly from AWS at page load. Each table below reflects the current state of the environment at the time you opened this page. Refresh the page to get an updated view.

All inbound traffic enters through CloudFront before reaching any application infrastructure. The WAF rules attached to the CloudFront distributions and the application load balancer provide protection against common web exploits, bot traffic, and rate-based attacks.

During an incident: if customers cannot reach the site at all, check the CloudFront distribution status and whether the associated WAF ACL is present. A distribution with status: InProgress indicates a recent deployment is still propagating globally.

Customer requests that pass through CloudFront and WAF are routed to the application load balancer, which distributes traffic across EC2 instances in the auto-scaling group. The EC2 instances run both the web frontend and the application API layer.

During an incident: check that the load balancer state is active and that EC2 instances are in the running state. If fewer than 3 instances are running, the auto-scaling group may be failing to launch replacements, which warrants investigation of the launch template and instance health checks.

Lambda functions handle asynchronous and event-driven workloads: order confirmation emails, inventory level updates, product image resizing, search index refresh, and customer authentication token management. These functions are invoked by SQS, DynamoDB Streams, and scheduled EventBridge rules.

During an incident: if orders are being placed but confirmation emails are not being sent, or if the product catalogue appears stale, the relevant Lambda function may have a deployment error or a failed execution. Check that the expected functions are present and note the last_modified date — a very recent deployment may coincide with the start of the incident.

Application storage spans two AWS services. S3 buckets hold static web assets, product images, customer order exports, and application logs. EBS volumes are attached to EC2 instances and provide the operating system and application storage for each server.

During an incident: if the site is loading without images or static assets, check that the S3 buckets are present and the CloudFront origin points to the correct bucket. If an EC2 instance has entered a degraded state, check that its EBS volume is in-use and not available (detached).

DynamoDB provides the primary data store for customer-facing application data. Three tables are in use: cart (active shopping carts), sessions (authenticated user sessions), and orders (order records). All three must be in ACTIVE status for the application to function correctly.

During an incident: a DynamoDB table in any state other than ACTIVE will cause the relevant part of the application to fail. A table in UPDATING state is undergoing a provisioned capacity change and should return to ACTIVE shortly. A table in CREATING or DELETING state warrants immediate investigation.

The network layer is typically the most stable part of the infrastructure. The components shown here — VPC, subnets, internet gateway, and NAT gateways — rarely change during normal operations. However, they are relevant during network-level incidents: if EC2 instances in the private subnets cannot reach external services (e.g. payment APIs, email providers), the most likely cause is a NAT gateway in a degraded state.

During an incident: NAT gateway issues are a common cause of “outbound connectivity from private resources is broken” incidents. Both gateways must be available. A NAT gateway in deleting or failed state should be treated as a P1 incident.

If you have identified a degraded or failed component, use the contact matrix below to escalate to the appropriate team. Severity is defined as follows: