How do I review the IAM permissions a vendor’s installer asks for?
Read this page as JSON or Markdown.
Separate bootstrap from day-to-day access
An installer may create resources and identities that the running application should not be allowed to create. Review both policies and record when elevated bootstrap access is removed. Broad permissions need a resource-by-resource explanation; some service APIs require wildcard resources, so review their effect rather than rejecting a character in isolation.
Review a vendor-assumed role
For a multi-tenant vendor assuming AWS roles, verify the trust relationship and the vendor’s external-ID mechanism against AWS guidance. An external ID addresses a confused-deputy risk; it is not a substitute for limiting permissions or checking the trusted principal.
Use a separate identity for routine operations and another process for support access. Define logging, approval, session limits where supported and revocation. In a trial, verify what fails when access is removed and how your team regains control without relying on the vendor’s identity.
Sources and further guidance
Answer reviewed 2026-11-21. Check the exact edition, configuration and current vendor terms before deciding.