Van een actieve AWS-omgeving.
Naar gevalideerd herstel na een ramp.

Welcome to Dockfield DRaaS. The opening screen presents the journey from live AWS to validated recovery. The six boxes show the sequence: Discover, Blueprint, Quarantine, Validate, Recover, and Promote.

The next screen says: no initial infrastructure as code baseline required. Read the flow along the bottom. Production is on the left, in us-east-1. Read-only discovery and the recovery blueprint sit in the middle. The destination on the right is DR-1, in eu-west-2.

Here is the Dockfield DRaaS interface. Across the top, the recovery record is DF-DEMO-001. Its state reads Static Scan Pending. Traffic promotion is Locked, and ARC routing is Off. Below the tabs, the Overview identifies the production source and DR-1 target. The yellow banner explains that recovery is still gated until promotion approval.

The Tier Zero Trust tab is now selected. Its blue notice says no trust result is attached yet. Below it, the example command shows how to run artifact trust and attach the result to this recovery record. The trust signals name Terraform validation, Checkov, and Trivy. The note explicitly says Trivy is not proof of malware absence.

The Quarantine tab displays a visible timeline. At the top, the record now reads Quarantined. Traffic promotion remains Locked and ARC remains Off. The red banner confirms that promotion is disabled. The timeline lists the manual demo quarantine, the earlier Static Scan Pending entry, and the initial Discovered entry, each with a timestamp and an actor.

The Destructive Changes tab shows a Delete Security Group event. Read the three fields: source event, DR action Held, and ARC Off. The detail below says the production security group was deleted, while the DR security group was retained. The action is waiting for explicit approval. The Technical details panel holds the event information for review.

The Validation Path tab outlines Tier One infrastructure and security checks, Tier Two smoke tests, and Tier Three application and data checks. This view describes the required path; it does not display completed test results. The recording then opens ARC Traffic Control. Its failover gate is still Locked and current promotion is Not eligible. The yellow message says the ARC routing controls have not yet been configured.

The top status fields now change. The recovery state becomes Promotion Approved, and traffic promotion and ARC readiness both read Eligible. The green banner confirms the promotion gate has passed. Notice that the separate destructive-change event still remains Held below. Recovery promotion and approval of that deletion are distinct decisions in this interface.

The ARC Traffic Control tab now shows the lifecycle as Promotion Approved, the failover gate as Open, and current promotion as DR eligible. The yellow configuration notice remains visible. This recording shows the approval and readiness display, rather than a live ARC routing switch. The page explains that live changes stay behind the explicitly approved backend path.

The recovery execution screen says: build the DR environment only after approval. Its five boxes identify the approved blueprint, DR account, eu-west-2, ECS Fargate, and health check. The text lists the components for this recorded slice: VPC, public subnets, Internet Gateway, Application Load Balancer, CloudWatch Logs, and ECS Fargate.

Here is the recovered application page. Its cards identify Amazon ECS as the runtime, DR-1 as the environment, and eu-west-2 as the Region. The image release is version one. Recovery mode reads Continuous Assurance. The green badge says Application Healthy. The AWS account field is blurred for this public recording. These visible labels identify the environment serving the recovered page.

The closing screen says: DRaaS first, DR-as-Code available. The boxes recap read-only discovery, trust and quarantine, three-tier validation, recovery, and ARC-ready promotion. Visit the recovery strategies page for diagrams explaining individual AWS services, or watch the separate DR-as-Code demo in your preferred language.