Skip to content

docs(cloud): document AWS roles restricted to specific regions - #870

Merged
blue4209211 merged 2 commits into
mainfrom
docs/aws-region-restricted-role
Oct 8, 2026
Merged

blue4209211 merged 2 commits into
mainfrom
docs/aws-region-restricted-role

Conversation

@mayankpande88

Copy link
Copy Markdown
Contributor

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:

  • a section on restricting the role to specific regions: why the list is needed, where to set it (when connecting, or Edit AWS Regions on a connected account), and which services stop working
  • the AWS Regions (optional) field in the common fields and in the IAM Role ARN and Access Keys steps
  • a troubleshooting entry for "The account connects but no resources or alarms appear"

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

  • Update to existing documentation

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

  • I ran npm run build locally and the site builds without errors
  • I ran npm run lint locally and lint passes
  • Internal links work; new external links open the correct page
  • My commits are signed off (DCO — git commit -s)
  • I read CONTRIBUTING.md

Local e2e: n/a — documentation only; the site build and lint pass.

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]>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread doc-server/docs/features/Cloud/AWS.md
@blue4209211
blue4209211 merged commit a216672 into main Oct 8, 2026
4 checks passed
@blue4209211
blue4209211 deleted the docs/aws-region-restricted-role branch October 8, 2026 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants