Skip to content

docs: clarify AWS connection retry window #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify AWS connection retry window #384

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions cloud-accounts/connecting-a-cloud-account.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,12 @@ Before Porter can create a cluster, you need to grant it access to your cloud ac
The IAM role must remain in your AWS account for Porter to manage your infrastructure. Deleting it will prevent Porter from making changes.
</Info>

## Finishing the connection later

Porter starts polling for the new IAM role as soon as you click **Grant Permissions**, so the connection usually completes within a few minutes of the CloudFormation stack reaching `CREATE_COMPLETE`.

If you step away before applying the stack, you do not need to restart the flow. Porter keeps retrying the connection in the background for up to 7 days after the account was created. Apply the CloudFormation stack any time within that window and Porter will detect the role on its next sweep and mark the account connected. If 7 days pass without the stack being applied, reopen the connect flow in Porter to start over.

## Permissions Granted

The CloudFormation stack creates an IAM role with permissions to:
Expand Down