Announcing Multi-Account Experiments for AWS Fault Injection Service
Today, AWS announces the support of multi-account experiments for AWS Fault Injection Service (FIS). This feature allows you to set up and run real-world failure scenarios on an application which spans multiple AWS accounts using a single FIS experiment. You can centrally configure, monitor, and review an experiment that targets resources in multiple accounts.
Today, AWS announces the support of multi-account experiments for AWS Fault Injection Service (FIS). This feature allows you to set up and run real-world failure scenarios on an application which spans multiple AWS accounts using a single FIS experiment. You can centrally configure, monitor, and review an experiment that targets resources in multiple accounts.
With this launch, you can create and run an FIS experiment from an orchestrator account that injects faults into resources belonging to one or more target accounts. You can easily configure a multi-account experiment template and control its scope by using IAM roles with fine-grained permissions and resource tags to specify each target. When running an experiment, FIS provides you with multi-account visibility and safety. You have visibility into the actions FIS takes across all accounts from the FIS Console, and can review and audit the API calls FIS makes in each account with AWS CloudTrail. In addition, accounts with affected resources will be notified via their AWS Health dashboards, providing awareness to other accounts and users.
Multi-account experiments are available in all AWS Regions where FIS is available, including the AWS GovCloud (US) Regions.
To get started using multi-account experiments, log in to FIS in the AWS Management Console. For detailed pricing information, please visit the FIS pricing page. To learn more, view the documentation.