Files
spinifex/docs/coverage/sts/README.md
T
Julian Sommer e2fb37c0ac docs: publish only the AWS operations Spinifex serves
The coverage pages led with a percentage and an "x of y" count, and every
table listed the modelled operations Spinifex does not implement, which reads
as a scorecard against AWS rather than a statement of what the platform serves.

A published page now opens with the operation count alone, tables the
operations the gateway serves, and carries a separate not-applicable table with
each reason inline instead of footnotes. The unimplemented operations and the
counts move to docs/coverage/internal-report.md, which no docs-site slug points
at. A service with no implemented operations has no publishable page.
2026-09-15 10:28:35 +10:00

1.6 KiB

title, seoTitle, description, category, sections, tags
title seoTitle description category sections tags
STS API Coverage AWS Security Token Service API Coverage — Spinifex Docs The AWS STS API operations Spinifex implements, covering role assumption, session tokens and web identity federation (IRSA), with those it does not offer. Coverage
overview
aws
compatibility
coverage
sts
identity
credentials

STS API Coverage

Overview

Spinifex implements 5 operations in the STS 2011-06-15 API model.

Trust policies

Trust policies are validated at write time rather than silently narrowed at assume time. NotPrincipal, NotAction, empty-string Action elements and empty Principal blocks are all rejected as malformed.

Condition blocks are rejected except on AssumeRoleWithWebIdentity with StringEquals, which is the shape IRSA needs and which Spinifex evaluates at assume time against the token's issuer, subject and audience. Anything wider is refused rather than accepted and ignored, because an accepted-but-unevaluated condition is a silent over-grant.

Parameters that are refused, not ignored

Several inputs the model describes are deliberately rejected rather than accepted as no-ops: inline session policies and policy ARNs, session tags, and MFA serial numbers and token codes. Each of them would otherwise appear to restrict or strengthen a session that in fact carries the role's full permissions.

Operations

Operation
AssumeRole
AssumeRoleWithWebIdentity
GetAccessKeyInfo
GetCallerIdentity
GetSessionToken