AWS Roles and Bedrock
A MicroVM runs as its workspace's AWS role, chosen in the AWS role section. AWS keeps its credentials fresh, and every process in the MicroVM can use them; none are written to files. Only roles that Lambda can use are listed, or choose Paste an ARN….
New Role…
New Role… opens New AWS Role. The name starts with MicroVMStudio-. Add what the role may do:
- Amazon Bedrock (for Claude Code): calling Claude models on Bedrock.
- Read-only access to this account: the AWS managed policy ReadOnlyAccess, which can also read data such as S3 objects.
- Your own policy: JSON with a
Statement.
Every role can write the MicroVM's logs to CloudWatch. The sheet shows the exact trust policy, permissions and tags before Create Role. A new role can take a minute to work; launching waits and tries again.
If a role with that name was made by MicroVM Studio, Create Role updates it to match the sheet. If someone else's role has the name, choose another. MicroVM Studio doesn't edit or delete roles afterwards: use the IAM console.
Create a Role for Bedrock…
When Claude Code uses Amazon Bedrock and no role is chosen, the Claude Code section offers Create a Role for Bedrock…: the same sheet, with Bedrock already ticked.
Your own permissions
Making roles needs IAM permissions of your own: the permission check calls them Use and create IAM roles. A persistent /workspace needs a role of the workspace's own; see Persistent /workspace.