Docs
Security & access

Flexible commitments permissions

What the optional Flexible Commitments stacks create, who can assume them, and what each role is allowed to do.

Flexible commitments are an optional level. Turning the level on deploys a separate CloudFormation stack. Nothing in the Wring Base stack changes.

There are two stacks, one role each. Write access is only needed to book, so you can evaluate the recommendations with the read stack alone:

StackIAM roleInstalled whenGrants
ReadReservedAI-ReadYou turn on Flexible commitments to see recommendationsCost, usage, commitment and inventory data for the recommendations
WriteReservedAI-WriteYou are ready to book — at your first booking, or right away if you already know you willEverything the read role can read, plus purchasing and managing commitments

Both stacks go into the management (payer) account only, and each contains exactly one resource: the IAM role with one inline policy. IAM is global, so the Region you launch them in does not matter.

The trust relationship

Each role can be assumed only by the designated AWS principal of our insurance partner Archera, and only with your per-customer external ID — the same confused-deputy protection the Wring role uses.

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Principal": { "AWS": "{PARTNER_PRINCIPAL_ARN}" },
    "Action": "sts:AssumeRole",
    "Condition": {
      "StringEquals": { "sts:ExternalId": "{YOUR_EXTERNAL_ID}" }
    }
  }]
}
MechanismHow it works
Designated principalOnly the partner's designated AWS principal is trusted — a dedicated principal for the write role
External IDRequired on every assume-role call; prevents confused-deputy attacks
Short-lived credentialsSTS sessions only — the stacks create no users, passwords or access keys
Audit trailEvery role assumption and API call appears in your CloudTrail
Revocable by youDeleting the stack removes the role and all access through it

Read role: ReservedAI-Read

Enough to compute recommendations from your real usage. It cannot buy, modify or delete anything you already run.

AreaAccess
Cost and pricingRead Cost Explorer, AWS pricing and Compute Optimizer data
CommitmentsRead existing Savings Plans, Reserved Instances, Capacity Reservations and the offerings available to you
InventoryDescribe EC2 instances, volumes and Spot usage; read tags, resource groups, service quotas and your organization structure
Report setupCreate its own report buckets (reserved-ai-cur-*, reserved-ai-spot-*), a reserved-ai-* Cost & Usage Report definition and the EC2 Spot data feed — and read objects only from those buckets
Self-checkRead its own role and policy (ReservedAI* only)

Write role: ReservedAI-Write

Only installed once you decide to book. It is a broader role, because buying and managing commitments across a whole organization touches more of AWS than reading cost data does.

AreaAccess
CommitmentsPurchase, modify and exchange Savings Plans, Reserved Instances (EC2, RDS, ElastiCache, MemoryDB, Redshift, OpenSearch) and Dedicated Host reservations; manage Capacity Reservations
OrganizationCreate, invite, move and remove accounts in your AWS Organization
Billing and supportCost Explorer, Budgets, AWS Support and Trusted Advisor; read and update billing preferences; read invoices; request service quota increases
Read accessDescribe and list access across common AWS services (compute, databases, containers, networking, analytics) and CloudWatch metrics — resource configuration and inventory
Report setup and self-checkThe same reserved-ai-* buckets, report definition and self-check as the read role; can create service-linked roles for Service Quotas, ElastiCache and MemoryDB

What the write role does not have: no Secrets Manager or Parameter Store access, no reads of database items or log events, no reads of your S3 objects outside its own reserved-ai-* buckets, and no instance access (SSH, SSM sessions, remote commands).

Safeguards around the write role

  • Purchases start in Wring. A commitment is bought only after an account owner books it in Wring, with the exact monthly amount on screen — the write role is how that booking is executed, not a standing licence to buy.
  • No double purchases. Each booking is idempotent and re-validates the plan right before purchase; if the plan changed, the booking stops.
  • Separate from Wring Base. Deleting the Flexible Commitments stacks ends the access and leaves the Wring Base stack untouched — and the reverse. Talk to us before removing them while commitments are active, so they can be wound down in an orderly way.

Reviewing the templates

The CloudFormation console shows the complete template — every action, word for word — before you launch either stack. Want it earlier, or a walkthrough with your security team? Ask [email protected].

On this page