The Following is a detailed breakdown of the additional Least-Privileged IAM credential required to enable the Production deployment of our AWS Platform Integration. This will enable all the features of our full automation platform and will be able to receive all updates for new services.

Like our trial credential these additional "write" permissions do not allow us to read anything beyond the bare minimum usage and cost metadata. They additionally allows you to automate all commitment management tasks (purchase, exchange, resell, renewal etc.) without having any ability to access or impact any underlying infrastructure in your AWS accounts.

The three main technical differences between the production credential and the permissions detailed on our documentation on the trial credential is:

1. The wildecard (*) added to the requested list, read & describe permissions to ensure Archera is robust to new metadata endpoints being added without requiring you to manually update the role.

2. The following block of "write" permissions allowing Archera to automate the purchase as well as management of commitments, which are non-infrastructure/application impacting financial discounts, on your behalf. This includes the lifecycle management of EC2 GRIs, with marketplace listing & resale.


3. The following (optional) block of "write" permissions allowing Archera to automate the AWS billing organization management of sub-accounts containing only commitments to handle the lifecycle management of Non-EC2 GRIs in non infrastructure/application impacting manner


Did this answer your question?