Identity and Access Management decides who may call what in your organization. Every request, from the console, the API, the CLI, a registry login or a git push, is answered by evaluating the caller's policies against one action and one resource name. People sign in with a password, a second factor or your company's single sign-on; programs use access keys or exchange an OIDC token for short-lived credentials.
Identity and Access Management decides who may do what in your organization, for every request from the console, the API, the CLI and the other ways in.
Create a group with read-only compute access, put a new IAM user in it, check what the user may do, and clean up.
Members, IAM users, groups and roles, and how the policies attached to them add up to what a principal may do.
Invite a colleague by email address, with a preset role or a group or role of your own, and follow up on invitations nobody has accepted.
Write a customer-managed policy, in the console's builder or as JSON, before you attach it to anyone.
Let a person, group or role do named things with one repository, app, database, hosted zone or secret, without writing a policy.
Create a credential that acts as an IAM user outside the browser, for the API, the CLI, Terraform, the container registry, git over HTTPS and S3 clients.
The IAM actions, which of them amount to administrator rights, what is recorded, and how credentials are kept.
Where to see who did what, which requests were refused, and the sign-in alerts people receive.
What the platform checks on every request, in which order, what a refusal looks like and what is recorded.
User Guide
48 pages: concepts, tasks, security, quotas, troubleshooting.
API Reference
104 operations, with their parameters and IAM actions.
CLI Command Reference
104 commands, one per API operation, with their arguments and flags.
Terraform resources
19 resources and data sources of the provider.
Document history
What changed in these docs.