This release of stacker brings the much anticipated multi-region/multi-account support.

Multi-Account Support

You can now specify an AWS profile that a stack should use when provisioning it. This allows you to define different AWS profiles for different AWS accounts, and then "target" stacks to that account. Output lookups work across stacks in different accounts and regions.

To use a specific profile with a stack, you just specify the profile with a new profile option:

stacks:
  - name: vpc
    profile: prod

When provisioning the stack, stacker will perform all AWS operations using the prod profile defined in your AWS config file (~/.aws/config or the AWS_CONFIG_FILE environment variable).

For more information on AWS/boto3 profiles, see the boto3 credentials documentation.

Multi-Region Support

In addition to support for AWS profiles, you can also target a stack to a specific region using the new region option:

stacks:
  - name: vpc-west
    region: us-west-2

See the documentation for more details.

Stack Policies

Stack policies are a feature in CloudFormation that allows you to provide extra protections on resources to prevent accidental updates. You can now manage stack policies directly with stacker, using the new stack_policy_path option.

See the documentation for more details.

Fulle Changes

• Support for provisioning stacks in multiple accounts and regions has been added [GH-553], [GH-551]
• Added a --profile flag, which can be used to set the global default profile that stacker will use (similar to AWS_PROFILE) [GH-563]
• class_path/template_path are no longer required when a stack is locked [GH-557]
• Support for setting stack policies on stacks has been added [GH-570]

For more information about using the new multi-region/account support, and best practices for setting up a shared boto3 profile, you can see the example setup here.