Getting started
Guides and examples
Reference documentation
Background concepts
Frequently Asked Questions
Integrations
Cloud Integrations (AWS)
Release integrates with your favorite cloud provider(s)! This is the first step in building out a self-hosted cluster in the cloud provider account of your choice.
Create an Integration
First, navigate to the Account Settings screen by clicking the Account Settings icon in the upper right corner of the window.
On the Account Settings screen, select the Clusters tab and click the green button to create a new Cloud Provider Integration:
Create a new cloud provider integration
1) Select a cloud integration provider, 2) type a name for your integration, and 3) click save:
Select a cloud provider, enter a name, and save your results.
For Amazon Web Services (AWS) Integrations
While on the Account Settings screen, navigate to the Integrations tab and find the AWS integration. Click the orange "Launch Stack" button:
Launch a new AWS Cloudformation Stack
In another tab or popup, you will be prompted to authenticate to the AWS account you wish to use.
We recommend you use AWS Organizations to create a sub-account to deploy your AWS resources into. This ensures a safe boundary between Release clusters and infrastructure and any other application infrastructure you may be testing or using, especially in development or test environments. This may align with your company policies on auditing, billing, and business units. Using an isolated sub account can also prevent any unintended consequences in your production or mission-critical accounts. Feel free to ask us any questions or concerns you may have about account permissions and boundaries.
Many customers deploy Release clusters into their production accounts to run their production workloads. The above recommendation for using an isolated sub account still applies if this is your first time integrating with Release. We recommend a "crawl-walk-run" iterative approach when approaching large problems.
Please make sure you use the correct account where Release will deploy your cluster (for example, preproduction clusters should be created in your "development" or "staging" AWS account, not in your "production" account).
Create the Cloudformation Stack by agreeing to the terms and saving
Most users will not change or alter the parameters. In particular, the AccountID, ExternalID, and Integration URL are set by Release and should not be edited. The Permissions Boundary ARN is explained in How to Use the Permissions Boundary to Restrict Release Access. You should not add a Permissions Boundary unless you have talked with Release first to verify the permissions restrictions will not break anything. If this is your first time running the AWS integration, you should not add a permissions boundary until after your cluster(s) have been created.
Agree to the terms of conditions and create the CloudFormation stack. In less than 2 or 3 minutes, you should see the CloudFormation stack has been created without errors (you may need to hit the "reload" circle icon a few times to get updates).
A successful cloudformation integration run finished
Last modified 2mo ago
Copy link