Skip to main content
Gapstack provisions infrastructure in your AWS account. Connecting an account creates a CloudFormation stack that grants Gapstack permission to do that. You own the account and can revoke access at any time.
You must have AdministratorAccess (recommended) or be the root user (not recommended) to create the stack.
1

Open Connect a new account

In Gapstack, click Connect a new account. You can also open Organization settings and add the account from there.
2

Name the account

Enter an Account name you will recognize, such as Prod or Dev.Select I have Administrator Access if you already have an AWS account. Select Create new AWS Account only if you need to create one.

Name the AWS account, then open the authorization page.

3

Open the AWS authorization page

Confirm you are signed in to the correct AWS account in the browser. Click Open AWS Authorization Page. AWS opens the CloudFormation Quick create stack page in a new tab.Gapstack fills the stack name and parameters for you. Leave them unchanged. Do not edit GapstackAwsAccountId or GapstackTenantId. Those values link the stack to your organization and AWS account.
Do not change the CloudFormation template, stack name, parameters, or region. The connection stack must be created in us-west-1. You can still deploy environments to any supported region.

Leave the stack name and parameters exactly as Gapstack filled them.

4

Accept the stack and create it

Scroll to Capabilities. Do not change any parameters on the way.
  1. Select I acknowledge that AWS CloudFormation might create IAM resources with custom names.
  2. Click Create stack.
5

Confirm the account is Connected

Stack creation takes a few minutes. When it finishes, open Organization settings.Refresh the page. The account status should show Connected.
The AWS account appears in Organization settings with a Connected status.
Connecting an account is free. AWS charges begin when you create environments and provision resources in that account. To show those charges in Gapstack, see View AWS costs. Leave cost analytics off until you need it.