Changelog

Quota checks

Initial setup now checks the cloud quotas a stack needs before it creates anything. A shortfall stops initial setup with the quota, the current usage, and a link to request an increase:

alien render --format cloudformation --stack .alien/build/aws/stack.json --check-quotas

On AWS, the checks cover EC2 vCPUs, VPCs, Elastic IPs, NAT gateways per Availability Zone, and Lambda concurrency. On Google Cloud, regional CPUs, custom IAM roles, and service accounts. On Azure, compute quotas and SKU restrictions in the region.

Before, a missing quota surfaced halfway through provisioning as a cloud error. Now the customer's admin sees it before the first resource exists.

  • IAM limits: generated policies are checked against AWS policy and template size limits
  • Overrides: --quota-warning-override L-1216C47A accepts a known shortfall for one deployment
  • Missing read access: a quota the admin's credentials can't read is reported as a warning
  • Clearer errors: deployment errors say who acts next, your team or the customer's admin

Read the docs →