Amazon Fault Injection Simulator now supports logging to Amazon CloudWatch Logs and Amazon S3
You can now record Amazon Fault Injection Simulator (FIS) experiment activities by sending logs to Amazon CloudWatch Logs or Amazon S3. AWS FIS experiment logs contain detailed information about experiments, actions, and targets, including start and end times, action names, and target resource ARNs. You can use these logs to identify the activities performed by AWS FIS experiments and correlate them with your systems’ responses and monitoring and observability tools, so that you can implement improvements. In addition, you can use experiment timeline charts in the AWS Management Console to monitor a running or completed experiment.
You can now record Amazon Fault Injection Simulator (FIS) experiment activities by sending logs to Amazon CloudWatch Logs or Amazon S3. AWS FIS experiment logs contain detailed information about experiments, actions, and targets, including start and end times, action names, and target resource ARNs. You can use these logs to identify the activities performed by AWS FIS experiments and correlate them with your systems’ responses and monitoring and observability tools, so that you can implement improvements. In addition, you can use experiment timeline charts in the AWS Management Console to monitor a running or completed experiment.
Experiment logging is turned off by default. To get started logging AWS FIS experiments using the AWS Management Console or CLI, first create or update an experiment template. Then, choose the option to enable logging, and select your destination Amazon S3 bucket or Amazon CloudWatch Logs log group.
AWS FIS experiment logging is available now in all commercial AWS Regions. You can get started creating and running fault injection experiments using AWS FIS in the AWS Management Console or using the AWS SDKs and CLI.