Environment Create a Environment from UI

Create an Environment using the Axio web interface. An Environment belongs to a Workspace and serves as a deployment target for infrastructure stacks.

Info

Prerequisite

Ensure that you have permission to create Environments and that a Workspace already exists.

Step-by-Step Guide

1

Login to Axio

Sign in to the Axio platform using your credentials.

2

Go to Environments

Navigate to:

Organization → Environments

3

Click Create Environment

Click the Create Environment button.

4

Fill in Environment Details

Provide the required information:

  • Name (Unique identifier)
  • Display Name
  • Workspace
  • Description (Optional)
5

Review and Confirm

Verify all the entered information and click Create.

6

Environment Created

The Environment will appear under the selected Workspace and is ready for deploying infrastructure stacks.

Create Environment

👥

Environment Owners

Assign users or groups as owners of an Environment. Owners can run workflows in the Environment and approve deployments when required.

KEY POINTS
▶

Environment Owners can run workflows within the Environment.

✓

Environment Owners can approve deployments when approval is required.

👥

Assign one or more users or groups as Environment Owners.

ⓘ

At least one user or group must be assigned as an Environment Owner.

🛡

Skip self-approval for workflows

Controls whether the user who triggered a workflow can approve its deployment.

🔒

If enabled

The workflow initiator cannot approve their own deployment. Another Environment Owner must review and approve.

♙

If disabled

Self-approval is allowed. However, at least one user or group must be assigned as an Environment Owner.

ⓘ

This setting helps maintain secure and compliant deployment practices.

Tip

Discover Runs

Environments provide access to Discover Runs, which shows the history of PR-driven stack discovery activity. It helps you track provisioned stacks, plans, PR-close destroy actions, discovery status, and related details.

What Happens Next?

After creating the Environment:

  • The Environment becomes available under the selected Workspace.
  • Deploy one or more Infrastructure Stacks in the Environment.
  • Sensitive Environments block destroy deployments for linked stacks.
  • Sensitive Environments cannot be deleted or archived.
  • An Environment can be unassigned from its Workspace and moved to the default workspace.
  • Environments can be archived when eligible.