Working with environments - Amazon CodeCatalyst

Working with environments

An environment, not to be confused with a Dev Environment, is where code is deployed to. It usually contains an instance of a running application along with its associated infrastructure. You can give your environment a name such as development, test, staging, or production. Any deployments generated by CodeCatalyst to an environment will appear on the Environments page. To set up an environment, you give it a name, such as my-production-environment, and then associate it with your AWS account.

In addition to displaying deployment information, an environment also serves as the mechanism through which to assign AWS IAM roles to workflow actions.

Can multiple environments exist within a single workflow?

Yes. If a workflow includes multiple actions, each of those actions can be assigned an environment. For example, you could have a workflow that includes two deploy actions, where one is assigned a my-staging-enviroment environment and another is assigned a my-production-environment environment.

Which actions support environments?

The following actions support having their deployment information displayed on the Environments page:

Note

If you want to allow an action to access and perform operations in your AWS account, you'll need to associate it with an environment. Many actions support an environment association, including, but not limited to, the actions listed previously. You can tell which actions support an environment association because they'll include an Environment drop-down list on their Configuration tab in the visual editor.

Supported Regions

The Environments page can display resources in any AWS Region.

Are environments mandatory?

An environment is mandatory if the workflow action to which it is assigned deploys resources into the AWS cloud, or communicates with AWS services for other reasons (such as monitoring and reporting).