'fault-injection' 검색 결과

GameDay シナリオを AWS FIS 実験テンプレート (CDK) として実装する。「シナリオを FIS にして」「実験テンプレートを作って」「障害注入を実装して」「fault-injection を書いて/直して」など、FIS 実験の実装・修正・レビューの全てで必ず使う。FIS アクションの選定、停止条件 (CloudWatch アラーム)、実験ロールの最小権限 IAM、爆発半径の制御 (selectionMode)、実験レポート設定、ECS タスクアクションの SSM サイドカー前提条件など、検証済みの判断基準とコード例を提供する。lib/constructs/fault-injection.ts を編集するときは内容にかかわらず該当する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test how agent workflows recover from repeatable simulated failures, including tool timeouts, worker restarts, and lost memory. Produces a fault matrix, event timeline, and verdict showing whether state, safety boundaries, and retry budgets were preserved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test recovery from MCP or tool timeouts
• Verify checkpoint recovery after a worker restart
• Check outcomes when one parallel branch fails

Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan controlled failure experiments to uncover system weaknesses. Define normal operating metrics, estimate affected users and reliability risk, set abort and recovery conditions, and turn experiment results into a structured review with follow-up actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing a controlled failure experiment
• Estimating affected users and reliability risk
• Planning a team failure response exercise

Plans, builds, runs, and analyzes fault injection experiments with AWS Fault Injection Service (AWS FIS) to validate application resilience through chaos engineering. Covers experiment templates (actions, targets, stop conditions), the FIS actions catalog and action selection, the scenario library (AZ power interruption, cross-Region connectivity, EC2/EKS/EBS stress), experiment lifecycle and monitoring, logging and reports, multi-account experiments, the experiment IAM role, and blast-radius safety. Applies when a user mentions AWS FIS or fault injection, asks what experiment to run for a failure mode (AZ, Region, API errors/throttling, instance/pod/DB/cache failure, latency, packet loss), wants to author an experiment template or CLI/CloudFormation, or needs to safely run chaos experiments in pre-production or production. For the broader resilience program across Resilience Hub and ARC, see aws-resilience-lifecycle; for ARC routing controls and zonal shift, see recovery-controller-setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and execute chaos engineering experiments using Litmus or Chaos Mesh. Test system resilience through controlled fault injection, validate hypothesis-driven tests, and improve failure recovery. Use before major product launches, after architecture changes to validate resilience, during GameDays or disaster recovery drills, to validate assumptions about failure modes, or as part of an SRE maturity program.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en chaos engineering (Gremlin, Litmus, fault injection, game days, fiabilité)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.