Environments

An environment groups the components and applications that together form one complete system. Within a single project you can create as many environments as you need.

Structure environments to fit your work

You can shape environments around different use cases. Create a separate environment for each sub-system in a project to isolate parts of your architecture. Or organize them by purpose, such as development, testing, and production, so every stage of your delivery lifecycle is clearly defined.

Deployment lifecycle

Each environment runs its own deployment lifecycle. You control how and when its applications and components deploy, independently of any other environment. That separation lowers risk and lets you test changes thoroughly before they reach production.

Connection to cloud accounts

An environment connects to a specific cloud account, such as AWS, GCP, or Azure. You set this connection when you create the environment. Once the environment is deployed, the cloud account can't be changed, so every resource in the environment stays tied to the cloud provider you chose at the start.

Deploy components and apps

You have two ways to deploy applications within an environment:

• Manual deployment — deploy applications one by one or in bulk, depending on your needs.
• Automated deployment — use pipelines to deploy applications automatically across all your environments.

Next steps

• Connect an AWS account
• Build infrastructure components
• Set up automated deployments