AWS RoboMaker and interface VPC endpoints (AWS PrivateLink)

You can establish a private connection between your VPC and AWS RoboMaker by creating an interface VPC endpoint. Interface endpoints are powered by AWS PrivateLink, a technology that enables you to privately access AWS RoboMaker 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 RoboMaker APIs. Traffic between your VPC and AWS RoboMaker 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 RoboMaker VPC endpoints

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

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

Creating an interface VPC endpoint for AWS RoboMaker

You can create a VPC endpoint for the AWS RoboMaker 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 RoboMaker using the following service name:

• com.amazonaws.region.robomaker

If you enable private DNS for the endpoint, you can make API requests to AWS RoboMaker using its default DNS name for the Region, for example, robomaker.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 RoboMaker

You can attach an endpoint policy to your VPC endpoint that controls access to AWS RoboMaker. 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 AWS RoboMaker actions

The following is an example of an endpoint policy for AWS RoboMaker. When attached to an endpoint, this policy grants access to the listed AWS RoboMaker actions for all principals on all resources.

{
   "Statement":[
      {
         "Principal":"*",
         "Effect":"Allow",
         "Action":[
            "robomaker:ListSimulationJobs",
            "robomaker:ListSimulationJobBatches"
         ],
         "Resource":"*"
      }
   ]
}