Amazon IAM
Amazon Identity and Access Management (IAM) enables you to manage access to AWS services and resources securely. Using IAM, you can create and manage AWS users, groups, roles, and policies, and use permissions to allow and deny their access to AWS resources. IAM is a feature of your AWS account offered at no additional charge.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Amazon IAM the way a machine reads it — 89 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon IAM scores 69.3/100 (strong), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon IAM
Each block below is one kind of artifact we hold for Amazon IAM. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon IAM Access Keys API
Operations for managing IAM access keys
Amazon IAM Groups API
Operations for managing IAM groups
Amazon IAM Policies API
Operations for managing IAM policies
Amazon IAM Roles API
Operations for managing IAM roles
Amazon IAM Users API
Operations for managing IAM users
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Amazon IAM API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Amazon Iam Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Amazon Iam Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
User Management
Create, manage, and delete IAM users with fine-grained permissions.
Role-Based Access Control
Define IAM roles that can be assumed by users, services, or applications.
Policy Management
Create and attach identity-based and resource-based policies to control access.
Multi-Factor Authentication
Enable MFA for IAM users to add an extra layer of security.
Access Key Management
Programmatically manage AWS access keys for long-term credentials.
Permission Boundaries
Use permission boundaries to define the maximum permissions an entity can have.
Service Control Policies
Centrally control the maximum available permissions across AWS accounts.
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Iam Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon IAM API Rules
SPECTRALAmazon IAM API Rules
SPECTRALJSON Schema 20
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessKey
JSON SCHEMACreateAccessKeyResponse
JSON SCHEMACreateGroupResponse
JSON SCHEMACreatePolicyResponse
JSON SCHEMACreateRoleResponse
JSON SCHEMACreateUserResponse
JSON SCHEMAGetGroupResponse
JSON SCHEMAGetPolicyResponse
JSON SCHEMAGetRoleResponse
JSON SCHEMAGetUserResponse
JSON SCHEMAGroup
JSON SCHEMAListAccessKeysResponse
JSON SCHEMAListGroupsResponse
JSON SCHEMAListPoliciesResponse
JSON SCHEMAListRolesResponse
JSON SCHEMAListUsersResponse
JSON SCHEMAPolicy
JSON SCHEMARole
JSON SCHEMATag
JSON SCHEMAAWS IAM User
JSON SCHEMAScroll within the panel for all 20 ·
JSON Structure 20
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Iam Access Key Structure
JSON STRUCTUREAmazon Iam Create Access Key Response Structure
JSON STRUCTUREAmazon Iam Create Group Response Structure
JSON STRUCTUREAmazon Iam Create Policy Response Structure
JSON STRUCTUREAmazon Iam Create Role Response Structure
JSON STRUCTUREAmazon Iam Create User Response Structure
JSON STRUCTUREAmazon Iam Get Group Response Structure
JSON STRUCTUREAmazon Iam Get Policy Response Structure
JSON STRUCTUREAmazon Iam Get Role Response Structure
JSON STRUCTUREAmazon Iam Get User Response Structure
JSON STRUCTUREAmazon Iam Group Structure
JSON STRUCTUREAmazon Iam List Access Keys Response Structure
JSON STRUCTUREAmazon Iam List Groups Response Structure
JSON STRUCTUREAmazon Iam List Policies Response Structure
JSON STRUCTUREAmazon Iam List Roles Response Structure
JSON STRUCTUREAmazon Iam List Users Response Structure
JSON STRUCTUREAmazon Iam Policy Structure
JSON STRUCTUREAmazon Iam Role Structure
JSON STRUCTUREAmazon Iam Tag Structure
JSON STRUCTUREAmazon Iam User Structure
JSON STRUCTUREScroll within the panel for all 20 ·
Examples 20
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Iam Group Example
EXAMPLEAmazon Iam Policy Example
EXAMPLEAmazon Iam Role Example
EXAMPLEAmazon Iam Tag Example
EXAMPLEAmazon Iam User Example
EXAMPLEScroll within the panel for all 20 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Least Privilege Access
Grant only the permissions required for specific tasks to reduce the attack surface.
Cross-Account Access
Enable users in one AWS account to assume roles in another account.
Service-to-Service Authorization
Allow AWS services to access other services on your behalf through service roles.
Temporary Credentials
Use STS to issue temporary security credentials for short-lived access.
Security Compliance
Audit IAM configurations to ensure compliance with security policies and regulations.
Resources
Every other property we hold for Amazon IAM — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/amazon-iam · machine-readable index on apis.io