OpsCanary
awsiamPractitioner

Mastering AWS Transform Custom: Limit Agent Permissions and Spend

5 min read AWS DevOps BlogOct 20, 2026Reviewed for accuracy
Share
Practitioner — Hands-on experience recommended

In the world of cloud computing, managing permissions and costs is crucial. AWS Transform Custom addresses these concerns by allowing you to limit what your agents can do and how much they can spend. This is particularly important in production environments where unmonitored actions can lead to runaway costs and security vulnerabilities.

The AWS Transform CLI runs transformations either interactively or in a pipeline. Before executing any command, it checks a trust settings file in your home directory. If the command is on the allowlist, it runs without prompting you. If not, you receive an approval prompt. Additionally, the execution identity restricts the agent's capabilities, ensuring it only performs actions you deem safe. Each run is capped by agent minutes, stopping execution once the limit is reached, which helps control costs effectively.

To use AWS Transform Custom effectively, ensure you have the necessary prerequisites, including an AWS account and the AWS Transform CLI installed. Be aware that restricted networks must allow access to specific AWS endpoints. The current version, 3.10.0, includes enhancements that improve performance and security. Always test your configurations in a controlled environment before deploying them in production to avoid unexpected issues.

Key takeaways

  • →Implement a trust allowlist to control agent actions without prompts.
  • →Set an execution identity to limit the agent's service requests.
  • →Cap agent minutes to prevent runaway costs during transformations.

Why it matters

In production, limiting agent permissions and spend can prevent costly mistakes and enhance security. Proper configurations can save your organization significant resources while maintaining operational efficiency.

Code examples

Bash
curl -fsSL https://transform-cli.awsstatic.com/install.sh | bash
Bash
atx --version

When NOT to use this

The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →
DigitalOceanSponsor

Simple, affordable cloud — VMs, Kubernetes, and managed databases in minutes. Trusted by 600,000+ developers. Spin up a Droplet in 60 seconds.

Try DigitalOcean →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.