Michael
My feedback
35 results found
-
29 votes
An error occurred while saving the comment Michael supported this idea ·
-
26 votes
Michael supported this idea ·
-
3 votes
Michael supported this idea ·
-
12 votes
An error occurred while saving the comment Michael commented
We are bumping this inquiry to see if it would be possible to have some sort of API access to even discover linked organizations under a paying organization. To my knowledge, even with the v2 API, there are no provisions for linked orgs. The documentation for "https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-listorgs" states "all organizations to which the requesting Service Account or API Key has access." My understanding is that the api key only has access to one organization, so why bother with this statement? Please implement access for multiple linked organizations for an api key.
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Once Atlas itself supports this we will implement in the Terraform provider. We are in close contact with the PM who owns IAM and have alerted him to this request.
Michael supported this idea ·
-
3 votes
Michael supported this idea ·
-
8 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
13 votes
Work for OIDC support for Database users has started, and is expected to release around May 2025.
Michael supported this idea ·
-
20 votes
An error occurred while saving the comment Michael commented
We support this request. Moving billing to AWS Marketplace offers has simplified the invoicing / payment process but does NOTHING for charge-back. "MongoDB Atlas Enterprise" exists as a single line-item in our monthly AWS bill , and it is up to our billing analyst to manually pull cost-explorer or per-organization billing.
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
2 votes
Michael supported this idea ·
-
8 votes
Michael supported this idea ·
-
38 votes
Michael supported this idea ·
-
13 votes
Michael supported this idea ·
We already have the login / authentication events captured at the Identity Provider layer, but it's important to have this information from the platform itself. I'm adding my vote to console logins / failures activity being included in organization activity streams, even if it is not shown as part of the default activity stream.