Environments

Overview

Environments group Resources and Services inside a private network (VPC) on either GCP or AWS. You can create multiple environments for different stages of your workflow (e.g. development, staging, production) and switch between them with a single command.

Environment Types

Environments can be created in two tiers: development and production. The tier of environment you create determines how your resources are auto configured.

Development Environments

Development environments are used for testing and development. They auto configure your resources to be more cost-effective and manage firewall rules to let you connect to your resources from your local machine.

Production Environments

Production environments are used for running your application in a secure and scalable way. They auto configure your resources for high availability and security, and ensure no connections are allowed from the public internet. Production environments are SOC 2 compliant by default.

Permissions & Roles

Permissions & roles are managed for you, so you can easily create / connect to infrastructure across multiple environments without compromising security. Services can access any resource in the same environment, but cannot access resources in other environments. Resource clients automatically configure their connection settings based on the environment your code is running in.

CLI Commands

For a full list of commands and options, see the Environments Reference.

Create an Environment

1
lf environments create [ENVIRONMENT_NAME]
content_copy

If this command fails for any reason you can re-run it with the same arguments to retrying creating the environment.

Listing Environments

1
lf environments list
content_copy

Delete an Environment

1
lf environments delete [ENVIRONMENT_NAME]
content_copy