Execution role
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
An IAM role that a function or agent runtime assumes when it runs. The role's policies decide which AWS APIs the code can call, and the service assumes the role automatically on each invocation, so the code holds no long-lived key.
An example, sourced
AWS documents the Lambda execution role as the role that Lambda automatically assumes when you invoke your function. The page, titled as defining function permissions with an execution role, also covers creating the role in the IAM console and granting least privilege access to it. AWS documents that when you create a function in the Lambda console, Lambda creates an execution role with minimal permissions, covering basic logging to CloudWatch Logs. Anything the function code does beyond that depends on policies someone attached.
Why it matters here
For a function-based or AgentCore agent, the execution role is the agent's whole reach into AWS. Reading its attached policies is the first step of a review, and a role created by a console wizard still needs reading. A role created by a wizard may also have been widened since.
Related pages
Sources
Last reviewed 16 Nov 2026.