Dockfield DRaaS の AWS 公開復旧デモ

稼働中の AWS から。
検証済みの DR へ。

録画されたインターフェースを5分で案内します。ステータス欄、タブ、隔離タイムライン、保留中の削除、検証経路、昇格ゲート、復旧した ECS アプリケーションを追ってください。各画面が表示されるたびにナレーションで説明します。

AWSの操作を収録したデモ5分ナレーション付き12セクションDRaaS のナレーションと字幕は英語です

機密性の高い AWS アカウント識別子はぼかしています。長い待機は短縮し、各シーンは35秒以内です。

復旧戦略と図を確認するDR-as-Code デモを11言語で見る

Press play for the five-minute Dockfield DRaaS walkthrough. English captions match the DRaaS narration.

Download the HD demo video

復旧ライフサイクルを確認する

段階を選択すると、その位置から再生します。

  1. ステージ 0100:15 No initial IaC baseline requiredThe 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.
  2. ステージ 0200:35 Recovery overview and status fieldsHere 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.
  3. ステージ 0301:00 Tier 0 artifact trust tabThe 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.
  4. ステージ 0401:25 Visible quarantine timelineThe 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.
  5. STAGE 0501:52 Destructive change held in DRThe 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.
  6. STAGE 0602:18 Validation path and locked failover gateThe 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.
  7. STAGE 0702:50 Promotion approved displayThe 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.
  8. STAGE 0803:15 ARC traffic control readinessThe 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.
  9. STAGE 0903:40 Recovery execution componentsThe 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.
  10. STAGE 1004:08 Recovered application fieldsHere 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.

DRAAS · プライマリ

継続的な復旧保証

ブループリントの継続更新、信頼性チェック、隔離、検証、復旧演習、証跡、制御された昇格。

DRaaS を見る
DR-AS-CODE · エンジニアリング

プロジェクトの引き継ぎを希望しますか?

従来の DR-as-Code デモは、ナレーション、字幕、チャプターを含む11言語で引き続き利用できます。

DR-as-Code の多言語デモを見る
解説を読む
  1. 00:00 · Live AWS to validated recovery

    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.

  2. 00:15 · No initial IaC baseline required

    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.

  3. 00:35 · Recovery overview and status fields

    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.

  4. 01:00 · Tier 0 artifact trust tab

    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.

  5. 01:25 · Visible quarantine timeline

    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.

  6. 01:52 · Destructive change held in DR

    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.

  7. 02:18 · Validation path and locked failover gate

    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.

  8. 02:50 · Promotion approved display

    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.

  9. 03:15 · ARC traffic control readiness

    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.

  10. 03:40 · Recovery execution components

    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.

  11. 04:08 · Recovered application fields

    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.

  12. 04:38 · DRaaS first and DR-as-Code available

    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.

初回無料相談会

AWS 環境で継続的な復旧保証を実現すると、どのようになるでしょうか。

ワークロード、復旧目標、重点を絞った DRaaS 導入手順について、30分間の無料相談でお話しください。