# Managing your AWS FIS experiments
<a name="experiments"></a>

AWS FIS enables you to perform fault injection experiments on your AWS workloads. To get started, create an [experiment template](experiment-templates.md). After you create an experiment template, you can use it to start an experiment.

An experiment is finished when one of the following occurs:
+ All [actions](action-sequence.md) in the template completed successfully.
+ A [stop condition](stop-conditions.md) is triggered.
+ An action cannot be completed because of an error. For example, if the [target](targets.md) cannot be found.
+ The experiment is [stopped manually](stop-experiment.md).

You cannot resume a stopped or failed experiment. You also cannot rerun a completed experiment. However, you can start a new experiment from the same experiment template. You can optionally update the experiment template before you specify it again in a new experiment.

**Topics**
+ [

# Start an experiment
](run-experiment.md)
+ [

# View your experiments
](view-experiment-progress.md)
+ [

# Tag an experiment
](tag-experiment.md)
+ [

# Stop an experiment
](stop-experiment.md)
+ [

# List resolved targets
](list-experiment-resolved-targets.md)

# Start an experiment
<a name="run-experiment"></a>

You start an experiment from an experiment template. For more information, see [Start an experiment from a template](start-experiment-from-template.md).

You can schedule your experiments as a one-time task or recurring tasks using Amazon EventBridge. For more information, see [Tutorial: Schedule a recurring experiment](fis-tutorial-recurring-experiment.md).

You can monitor your experiment using any of the following features:
+ View your experiments in the AWS FIS console. For more information, see [View your experiments](view-experiment-progress.md).
+ View Amazon CloudWatch metrics for the target resources in your experiments or view AWS FIS usage metrics. For more information, see [Monitor using CloudWatch](monitoring-cloudwatch.md).
+ Enable experiment logging to capture detailed information about your experiment as it runs. For more information see [Experiment logging](monitoring-logging.md).

# View your experiments
<a name="view-experiment-progress"></a>

You can view the progress of a running experiment, and you can view experiments that have completed, stopped, or failed.

Stopped, completed, and failed experiments are automatically removed from your account after 120 days.

**To view experiments using the console**

1. Open the AWS FIS console at [https://console.aws.amazon.com/fis/](https://console.aws.amazon.com/fis/).

1. In the navigation pane, choose **Experiments**.

1. Choose the **Experiment ID** of the experiment to open its details page.

1. Do one or more of the following:
   + Check **Details**, **State** for the [state of the experiment](#experiment-states).
   + Choose the **Actions** tab for information about the experiment actions.
   + Choose the **Targets** tab for information about the experiment targets.
   + Choose the **Timeline** tab for a visual representation of the actions based on their start and end times.

**To view experiments using the CLI**  
Use the [list-experiments](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/fis/list-experiments.html) command to get a list of experiments, and use the [get-experiment](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/fis/get-experiment.html) command to get information about a specific experiment.

## Experiment states
<a name="experiment-states"></a>

An experiment can be in one of the following states:
+ **pending** – The experiment is pending.
+ **initiating** – The experiment is preparing to start.
+ **running** – The experiment is running.
+ **completed** – All actions in the experiment completed successfully.
+ **stopping** – The stop condition was triggered or the experiment was stopped manually.
+ **stopped** – All running or pending actions in the experiment are stopped.
+ **failed** – The experiment failed due to an error, such as insufficient permissions or incorrect syntax.
+ **cancelled** – The experimented was stopped or prevented from starting due to an engaged safety lever.

## Action states
<a name="action-states"></a>

An action can be in one of the following states:
+ **pending** – The action is pending, either because the experiment hasn't started or the action is to start later in the experiment.
+ **initiating** – The action is preparing to start.
+ **running** – The action is running.
+ **completed** – The action completed successfully.
+ **cancelled** – The experiment stopped before the action started.
+ **skipped** – The action has been skipped.
+ **stopping** – The action is stopping.
+ **stopped** – All running or pending actions in the experiment are stopped.
+ **failed** – The action failed due to a client error, such as insufficient permissions or incorrect syntax.

# Tag an experiment
<a name="tag-experiment"></a>

You can apply tags to experiments to help you organize them. You can also implement [tag-based IAM policies](security_iam_service-with-iam.md#security_iam_service-with-iam-tags) to control access to experiments.

**To tag an experiment using the console**

1. Open the AWS FIS console at [https://console.aws.amazon.com/fis/](https://console.aws.amazon.com/fis/).

1. In the navigation pane, choose **Experiments**.

1. Select the experiment and choose **Actions**, **Manage tags**.

1. To add a new tag, choose **Add new tag**, and specify a key and value.

   To remove a tag, choose **Remove** for the tag.

1. Choose **Save**.

**To tag an experiment using the CLI**  
Use the [tag-resource](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/fis/tag-resource.html) command.

# Stop an experiment
<a name="stop-experiment"></a>

You can stop a running experiment at any time. When you stop an experiment, any post actions that have not been completed for an action are completed before the experiment stops. You cannot resume a stopped experiment.

**To stop an experiment using the console**

1. Open the AWS FIS console at [https://console.aws.amazon.com/fis/](https://console.aws.amazon.com/fis/).

1. In the navigation pane, choose **Experiments**.

1. Select the experiment, and choose **Stop experiment**.

1. In the confirmation dialog box, choose **Stop experiment**.

**To stop an experiment using the CLI**  
Use the [stop-experiment](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/fis/stop-experiment.html) command.

# List resolved targets
<a name="list-experiment-resolved-targets"></a>

You can view information for resolved targets for an experiment after target resolution has ended.

**To view resolved targets using the console**

1. Open the AWS FIS console at [https://console.aws.amazon.com/fis/](https://console.aws.amazon.com/fis/).

1. In the navigation pane, choose **Experiments**.

1. Select the experiment, and choose **Report**.

1. View resolved target information under **Resources**.

**To view resolved targets using the CLI**  
Use the [list-experiment-resolved-targets](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/fis/list-experiment-resolved-targets.html) command.