AWS managed policies for AWS RoboMaker - AWS RoboMaker

End of support notice: On September 10, 2025, AWS will discontinue support for AWS RoboMaker. After September 10, 2025, you will no longer be able to access the AWS RoboMaker console or AWS RoboMaker resources. For more information on transitioning to AWS Batch to help run containerized simulations, visit this blog post.

AWS managed policies for AWS RoboMaker

To add permissions to users, groups, and roles, it is easier to use AWS managed policies than to write policies yourself. It takes time and expertise to create IAM customer managed policies that provide your team with only the permissions they need. To get started quickly, you can use our AWS managed policies. These policies cover common use cases and are available in your AWS account. For more information about AWS managed policies, see AWS managed policies in the IAM User Guide.

AWS services maintain and update AWS managed policies. You can't change the permissions in AWS managed policies. Services occasionally add additional permissions to an AWS managed policy to support new features. This type of update affects all identities (users, groups, and roles) where the policy is attached. Services are most likely to update an AWS managed policy when a new feature is launched or when new operations become available. Services do not remove permissions from an AWS managed policy, so policy updates won't break your existing permissions.

Additionally, AWS supports managed policies for job functions that span multiple services. For example, the ReadOnlyAccess AWS managed policy provides read-only access to all AWS services and resources. When a service launches a new feature, AWS adds read-only permissions for new operations and resources. For a list and descriptions of job function policies, see AWS managed policies for job functions in the IAM User Guide.

AWS managed policy: AWSRoboMaker_FullAccess

This policy grants contributor permissions that allows AWS RoboMaker to read images or bundles that you can use to create applications. Additionally, this policy gives you access to all AWS RoboMaker resources and operations. It also creates an IAM role in your account that manages Amazon EC2 resources in your account.

Permissions details

This policy includes the following permissions.

  • s3:GetObject — If you're using a bundle for either your robot or simulation application, it allows AWS RoboMaker to get the zip files from your Amazon S3 bucket.

  • ecr:BatchGetImage — If you're using an image for either your robot or simulation application, it allows AWS RoboMaker to get the image from your Amazon ECR repository.

  • ecr-public:DescribeImages — If you're using a publicly available image for either your robot or simulation application, it allows AWS RoboMaker to get information about that image from the Amazon ECR repository.

  • iam:CreateServiceLinkedRole — Provides AWS RoboMaker with access with the Amazon EC2 resources it needs to operate successfully. For more information, see Using service-linked roles for AWS RoboMaker

{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "robomaker:*", "Resource": "*" }, { "Effect": "Allow", "Action": "s3:GetObject", "Resource": "*", "Condition": { "StringEquals": { "aws:CalledViaFirst": "robomaker.amazonaws.com" } } }, { "Effect": "Allow", "Action": "ecr:BatchGetImage", "Resource": "*", "Condition": { "StringEquals": { "aws:CalledViaFirst": "robomaker.amazonaws.com" } } }, { "Effect": "Allow", "Action": "ecr-public:DescribeImages", "Resource": "*", "Condition": { "StringEquals": { "aws:CalledViaFirst": "robomaker.amazonaws.com" } } }, { "Effect": "Allow", "Action": "iam:CreateServiceLinkedRole", "Resource": "*", "Condition": { "StringEquals": { "iam:AWSServiceName": "robomaker.amazonaws.com" } } } ] }

AWS managed policy: AWSRoboMakerReadOnlyAccess

This managed policy example provides read only access to AWS RoboMaker via the AWS Management Console and SDK.

{ "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [ "robomaker:List*", "robomaker:BatchDescribe*", "robomaker:Describe*", "robomaker:Get*" ], "Resource": "*" } ] }

AWS RoboMaker updates to AWS managed policies

View details about updates to AWS managed policies for AWS RoboMaker since this service began tracking these changes. For automatic alerts about changes to this page, subscribe to the RSS feed on the AWS RoboMaker Document history page.

Change Description Date

AWSRoboMaker_FullAccess – New policy

AWS RoboMaker added a new policy to allow access to resources it needs to successfully run.

This policy gives AWS RoboMaker access to the Amazon ECR images or zip files that you've stored on Amazon S3 to create your robot and simulation applications. It also gives AWS RoboMaker the ability to access the Amazon EC2 it needs to run successfully.

July 27, 2021

AWSRoboMakerReadOnlyAccess – New policy

AWS RoboMaker added a new policy to allow read only access to AWS RoboMaker resources.

January 11, 2022

AWS RoboMaker started tracking changes

AWS RoboMaker started tracking changes for its AWS managed policies.

July 27, 2021