AWS Fault Injection Simulator and interface VPC endpoints (AWS PrivateLink) - AWS Fault Injection Simulator

AWS Fault Injection Simulator and interface VPC endpoints (AWS PrivateLink)

You can establish a private connection between your VPC and AWS Fault Injection Simulator by creating an interface VPC endpoint. Interface endpoints are powered by AWS 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. Traffic between your VPC and AWS FIS does not leave the Amazon network.

Each interface endpoint is represented by one or more elastic network interfaces in your subnets.

For more information, see Interface VPC endpoints (AWS PrivateLink) in the AWS PrivateLink Guide.

Considerations for AWS FIS VPC endpoints

Before you set up an interface VPC endpoint for AWS FIS, ensure that you review Interface endpoint properties and limitations in the AWS PrivateLink Guide.

AWS FIS supports making calls to all of its API actions from your VPC.

Creating 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 Creating an interface endpoint 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.

For more information, see Accessing a service through an interface endpoint in the AWS PrivateLink Guide.

Creating 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 Controlling access to services with VPC endpoints 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" ] } } ] }