Conversation
melissamahoney-mongodb
requested changes
Sep 15, 2026
Comment on lines
+67
to
+79
| .. note:: {+atlas-admin-api+} Limitations for Regionalized Projects | ||
|
|
||
| For projects with a non-US *Project Services Region* enabled, you | ||
| can access the preceding features only through the {+service+} | ||
| console. |service-fullname| doesn't support programmatic requests to | ||
| the :ref:`{+atlas-admin-api+} <atlas-admin-api>` for the following | ||
| features, and such requests fail: | ||
|
|
||
| - :ref:`Performance Advisor <performance-advisor>` | ||
| - :ref:`Query Profiler <profile-database>` | ||
| - :ref:`Schema Advisor <schema-suggestions>` | ||
| - :ref:`Data Explorer <atlas-ui>` | ||
| - :ref:`Real Time Performance Panel <real-time-metrics-status-tab>` |
Collaborator
There was a problem hiding this comment.
As its own little change, this feels tidy. However, in context of the broader section, this is sort of awkward and repetitive. It refers to the above features, and then describes the following features, which are all the same. Can we simplify? Does it have to be a separate note? Could this simply be "You can't access these features by programmatic request"?
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
2 participants
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
Adds a note to the Atlas Data Processing page (
cet/atlas/data-processing.rst) clarifying that for projects with a non-US Project Services Region (data regionalization) enabled, five features are accessible only via the Atlas UI — programmatic requests to the Atlas Administration API are not supported and will fail.Affected features:
The note is placed immediately after the existing section that enumerates these same five features, and intentionally avoids citing a specific HTTP status code (engineering logs show a 400 from the regionalization check, but HELP-99639's customer observed 401/500 — the wording states only that requests "fail").
Jira
Resolves DOCSP-58901 — motivated by HELP-99639 (customer's Performance Advisor slow-query-logs API calls failing on a regionalized project).
Root cause (context)
All public Atlas API requests route to
mms-api-publicpods inus-east-1only; no public API pods are deployed in the EU regionalization regions. Regionalized projects therefore hit the regionalization check and fail for these endpoints.Staging