Skip to content
Richard Hurt edited this page Jul 30, 2017 · 2 revisions

Each environment (Prod, QA, Test, Dev, account, etc.) needs it's own environment file. The simplest file just contains the name of the environment, it's version, and what regions its valid for.

Example

{
  "EnvName" : "Account",
  "EnvVersion" : "a",

  "EnvRegions" : [
    {
      "Id" : "us-east-1",
      "Name" : "USEast1"
    },
    {
      "Id" : "us-west-2",
      "Name" : "USWest2"
    }
  ]
}

Usage

EnvName

This is the name of the environment (Prod, Dev, QA, Account, etc.) and is used to determine how to process a stack blueprint.

EnvVersion

Each blueprint can have different versions. Since CloudFormation doesn't allow you to rename an existing stack, this attribute allows you to transition to new stacks if/when your needs change and you have to rebuild things.

Regions

For every region in this array, cfn-builder will create a template.

Clone this wiki locally