Environments FAQ

What is an Environment?

Environments are regional, thus they are restricted to a single AWS region. Environments are a way to securely group deployments and configure the same network access rules for them with (IP Whitelist and VPC peering). Additionally, you can configure which member has access to Environments and their databases. Selecting an environment color (type) is a way to categorize the different categories of environments.

How many Environment colors are there/Envirnoment types?

There are 5 different Environment colors. Selecting an environment color (type) is a way to categorize the different categories of environments you have, eg. staging, production, etc. You can choose the Environment Type by assigning a color to it, and you can provide access to that specific Environment to members of your Organization.

How can I create an Environment?

Environments can be created within an Organization. Select the Organization from the drop-down menu in which you want to create a new Environment, go to Environments tab and click on the +Add new Environment button. More details on how to create an Environment can be found here.

How many Environments can I create?

There is a limit of 1 Environment in the Standard (free) Subscription and a limit of 3 Environments in the Gold ($50/month) Subscription. More details on Subscription plans can be found here.

Can I modify Network Access rules?

Yes. In the Network Access section you can configure the VPC peering and IP Whitelist for your deployments within respective Environments. Detailed information on this topic can be found in this article.

Which AWS regions do you support?