At GrapheneDB all databases are deployed into Environments. Environments are regional, which means that they are locked to one AWS region. Environments provide a way to group databases and configure the same Network Access rules (IP Whitelist and VPC peering), as well as configure access to a group of members of the Organization.
You can manage Member access to Databases deployed into Environments by choosing the Environment type.
- Please make sure you configure Network rules after creating the Environment.
- Region and Address Range cannot be changed after creation. Please make sure to choose them carefully.
Environment types are 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 Operators of your Organization.
Environments will be displayed to all Operators with access to the specific type. Meaning that the Operators will be able to have access to the Deployments, Network Access and Settings for the specific Environment Type (color).
We support most AWS regions. If you don’t find the AWS region in the list it might be probably new and we’re working on adding it. Feel free to reach out to our support team to ask about the progress on it.
If you’re not sure about this setting, you can leave it at the default value. The following Address Ranges are not allowed:
Ranges not allowed are:
Bad options are:
172.16.0.0/16 - heavily used
172.17.0.0/16 - Docker’s default
- There is a limit of 1 Environment per Organization with Standard (Free) Subscription plan.
- There is a limit of 3 Environments per Organization with Gold ($50/month) Subscription plan.
Please check out more info on Subscription plans here.
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.
You’ll be prompted to the next section where you will need to enter the Environment name, Type, Region, and IP address range. Once you set all the required fields, please click on Confirm button.
When naming the Environment these conditions must be met:
- At least two characters long.
- At most thirty characters long.
- Can only contain alphabetical characters, numbers, underscore or dashes.
In the Network Access section you can configure the VPC peering and IP Whitelist for your deployments within respective Environment. Navigate to the Organization your Environment is placed within, and choose the desired Environment from the list of created Environments. Then, click on Network Access tab and configure the IP Whitelist and/or VPC peering.
In the Environment Settings section, you can change the name of the Environment, and change the Environment Type. Please note that AWS region and IP address range cannot be changed.
You can also delete the Environment by clicking on the Delete Environment button. Please take into account that all deployments within the Environments need to be terminated, otherwise you won’t be able to delete the Environment.
If you select the delete button, a modal window will appear as a confirmation that you’re about to delete the selected Environment. You will need to enter the name of your Environment to be able to delete it.
All deployments inside the Environment must be deleted before the Environment can be deleted. Only the Owner and Admin can delete the Environment.
To delete an Environment, after ensuring that all deployments are deleted, please navigate to the Environments tab of your Organization, where you’ll be able to see a list of your Environments (unless there’s only one if you’re on a Standard Subscription plan). Next, click on the trashcan icon on the right-hand side next to the Environment you want to delete.
A modal window will appear as a confirmation that you’re about to delete the selected Environment. You will need to enter the name of your Environment to be able to delete it. Click on the Delete Environment button.
The operation will delete the Environment and all the associated configuration, like network access rules.
In this section, you’ll be able to see the last activities of your Environment. Navigate to the Environment view > Activity (as shown in the screenshot below). You can check the activity for all users or only a specific user, as well as sort it by Category for more specific visibility of activities.
Activities are going to be marked for expiration after 1 month.