# Security in AWS Fault Injection Service
Cloud security at AWS is the highest priority. As an AWS customer, you benefit from data centers and network architectures that are built to meet the requirements of the most security-sensitive organizations.
Security is a shared responsibility between AWS and you. The [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) describes this as security *of* the cloud and security *in* the cloud:
+ **Security of the cloud** – AWS is responsible for protecting the infrastructure that runs AWS services in the AWS Cloud. AWS also provides you with services that you can use securely. Third-party auditors regularly test and verify the effectiveness of our security as part of the [AWS Compliance Programs](https://aws.amazon.com/compliance/programs/). To learn about the compliance programs that apply to AWS Fault Injection Service, see [AWS Services in Scope by Compliance Program](https://aws.amazon.com/compliance/services-in-scope/).
+ **Security in the cloud** – Your responsibility is determined by the AWS service that you use. You are also responsible for other factors including the sensitivity of your data, your company’s requirements, and applicable laws and regulations.
This documentation helps you understand how to apply the shared responsibility model when using AWS FIS. The following topics show you how to configure AWS FIS to meet your security and compliance objectives. You also learn how to use other AWS services that help you to monitor and secure your AWS FIS resources.
**Topics**
+ [Data protection in AWS Fault Injection Service](data-protection.md)
+ [Identity and access management for AWS Fault Injection Service](security-iam.md)
+ [Infrastructure security in AWS Fault Injection Service](infrastructure-security.md)
+ [Access AWS FIS using an interface VPC endpoint (AWS PrivateLink)](vpc-interface-endpoints.md)
# Data protection in AWS Fault Injection Service
The AWS [shared responsibility model](https://aws.amazon.com/compliance/shared-responsibility-model/) applies to data protection in AWS Fault Injection Service. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. You are also responsible for the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the [Data Privacy FAQ](https://aws.amazon.com/compliance/data-privacy-faq/). For information about data protection in Europe, see the [AWS Shared Responsibility Model and GDPR](https://aws.amazon.com/blogs/security/the-aws-shared-responsibility-model-and-gdpr/) blog post on the *AWS Security Blog*.
For data protection purposes, we recommend that you protect AWS account credentials and set up individual users with AWS IAM Identity Center or AWS Identity and Access Management (IAM). That way, each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:
+ Use multi-factor authentication (MFA) with each account.
+ Use SSL/TLS to communicate with AWS resources. We require TLS 1.2 and recommend TLS 1.3.
+ Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see [Working with CloudTrail trails](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-trails.html) in the *AWS CloudTrail User Guide*.
+ Use AWS encryption solutions, along with all default security controls within AWS services.
+ Use advanced managed security services such as Amazon Macie, which assists in discovering and securing sensitive data that is stored in Amazon S3.
+ If you require FIPS 140-3 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see [Federal Information Processing Standard (FIPS) 140-3](https://aws.amazon.com/compliance/fips/).
We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a **Name** field. This includes when you work with AWS FIS or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.
## Encryption at rest
AWS FIS always encrypts your data at rest. Data in AWS FIS is encrypted at rest using transparent server-side encryption. This helps reduce the operational burden and complexity involved in protecting sensitive data. With encryption at rest, you can build security-sensitive applications that meet encryption compliance and regulatory requirements.
## Encryption in transit
AWS FIS encrypts data in transit between the service and other integrated AWS services. All data that passes between AWS FIS and integrated services is encrypted using Transport Layer Security (TLS). For more information about other integrated AWS services, see [Supported AWS services](what-is.md#supported-services).
# Identity and access management for AWS Fault Injection Service
AWS Identity and Access Management (IAM) is an AWS service that helps an administrator securely control access to AWS resources. IAM administrators control who can be *authenticated* (signed in) and *authorized* (have permissions) to use AWS FIS resources. IAM is an AWS service that you can use with no additional charge.
**Topics**
+ [Audience](#security_iam_audience)
+ [Authenticating with identities](#security_iam_authentication)
+ [Managing access using policies](#security_iam_access-manage)
+ [How AWS Fault Injection Service works with IAM](security_iam_service-with-iam.md)
+ [Policy examples](security_iam_id-based-policy-examples.md)
+ [Use service-linked roles](using-service-linked-roles.md)
+ [AWS managed policies](security-iam-awsmanpol.md)
## Audience
How you use AWS Identity and Access Management (IAM) differs, depending on the work that you do in AWS FIS.
**Service user** – If you use the AWS FIS service to do your job, then your administrator provides you with the credentials and permissions that you need. As you use more AWS FIS features to do your work, you might need additional permissions. Understanding how access is managed can help you request the right permissions from your administrator.
**Service administrator** – If you're in charge of AWS FIS resources at your company, you probably have full access to AWS FIS. It's your job to determine which AWS FIS features and resources your service users should access. You must then submit requests to your IAM administrator to change the permissions of your service users. Review the information on this page to understand the basic concepts of IAM.
**IAM administrator** – If you're an IAM administrator, you might want to learn details about how you can write policies to manage access to AWS FIS.
## Authenticating with identities
Authentication is how you sign in to AWS using your identity credentials. You must be authenticated as the AWS account root user, an IAM user, or by assuming an IAM role.
You can sign in as a federated identity using credentials from an identity source like AWS IAM Identity Center (IAM Identity Center), single sign-on authentication, or Google/Facebook credentials. For more information about signing in, see [How to sign in to your AWS account](https://docs.aws.amazon.com/signin/latest/userguide/how-to-sign-in.html) in the *AWS Sign-In User Guide*.
For programmatic access, AWS provides an SDK and CLI to cryptographically sign requests. For more information, see [AWS Signature Version 4 for API requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html) in the *IAM User Guide*.
### AWS account root user
When you create an AWS account, you begin with one sign-in identity called the AWS account *root user* that has complete access to all AWS services and resources. We strongly recommend that you don't use the root user for everyday tasks. For tasks that require root user credentials, see [Tasks that require root user credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html#root-user-tasks) in the *IAM User Guide*.
### Federated identity
As a best practice, require human users to use federation with an identity provider to access AWS services using temporary credentials.
A *federated identity* is a user from your enterprise directory, web identity provider, or Directory Service that accesses AWS services using credentials from an identity source. Federated identities assume roles that provide temporary credentials.
For centralized access management, we recommend AWS IAM Identity Center. For more information, see [What is IAM Identity Center?](https://docs.aws.amazon.com/singlesignon/latest/userguide/what-is.html) in the *AWS IAM Identity Center User Guide*.
### IAM users and groups
An *[IAM user](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html)* is an identity with specific permissions for a single person or application. We recommend using temporary credentials instead of IAM users with long-term credentials. For more information, see [Require human users to use federation with an identity provider to access AWS using temporary credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#bp-users-federation-idp) in the *IAM User Guide*.
An [https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_groups.html) specifies a collection of IAM users and makes permissions easier to manage for large sets of users. For more information, see [Use cases for IAM users](https://docs.aws.amazon.com/IAM/latest/UserGuide/gs-identities-iam-users.html) in the *IAM User Guide*.
### IAM roles
An *[IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html)* is an identity with specific permissions that provides temporary credentials. You can assume a role by [switching from a user to an IAM role (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-console.html) or by calling an AWS CLI or AWS API operation. For more information, see [Methods to assume a role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_manage-assume.html) in the *IAM User Guide*.
IAM roles are useful for federated user access, temporary IAM user permissions, cross-account access, cross-service access, and applications running on Amazon EC2. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Managing access using policies
You control access in AWS by creating policies and attaching them to AWS identities or resources. A policy defines permissions when associated with an identity or resource. AWS evaluates these policies when a principal makes a request. Most policies are stored in AWS as JSON documents. For more information about JSON policy documents, see [Overview of JSON policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#access_policies-json) in the *IAM User Guide*.
Using policies, administrators specify who has access to what by defining which **principal** can perform **actions** on what **resources**, and under what **conditions**.
By default, users and roles have no permissions. An IAM administrator creates IAM policies and adds them to roles, which users can then assume. IAM policies define permissions regardless of the method used to perform the operation.
### Identity-based policies
Identity-based policies are JSON permissions policy documents that you attach to an identity (user, group, or role). These policies control what actions identities can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
Identity-based policies can be *inline policies* (embedded directly into a single identity) or *managed policies* (standalone policies attached to multiple identities). To learn how to choose between managed and inline policies, see [Choose between managed policies and inline policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-choosing-managed-or-inline.html) in the *IAM User Guide*.
### Resource-based policies
Resource-based policies are JSON policy documents that you attach to a resource. Examples include IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy.
Resource-based policies are inline policies that are located in that service. You can't use AWS managed policies from IAM in a resource-based policy.
### Other policy types
AWS supports additional policy types that can set the maximum permissions granted by more common policy types:
+ **Permissions boundaries** – Set the maximum permissions that an identity-based policy can grant to an IAM entity. For more information, see [Permissions boundaries for IAM entities](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html) in the *IAM User Guide*.
+ **Service control policies (SCPs)** – Specify the maximum permissions for an organization or organizational unit in AWS Organizations. For more information, see [Service control policies](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_scps.html) in the *AWS Organizations User Guide*.
+ **Resource control policies (RCPs)** – Set the maximum available permissions for resources in your accounts. For more information, see [Resource control policies (RCPs)](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_rcps.html) in the *AWS Organizations User Guide*.
+ **Session policies** – Advanced policies passed as a parameter when creating a temporary session for a role or federated user. For more information, see [Session policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html#policies_session) in the *IAM User Guide*.
### Multiple policy types
When multiple types of policies apply to a request, the resulting permissions are more complicated to understand. To learn how AWS determines whether to allow a request when multiple policy types are involved, see [Policy evaluation logic](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html) in the *IAM User Guide*.
# How AWS Fault Injection Service works with IAM
Before you use IAM to manage access to AWS FIS, learn what IAM features are available to use with AWS FIS.
**IAM features you can use with AWS Fault Injection Service**
| IAM feature | AWS FIS support |
| --- | --- |
| [Identity-based policies](#security_iam_service-with-iam-id-based-policies) | Yes |
| [Resource-based policies](#security_iam_service-with-iam-resource-based-policies) | No |
| [Policy actions](#security_iam_service-with-iam-id-based-policies-actions) | Yes |
| [Policy resources](#security_iam_service-with-iam-id-based-policies-resources) | Yes |
| [Policy condition keys (service-specific)](#security_iam_service-with-iam-id-based-policies-conditionkeys) | Yes |
| [ACLs](#security_iam_service-with-iam-acls) | No |
| [ABAC (tags in policies)](#security_iam_service-with-iam-tags) | Yes |
| [Temporary credentials](#security_iam_service-with-iam-roles-tempcreds) | Yes |
| [Principal permissions](#security_iam_service-with-iam-principal-permissions) | Yes |
| [Service roles](#security_iam_service-with-iam-roles-service) | Yes |
| [Service-linked roles](#security_iam_service-with-iam-roles-service-linked) | Yes |
To get a high-level view of how AWS FIS and other AWS services work with most IAM features, see [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Identity-based policies for AWS FIS
**Supports identity-based policies:** Yes
Identity-based policies are JSON permissions policy documents that you can attach to an identity, such as an IAM user, group of users, or role. These policies control what actions users and roles can perform, on which resources, and under what conditions. To learn how to create an identity-based policy, see [Define custom IAM permissions with customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the *IAM User Guide*.
With IAM identity-based policies, you can specify allowed or denied actions and resources as well as the conditions under which actions are allowed or denied. To learn about all of the elements that you can use in a JSON policy, see [IAM JSON policy elements reference](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html) in the *IAM User Guide*.
### Identity-based policy examples for AWS FIS
To view examples of AWS FIS identity-based policies, see [AWS Fault Injection Service policy examples](security_iam_id-based-policy-examples.md).
## Resource-based policies within AWS FIS
**Supports resource-based policies:** No
Resource-based policies are JSON policy documents that you attach to a resource. Examples of resource-based policies are IAM *role trust policies* and Amazon S3 *bucket policies*. In services that support resource-based policies, service administrators can use them to control access to a specific resource. For the resource where the policy is attached, the policy defines what actions a specified principal can perform on that resource and under what conditions. You must [specify a principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html) in a resource-based policy. Principals can include accounts, users, roles, federated users, or AWS services.
To enable cross-account access, you can specify an entire account or IAM entities in another account as the principal in a resource-based policy. For more information, see [Cross account resource access in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies-cross-account-resource-access.html) in the *IAM User Guide*.
## Policy actions for AWS FIS
**Supports policy actions:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Action` element of a JSON policy describes the actions that you can use to allow or deny access in a policy. Include actions in a policy to grant permissions to perform the associated operation.
To see a list of AWS FIS actions, see [Actions defined by AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html#amazonec2-actions-as-permissions) in the *Service Authorization Reference*.
Policy actions in AWS FIS use the following prefix before the action:
```
fis
```
To specify multiple actions in a single statement, separate them with commas.
```
"Action": [
"fis:action1",
"fis:action2"
]
```
You can specify multiple actions using wildcards (\$1). For example, to specify all actions that begin with the word `List`, include the following action:
```
"Action": "fis:List*"
```
## Policy resources for AWS FIS
**Supports policy resources:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Resource` JSON policy element specifies the object or objects to which the action applies. As a best practice, specify a resource using its [Amazon Resource Name (ARN)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference-arns.html). For actions that don't support resource-level permissions, use a wildcard (\$1) to indicate that the statement applies to all resources.
```
"Resource": "*"
```
Some AWS FIS API actions support multiple resources. To specify multiple resources in a single statement, separate the ARNs with commas.
```
"Resource": [
"resource1",
"resource2"
]
```
To see a list of AWS FIS resource types and their ARNs, see [Resource types defined by AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html#amazonec2-resources-for-iam-policies) in the *Service Authorization Reference*. To learn with which actions you can specify the ARN of each resource, see [Actions defined by AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html#amazonec2-actions-as-permissions).
## Policy condition keys for AWS FIS
**Supports service-specific policy condition keys:** Yes
Administrators can use AWS JSON policies to specify who has access to what. That is, which **principal** can perform **actions** on what **resources**, and under what **conditions**.
The `Condition` element specifies when statements execute based on defined criteria. You can create conditional expressions that use [condition operators](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition_operators.html), such as equals or less than, to match the condition in the policy with values in the request. To see all AWS global condition keys, see [AWS global condition context keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html) in the *IAM User Guide*.
To see a list of AWS FIS condition keys, see [Condition keys for AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html#amazonec2-policy-keys) in the *Service Authorization Reference*. To learn with which actions and resources you can use a condition key, see [Actions defined by AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html#amazonec2-actions-as-permissions).
To view examples of AWS FIS identity-based policies, see [AWS Fault Injection Service policy examples](security_iam_id-based-policy-examples.md).
## ACLs in AWS FIS
**Supports ACLs:** No
Access control lists (ACLs) control which principals (account members, users, or roles) have permissions to access a resource. ACLs are similar to resource-based policies, although they do not use the JSON policy document format.
## ABAC with AWS FIS
**Supports ABAC (tags in policies):** Yes
Attribute-based access control (ABAC) is an authorization strategy that defines permissions based on attributes called tags. You can attach tags to IAM entities and AWS resources, then design ABAC policies to allow operations when the principal's tag matches the tag on the resource.
To control access based on tags, you provide tag information in the [condition element](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) of a policy using the `aws:ResourceTag/key-name`, `aws:RequestTag/key-name`, or `aws:TagKeys` condition keys.
If a service supports all three condition keys for every resource type, then the value is **Yes** for the service. If a service supports all three condition keys for only some resource types, then the value is **Partial**.
For more information about ABAC, see [Define permissions with ABAC authorization](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_attribute-based-access-control.html) in the *IAM User Guide*. To view a tutorial with steps for setting up ABAC, see [Use attribute-based access control (ABAC)](https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_attribute-based-access-control.html) in the *IAM User Guide*.
To view an example identity-based policy for limiting access to a resource based on the tags for that resource, see [Example: Use tags to control resource usage](security_iam_id-based-policy-examples.md#security-iam-policy-examples-tagging).
## Using temporary credentials with AWS FIS
**Supports temporary credentials:** Yes
Temporary credentials provide short-term access to AWS resources and are automatically created when you use federation or switch roles. AWS recommends that you dynamically generate temporary credentials instead of using long-term access keys. For more information, see [Temporary security credentials in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html) and [AWS services that work with IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html) in the *IAM User Guide*.
## Cross-service principal permissions for AWS FIS
**Supports forward access sessions (FAS):** Yes
Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).
## Service roles for AWS FIS
**Supports service roles:** Yes
A service role is an [IAM role](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles.html) that a service assumes to perform actions on your behalf. An IAM administrator can create, modify, and delete a service role from within IAM. For more information, see [Create a role to delegate permissions to an AWS service](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-service.html) in the *IAM User Guide*.
## Service-linked roles for AWS FIS
**Supports service-linked roles:** Yes
A service-linked role is a type of service role that is linked to an AWS service. The service can assume the role to perform an action on your behalf. Service-linked roles appear in your AWS account and are owned by the service. An IAM administrator can view, but not edit the permissions for service-linked roles.
For details about creating or managing AWS FIS service-linked roles, see [Use service-linked roles for AWS Fault Injection Service](using-service-linked-roles.md).
# AWS Fault Injection Service policy examples
By default, users and roles don't have permission to create or modify AWS FIS resources. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies.
To learn how to create an IAM identity-based policy by using these example JSON policy documents, see [Create IAM policies (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create-console.html) in the *IAM User Guide*.
For details about actions and resource types defined by AWS FIS, including the format of the ARNs for each of the resource types, see [Actions, resources, and condition keys for AWS Fault Injection Service](https://docs.aws.amazon.com/service-authorization/latest/reference/list_awsfaultinjectionservice.html) in the *Service Authorization Reference*.
**Topics**
+ [Policy best practices](#security_iam_service-with-iam-policy-best-practices)
+ [Example: Use the AWS FIS console](#security-iam-policy-examples-console)
+ [Example: List available AWS FIS actions](#security-iam-policy-examples-list-actions)
+ [Example: Create an experiment template for a specific action](#security-iam-policy-examples-create-template)
+ [Example: Start an experiment](#security-iam-policy-examples-start-experiment)
+ [Example: Use tags to control resource usage](#security-iam-policy-examples-tagging)
+ [Example: Delete an experiment template with a specific tag](#security-iam-policy-examples-delete-tagged-template)
+ [Example: Allow users to view their own permissions](#security_iam_id-based-policy-examples-view-own-permissions)
+ [Example: Use condition keys for `ec2:InjectApiError`](#security-iam-policy-examples-ec2)
+ [Example: Use condition keys for `aws:s3:bucket-pause-replication`](#security-iam-policy-examples-s3)
## Policy best practices
Identity-based policies determine whether someone can create, access, or delete AWS FIS resources in your account. These actions can incur costs for your AWS account. When you create or edit identity-based policies, follow these guidelines and recommendations:
+ **Get started with AWS managed policies and move toward least-privilege permissions** – To get started granting permissions to your users and workloads, use the *AWS managed policies* that grant permissions for many common use cases. They are available in your AWS account. We recommend that you reduce permissions further by defining AWS customer managed policies that are specific to your use cases. For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) or [AWS managed policies for job functions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_job-functions.html) in the *IAM User Guide*.
+ **Apply least-privilege permissions** – When you set permissions with IAM policies, grant only the permissions required to perform a task. You do this by defining the actions that can be taken on specific resources under specific conditions, also known as *least-privilege permissions*. For more information about using IAM to apply permissions, see [ Policies and permissions in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) in the *IAM User Guide*.
+ **Use conditions in IAM policies to further restrict access** – You can add a condition to your policies to limit access to actions and resources. For example, you can write a policy condition to specify that all requests must be sent using SSL. You can also use conditions to grant access to service actions if they are used through a specific AWS service, such as CloudFormation. For more information, see [ IAM JSON policy elements: Condition](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_condition.html) in the *IAM User Guide*.
+ **Use IAM Access Analyzer to validate your IAM policies to ensure secure and functional permissions** – IAM Access Analyzer validates new and existing policies so that the policies adhere to the IAM policy language (JSON) and IAM best practices. IAM Access Analyzer provides more than 100 policy checks and actionable recommendations to help you author secure and functional policies. For more information, see [Validate policies with IAM Access Analyzer](https://docs.aws.amazon.com/IAM/latest/UserGuide/access-analyzer-policy-validation.html) in the *IAM User Guide*.
+ **Require multi-factor authentication (MFA)** – If you have a scenario that requires IAM users or a root user in your AWS account, turn on MFA for additional security. To require MFA when API operations are called, add MFA conditions to your policies. For more information, see [ Secure API access with MFA](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_mfa_configure-api-require.html) in the *IAM User Guide*.
For more information about best practices in IAM, see [Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html) in the *IAM User Guide*.
## Example: Use the AWS FIS console
To access the AWS Fault Injection Service console, you must have a minimum set of permissions. These permissions must allow you to list and view details about the AWS FIS resources in your AWS account. If you create an identity-based policy that is more restrictive than the minimum required permissions, the console won't function as intended for entities (users or roles) with that policy.
You don't need to allow minimum console permissions for users that are making calls only to the AWS CLI or the AWS API. Instead, allow access to only the actions that match the API operation that they're trying to perform.
The following example policy grants permission to list and view all AWS FIS resources using AWS FIS console, but not to create, update, or delete them. It also grants permissions to view the available resources used by all AWS FIS actions that you could specify in an experiment template.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "FISReadOnlyActions",
"Effect": "Allow",
"Action": [
"fis:List*",
"fis:Get*"
],
"Resource": "*"
},
{
"Sid": "AdditionalReadOnlyActions",
"Effect": "Allow",
"Action": [
"ssm:Describe*",
"ssm:Get*",
"ssm:List*",
"ec2:DescribeInstances",
"rds:DescribeDBClusters",
"ecs:DescribeClusters",
"ecs:ListContainerInstances",
"eks:DescribeNodegroup",
"cloudwatch:DescribeAlarms",
"iam:ListRoles"
],
"Resource": "*"
},
{
"Sid": "PermissionsToCreateServiceLinkedRole",
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "*",
"Condition": {
"StringEquals": {
"iam:AWSServiceName": "fis.amazonaws.com"
}
}
}
]
}
```
------
## Example: List available AWS FIS actions
The following policy grants permission to list the available AWS FIS actions.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"fis:ListActions"
],
"Resource": "arn:aws:fis:*:*:action/*"
}
]
}
```
------
## Example: Create an experiment template for a specific action
The following policy grants permission to create an experiment template for the action `aws:ec2:stop-instances`.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "PolicyExample",
"Effect": "Allow",
"Action": [
"fis:CreateExperimentTemplate"
],
"Resource": [
"arn:aws:fis:*:*:action/aws:ec2:stop-instances",
"arn:aws:fis:*:*:experiment-template/*"
]
},
{
"Sid": "PolicyPassRoleExample",
"Effect": "Allow",
"Action": [
"iam:PassRole"
],
"Resource": [
"arn:aws:iam::111122223333:role/role-name"
]
}
]
}
```
------
## Example: Start an experiment
The following policy grants permission to start an experiment using the specified IAM role and experiment template. It also allows AWS FIS to create a service-linked role on the user's behalf. For more information, see [Use service-linked roles for AWS Fault Injection Service](using-service-linked-roles.md).
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Sid": "PolicyExample",
"Effect": "Allow",
"Action": [
"fis:StartExperiment"
],
"Resource": [
"arn:aws:fis:*:*:experiment-template/experiment-template-id",
"arn:aws:fis:*:*:experiment/*"
]
},
{
"Sid": "PolicyExampleforServiceLinkedRole",
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "*",
"Condition": {
"StringEquals": {
"iam:AWSServiceName": "fis.amazonaws.com"
}
}
}
]
}
```
------
## Example: Use tags to control resource usage
The following policy grants permission to run experiments from experiment templates that have the tag `Purpose=Test`. It does not grant permission to create or modify experiment templates, or run experiments using templates that do not have the specified tag.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "fis:StartExperiment",
"Resource": "arn:aws:fis:*:*:experiment-template/*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/Purpose": "Test"
}
}
}
]
}
```
------
## Example: Delete an experiment template with a specific tag
The following policy grants permission to delete an experiment template with tag `Purpose=Test`.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"fis:DeleteExperimentTemplate"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/Purpose": "Test"
}
}
}
]
}
```
------
## Example: Allow users to view their own permissions
This example shows how you might create a policy that allows IAM users to view the inline and managed policies that are attached to their user identity. This policy includes permissions to complete this action on the console or programmatically using the AWS CLI or AWS API.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ViewOwnUserInfo",
"Effect": "Allow",
"Action": [
"iam:GetUserPolicy",
"iam:ListGroupsForUser",
"iam:ListAttachedUserPolicies",
"iam:ListUserPolicies",
"iam:GetUser"
],
"Resource": ["arn:aws:iam::*:user/${aws:username}"]
},
{
"Sid": "NavigateInConsole",
"Effect": "Allow",
"Action": [
"iam:GetGroupPolicy",
"iam:GetPolicyVersion",
"iam:GetPolicy",
"iam:ListAttachedGroupPolicies",
"iam:ListGroupPolicies",
"iam:ListPolicyVersions",
"iam:ListPolicies",
"iam:ListUsers"
],
"Resource": "*"
}
]
}
```
## Example: Use condition keys for `ec2:InjectApiError`
The following example policy uses the `ec2:FisTargetArns` condition key to scope target resources. This policy allows the AWS FIS actions `aws:ec2:api-insufficient-instance-capacity-error` and `aws:ec2:asg-insufficient-instance-capacity-error`.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ec2:InjectApiError",
"Resource": "*",
"Condition": {
"StringEquals": {
"ec2:FisActionId": [
"aws:ec2:api-insufficient-instance-capacity-error",
"aws:ec2:asg-insufficient-instance-capacity-error"
]
}
}
},
{
"Effect": "Allow",
"Action": "ec2:InjectApiError",
"Resource": "*",
"Condition": {
"ForAllValues:ArnLike": {
"ec2:FisTargetArns": [
"arn:aws:autoscaling:*:*:autoScalingGroup:uuid:autoScalingGroupName/asg-name"
]
}
}
},
{
"Effect": "Allow",
"Action": "autoscaling:DescribeAutoScalingGroups",
"Resource": "*"
}
]
}
```
------
## Example: Use condition keys for `aws:s3:bucket-pause-replication`
The following example policy uses the `S3:IsReplicationPauseRequest` condition key to allow `PutReplicationConfiguration` and `GetReplicationConfiguration` only when used by AWS FIS in the context of the AWS FIS action `aws:s3:bucket-pause-replication`.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"S3:PauseReplication"
],
"Resource": "arn:aws:s3:::mybucket",
"Condition": {
"StringEquals": {
"s3:DestinationRegion": "region"
}
}
},
{
"Effect": "Allow",
"Action": [
"S3:PutReplicationConfiguration",
"S3:GetReplicationConfiguration"
],
"Resource": "arn:aws:s3:::mybucket",
"Condition": {
"BoolIfExists": {
"s3:IsReplicationPauseRequest": "true"
}
}
},
{
"Effect": "Allow",
"Action": [
"S3:ListBucket"
],
"Resource": "arn:aws:s3:::*"
},
{
"Effect": "Allow",
"Action": [
"tag:GetResources"
],
"Resource": "*"
}
]
}
```
------
# Use service-linked roles for AWS Fault Injection Service
AWS Fault Injection Service uses AWS Identity and Access Management (IAM) [service-linked roles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role). A service-linked role is a unique type of IAM role that is linked directly to AWS FIS. Service-linked roles are predefined by AWS FIS and include all of the permissions that the service requires to call other AWS services on your behalf.
A service-linked role makes setting up AWS FIS easier because you don’t have to manually add the necessary permissions to manage monitoring and resource selection for experiments. AWS FIS defines the permissions of its service-linked roles, and unless defined otherwise, only AWS FIS can assume its roles. The defined permissions include the trust policy and the permissions policy, and that permissions policy cannot be attached to any other IAM entity.
In addition to the service-linked role, you must also specify an IAM role that grants permission to modify the resources that you specify as targets in an experiment template. For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
You can delete a service-linked role only after first deleting the related resources. This protects your AWS FIS resources because you can't inadvertently remove permission to access the resources.
## Service-linked role permissions for AWS FIS
AWS FIS uses the service-linked role named ****AWSServiceRoleForFIS**** to enable it to manage monitoring and resource selection for experiments.
The **AWSServiceRoleForFIS** service-linked role trusts the following services to assume the role:
+ `fis.amazonaws.com`
The **AWSServiceRoleForFIS** service-linked role uses the managed policy **AmazonFISServiceRolePolicy**. This policy enables AWS FIS to manage monitoring and resource selection for experiments. For more information, see [AmazonFISServiceRolePolicy](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AmazonFISServiceRolePolicy.html) in the *AWS Managed Policy Reference*.
You must configure permissions to allow an IAM entity (such as a user, group, or role) to create, edit, or delete a service-linked role. For the ****AWSServiceRoleForFIS**** service-linked role to be successfully created, the IAM identity that you use AWS FIS with must have the required permissions. To grant the required permissions, attach the following policy to the IAM identity.
------
#### [ JSON ]
****
```
{
"Version":"2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "iam:CreateServiceLinkedRole",
"Resource": "*",
"Condition": {
"StringLike": {
"iam:AWSServiceName": "fis.amazonaws.com"
}
}
}
]
}
```
------
For more information, see [Service-linked role permissions](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#service-linked-role-permissions) in the *IAM User Guide*.
## Create a service-linked role for AWS FIS
You don't need to manually create a service-linked role. When you start an AWS FIS experiment in the AWS Management Console, the AWS CLI, or the AWS API, AWS FIS creates the service-linked role for you.
If you delete this service-linked role, and then need to create it again, you can use the same process to recreate the role in your account. When you start an AWS FIS experiment, AWS FIS creates the service-linked role for you again.
## Edit a service-linked role for AWS FIS
AWS FIS does not allow you to edit the **AWSServiceRoleForFIS** service-linked role. After you create a service-linked role, you cannot change the name of the role because various entities might reference the role. However, you can edit the description of the role using IAM. For more information, see [Editing a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#edit-service-linked-role) in the *IAM User Guide*.
## Delete a service-linked role for AWS FIS
If you no longer need to use a feature or service that requires a service-linked role, we recommend that you delete that role. That way you don’t have an unused entity that is not actively monitored or maintained. However, you must clean up the resources for your service-linked role before you can manually delete it.
**Note**
If the AWS FIS service is using the role when you try to clean up the resources, then the cleanup might fail. If that happens, wait for a few minutes and try the operation again.
**To clean up AWS FIS resources used by the **AWSServiceRoleForFIS****
Make sure that none of your experiments are currently running. If necessary, stop your experiments. For more information, see [Stop an experiment](stop-experiment.md).
**To manually delete the service-linked role using IAM**
Use the IAM console, the AWS CLI, or the AWS API to delete the **AWSServiceRoleForFIS** service-linked role. For more information, see [Deleting a service-linked role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#delete-service-linked-role) in the *IAM User Guide*.
## Supported Regions for AWS FIS service-linked roles
AWS FIS supports using service-linked roles in all of the Regions where the service is available. For more information, see [AWS Fault Injection Service endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/fis.html).
# AWS managed policies for AWS Fault Injection Service
An AWS managed policy is a standalone policy that is created and administered by AWS. AWS managed policies are designed to provide permissions for many common use cases so that you can start assigning permissions to users, groups, and roles.
Keep in mind that AWS managed policies might not grant least-privilege permissions for your specific use cases because they're available for all AWS customers to use. We recommend that you reduce permissions further by defining [ customer managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#customer-managed-policies) that are specific to your use cases.
You cannot change the permissions defined in AWS managed policies. If AWS updates the permissions defined in an AWS managed policy, the update affects all principal identities (users, groups, and roles) that the policy is attached to. AWS is most likely to update an AWS managed policy when a new AWS service is launched or new API operations become available for existing services.
For more information, see [AWS managed policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html#aws-managed-policies) in the *IAM User Guide*.
## AWS managed policy: AmazonFISServiceRolePolicy
This policy is attached to the service-linked role named **AWSServiceRoleForFIS** to allow AWS FIS to manage monitoring and resource selection for experiments. For more information, see [Use service-linked roles for AWS Fault Injection Service](using-service-linked-roles.md).
## AWS managed policy: AWSFaultInjectionSimulatorEC2Access
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS actions for Amazon EC2](fis-actions-reference.md#ec2-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorEC2Access](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorEC2Access.html) in the *AWS Managed Policy Reference*.
## AWS managed policy: AWSFaultInjectionSimulatorECSAccess
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS actions for Amazon ECS](fis-actions-reference.md#ecs-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorECSAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorECSAccess.html) in the *AWS Managed Policy Reference*.
## AWS managed policy: AWSFaultInjectionSimulatorEKSAccess
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS actions for Amazon EKS](fis-actions-reference.md#eks-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorEKSAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorEKSAccess.html) in the *AWS Managed Policy Reference*.
## AWS managed policy: AWSFaultInjectionSimulatorNetworkAccess
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS networking actions](fis-actions-reference.md#network-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorNetworkAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorNetworkAccess.html) in the *AWS Managed Policy Reference*.
## AWS managed policy: AWSFaultInjectionSimulatorRDSAccess
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS actions for Amazon RDS](fis-actions-reference.md#rds-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorRDSAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorRDSAccess.html) in the *AWS Managed Policy Reference*.
## AWS managed policy: AWSFaultInjectionSimulatorSSMAccess
Use this policy in an experiment role to grant AWS FIS permission to run experiments that use the [AWS FIS actions for Systems Manager](fis-actions-reference.md#ssm-actions-reference). For more information, see [IAM roles for AWS FIS experiments](getting-started-iam-service-role.md).
To view the permissions for this policy, see [AWSFaultInjectionSimulatorSSMAccess](https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AWSFaultInjectionSimulatorSSMAccess.html) in the *AWS Managed Policy Reference*.
## AWS FIS updates to AWS managed policies
View details about updates to AWS managed policies for AWS FIS since this service began tracking these changes.
| Change | Description | Date |
| --- | --- | --- |
| [AWSFaultInjectionSimulatorEC2Access](#AWSFaultInjectionSimulatorEC2Access) – Update to an existing policy | Added permission required for the "AZ: Application Slowdown" and "Cross-AZ: Traffic Slowdown" scenarios. The permissions are: ec2:DescribeSubnets | November 12, 2025 |
| [AWSFaultInjectionSimulatorECSAccess](#AWSFaultInjectionSimulatorECSAccess) – Update to an existing policy | Added permissions required for the "AZ: Application Slowdown" and "Cross-AZ: Traffic Slowdown" scenarios. The permissions are: ecs:DescribeContainerInstances, ec2:DescribeSubnets and ec2:DescribeInstances | November 12, 2025 |
| [AWSFaultInjectionSimulatorECSAccess](#AWSFaultInjectionSimulatorECSAccess) – Update to an existing policy | Added permissions to allow AWS FIS to resolve ECS targets. | January 25, 2024 |
| [AWSFaultInjectionSimulatorNetworkAccess](#AWSFaultInjectionSimulatorNetworkAccess) – Update to an existing policy | Added permissions to allow AWS FIS to run experiments using the aws:network:route-table-disrupt-cross-region-connectivity and aws:network:transit-gateway-disrupt-cross-region-connectivity actions. | January 25, 2024 |
| [AWSFaultInjectionSimulatorEC2Access](#AWSFaultInjectionSimulatorEC2Access) – Update to an existing policy | Added permissions to allow AWS FIS to resolve EC2 instances. | November 13, 2023 |
| [AWSFaultInjectionSimulatorEKSAccess](#AWSFaultInjectionSimulatorEKSAccess) – Update to an existing policy | Added permissions to allow AWS FIS to resolve EKS targets. | November 13, 2023 |
| [AWSFaultInjectionSimulatorRDSAccess](#AWSFaultInjectionSimulatorRDSAccess) – Update to an existing policy | Added permissions to allow AWS FIS to resolve RDS targets. | November 13, 2023 |
| [AWSFaultInjectionSimulatorEC2Access](#AWSFaultInjectionSimulatorEC2Access) – Update to an existing policy | Added permissions to allow AWS FIS to run SSM documents on EC2 instances and to terminate EC2 instances. | June 2, 2023 |
| [AWSFaultInjectionSimulatorSSMAccess](#AWSFaultInjectionSimulatorSSMAccess) – Update to an existing policy | Added permissions to allow AWS FIS to run SSM documents on EC2 instances. | June 2, 2023 |
| [AWSFaultInjectionSimulatorECSAccess](#AWSFaultInjectionSimulatorECSAccess) – Update to an existing policy | Added permissions to allow AWS FIS to run experiments using the new aws:ecs:task actions. | June 1, 2023 |
| [AWSFaultInjectionSimulatorEKSAccess](#AWSFaultInjectionSimulatorEKSAccess) – Update to an existing policy | Added permissions to allow AWS FIS to run experiments using the new aws:eks:pod actions. | June 1, 2023 |
| [AWSFaultInjectionSimulatorEC2Access](#AWSFaultInjectionSimulatorEC2Access) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS actions for Amazon EC2. | October 26, 2022 |
| [AWSFaultInjectionSimulatorECSAccess](#AWSFaultInjectionSimulatorECSAccess) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS actions for Amazon ECS. | October 26, 2022 |
| [AWSFaultInjectionSimulatorEKSAccess](#AWSFaultInjectionSimulatorEKSAccess) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS actions for Amazon EKS. | October 26, 2022 |
| [AWSFaultInjectionSimulatorNetworkAccess](#AWSFaultInjectionSimulatorNetworkAccess) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS networking actions. | October 26, 2022 |
| [AWSFaultInjectionSimulatorRDSAccess](#AWSFaultInjectionSimulatorRDSAccess) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS actions for Amazon RDS. | October 26, 2022 |
| [AWSFaultInjectionSimulatorSSMAccess](#AWSFaultInjectionSimulatorSSMAccess) – New policy | Added a policy to allow AWS FIS to run an experiment that uses AWS FIS actions for Systems Manager. | October 26, 2022 |
| [AmazonFISServiceRolePolicy](#security-iam-awsmanpol-AmazonFISServiceRolePolicy) – Update to an existing policy | Added permissions to allow AWS FIS to describe subnets. | October 26, 2022 |
| [AmazonFISServiceRolePolicy](#security-iam-awsmanpol-AmazonFISServiceRolePolicy) – Update to an existing policy | Added permissions to allow AWS FIS to describe EKS clusters. | July 7, 2022 |
| [AmazonFISServiceRolePolicy](#security-iam-awsmanpol-AmazonFISServiceRolePolicy) – Update to an existing policy | Added permissions to allow AWS FIS to list and describe the tasks in your clusters. | February 7, 2022 |
| [AmazonFISServiceRolePolicy](#security-iam-awsmanpol-AmazonFISServiceRolePolicy) – Update to an existing policy | Removed the events:ManagedBy condition for the events:DescribeRule action. | January 6, 2022 |
| [AmazonFISServiceRolePolicy](#security-iam-awsmanpol-AmazonFISServiceRolePolicy) – Update to an existing policy | Added permissions to allow AWS FIS to retrieve history for the CloudWatch alarms used in stop conditions. | June 30, 2021 |
| AWS FIS started tracking changes | AWS FIS started tracking changes to its AWS managed policies | March 1, 2021 |
# Infrastructure security in AWS Fault Injection Service
As a managed service, AWS Fault Injection Service is protected by AWS global network security. For information about AWS security services and how AWS protects infrastructure, see [AWS Cloud Security](https://aws.amazon.com/security/). To design your AWS environment using the best practices for infrastructure security, see [Infrastructure Protection](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/infrastructure-protection.html) in *Security Pillar AWS Well‐Architected Framework*.
You use AWS published API calls to access AWS FIS through the network. Clients must support the following:
+ Transport Layer Security (TLS). We require TLS 1.2 and recommend TLS 1.3.
+ Cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes.
# Access AWS FIS using an interface VPC endpoint (AWS PrivateLink)
You can establish a private connection between your VPC and AWS Fault Injection Service by creating an *interface VPC endpoint*. VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that enables you to privately access AWS FIS APIs without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with AWS FIS APIs.
Each interface endpoint is represented by one or more [elastic network interfaces](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html) in your subnets.
For more information, see [Access AWS services through AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html) in the *AWS PrivateLink Guide*.
## Considerations for AWS FIS VPC endpoints
Before you set up an interface VPC endpoint for AWS FIS, review [Access an AWS service using an interface VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html) in the *AWS PrivateLink Guide*.
AWS FIS supports making calls to all of its API actions from your VPC.
## Create an interface VPC endpoint for AWS FIS
You can create a VPC endpoint for the AWS FIS service using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Create a VPC endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the *AWS PrivateLink Guide*.
Create a VPC endpoint for AWS FIS using the following service name: `com.amazonaws.region.fis`.
If you enable private DNS for the endpoint, you can make API requests to AWS FIS using its default DNS name for the Region, for example, `fis.us-east-1.amazonaws.com`.
## Create a VPC endpoint policy for AWS FIS
You can attach an endpoint policy to your VPC endpoint that controls access to AWS FIS. The policy specifies the following information:
+ The principal that can perform actions.
+ The actions that can be performed.
+ The resources on which actions can be performed.
For more information, see [Control access to VPC endpoints using endpoint policies](https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-access.html) in the *AWS PrivateLink Guide*.
**Example: VPC endpoint policy for specific AWS FIS actions**
The following VPC endpoint policy grants access to the listed AWS FIS actions on all resources to all principals.
```
{
"Statement":[
{
"Effect":"Allow",
"Action":[
"fis:ListExperimentTemplates",
"fis:StartExperiment",
"fis:StopExperiment",
"fis:GetExperiment"
],
"Resource":"*",
"Principal":"*"
}
]
}
```
**Example: VPC endpoint policy that denies access from a specific AWS account**
The following VPC endpoint policy denies the specified AWS account access to all actions and resources, but grants all other AWS accounts access to all actions and resources.
```
{
"Statement":[
{
"Effect": "Allow",
"Action": "*",
"Resource": "*",
"Principal": "*"
},
{
"Effect":"Deny",
"Action": "*",
"Resource": "*",
"Principal": {
"AWS": [ "123456789012" ]
}
}
]
}
```