Repository navigation
docs(cloud): document AWS roles restricted to specific regions - #870
Merged
Merged
Conversation
The AWS page said not to add a region condition to the IAM role. A region-restricted role works once the account has an AWS Regions list, which the page never mentioned. Add a section on restricting the role to specific regions, the AWS Regions field in the connect steps, and a troubleshooting entry for an account that connects but stays empty. Drop the Access Keys step for an AWS Region field the form no longer has. Signed-off-by: mayankpande88 <[email protected]>
There was a problem hiding this comment.
Code Review
This pull request updates the AWS integration documentation to explain how to restrict IAM roles or users to specific AWS regions using the new optional "AWS Regions" setting in NudgeBee. It details how this setting avoids region lookup failures and adds a troubleshooting section for empty accounts caused by region restrictions. The feedback suggests a minor rephrasing to improve the readability of a sentence explaining the behavior of global services when us-east-1 is not allowed.
Signed-off-by: mayankpande88 <[email protected]>
RamanKharchee
approved these changes
Oct 8, 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
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.
Description
Summary
The AWS page told readers "Do not add a region condition" to the IAM role. That is out of date: a role restricted to specific regions works once the account is given an AWS Regions list, and the page never mentioned that setting. A reader with a region-restricted role got an account that connects and then stays empty, with nothing on the page pointing to the fix.
The page now gives:
It also drops the Access Keys step that asked for an AWS Region field; the form no longer has one.
Edit AWS Regions is not in every self-hosted release yet; the page tells those readers to upgrade or contact support.
Type of change
How Has This Been Tested?
Open the Amazon Web Services page in a local build of the site: the new section sits after the Option B policy document, the links to it from "Trimming it safely" and "Troubleshooting" jump to it, and the troubleshooting entry links back to the permissions policy.
Checklist
npm run buildlocally and the site builds without errorsnpm run lintlocally and lint passesgit commit -s)Local e2e: n/a — documentation only; the site build and lint pass.