Required Permissions
Breakdown of the cross-account IAM role MilkStraw AI uses and the least-privilege permissions it requires.
Why We Need Permissions
To deliver savings, we analyse your AWS usage and apply commitment-based discounts on your behalf. This is done through a cross-account IAM role that you create in your management / payer account with our CloudFormation template. The role follows the principle of least privilege,we only receive the access strictly necessary to:
- Read cost and usage data.
- Detect optimisation opportunities.
- Manage the lifecycle of our .
Below is a breakdown of the permissions granted to that role.
Monitoring and Data Collection (Read-Only)
These permissions let MilkStraw AI monitor your spend and resources without touching your workloads.
Cost Management
Compute & Databases
Integration Management
These actions are required to integrate MilkBox accounts into your AWS Organization.
organizations:InviteAccountToOrganization
is used solely to invite MilkBox accounts.
EC2 Reservation Management
We manage the lifecycle of Savings Plans and Reserved Instances on the MilkBox accounts that cover your usage.
Other Essential Operations
Budgets
Support
Service Quotas
Review the Full Policy
You can always inspect the exact IAM policy generated by our CloudFormation stack:
Feel free to reach out if you have any questions about security or least-privilege access.