docs: document cloud permission errors on env group create#294
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document cloud permission errors on env group create#294mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
GKestenberg
reviewed
May 28, 2026
|
|
||
| - **AWS** — `secretsmanager:CreateSecret`, `secretsmanager:PutSecretValue`, `secretsmanager:GetSecretValue`, `secretsmanager:UpdateSecret`, and `sts:AssumeRole` for the Porter role. | ||
| - **GCP** — `secretmanager.secrets.create`, `secretmanager.versions.add`, and `secretmanager.versions.access` on the project. | ||
| - **Azure** — `Key Vault Secrets Officer` (or equivalent get/set permissions) on the Key Vault used by the connected cloud account. |
Contributor
There was a problem hiding this comment.
You should use <Tabs>
<Tabs>
<Tab title="AWS">
- `secretsmanager:CreateSecret`
- `secretsmanager:PutSecretValue`
- `secretsmanager:GetSecretValue`
- `secretsmanager:UpdateSecret`
- `sts:AssumeRole` for the Porter role
</Tab>
<Tab title="GCP">
- `secretmanager.secrets.create`
- `secretmanager.versions.add`
- `secretmanager.versions.access`
Granted on the project.
</Tab>
<Tab title="Azure">
- `Key Vault Secrets Officer` (or equivalent get/set permissions)
Granted on the Key Vault used by the connected cloud account.
</Tab>
</Tabs>
GKestenberg
approved these changes
May 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the new 403 response and required cloud IAM permissions when creating an environment group fails because the connected cloud account cannot manage secrets.
Context
Upstream PR maps cloud-provider access-denied errors (AWS Secrets Manager, GCP Secret Manager, Azure Key Vault) to a 403 with an actionable message, replacing the previous opaque 500. Users hitting this need to know which permissions to grant the Porter role.
Changes