Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
484 results found
-
Support the unlimited mode for t3 AWS instances (M10 and M20)
We use M10/M20 instances (AWS backend), which accumulate CPU credits over time. The problem is that when Atlas nodes run out of CPU credits, performance goes down and we see a lot of CPU steals. This is a common issue with AWS EC2 instances. We would like to have an option within Atlas UI (a tick box perhaps) to enable the unlimited mode for t3 instances (M10/M20).
1 vote -
Sign Up Process Security
I have recently signed up for a developer account. I have used a Microsoft email address during registration. As soon as I submitted it, I have received an account login MFA message from Microsoft indicating that someone is trying to sign into Microsoft with it. I obviously used it to just register with Atlas as an ordinary email address. Being security savvy, it indicated a red flag. There is a potential that your registration system is compromised (hacked) by a malicious actor. Please forward this message to a security team.
1 vote -
Ability to create mirror/snapshot clusters for load and behavior testing
We would like to request the following:
- The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
- This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
- The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
- The mirrored cluster should be allowed to…
1 vote -
Enforce MFA for google login users
Our organization needs to enforce MFA for users signing in with google login. Is there any way to do it other than "Require MFA"?
1 vote -
Allow private dns names for Atlas private endpoints
When a customer requires the use of private DNS names for their Atlas private link connection strings, can we allow them to switch on this capability? Basically use a private dns zone instead of a public one and share it as part of the VPC endpoint setup? AWS seems to offer this capability. See this link here https://aws.amazon.com/about-aws/whats-new/2020/01/aws-privatelink-supports-private-dns-names-internal-3rd-party-services/
11 votes -
Hyperlink to "all cases" that's under the "create new case" link
To access the support portal from the projects page:
- Navigate to Support to the left side of the page
- Click on Visit Support Portal button under Request Support
It will be easier to navigate if a hyper link of "all cases" can be added to "create new case" from the "get help" drop down as in screenshot attached.
2 votes -
4 votes
-
Remove the requirement to have an API Access List CIDR before being able to manage backup schedules
The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952
Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedulesOur request is that the requirement to have an API Access List to manage backup policies be removed.
At the very least,…
3 votes -
Lock a user account
We have an occasional need to disable/lock an individual database user. Either because of a run away process or inactivity. We do not want to change the password or drop the user as we may need to reenable the user quickly with the same permissions and password as before.
6 votes -
Add more information to "We are deploying your changes..." blue bar
Occasionally we see the deployment blue bar but aren't sure exactly what is being done. It would be very useful to have a link to click to see what changes are currently being pushed out.
5 votes -
Add UUID generation to Atlas Functions
Atlas Functions have a
utils.crypto
library that offers some basic cryptography functions. One of those should be the moderncrypto.randomUUID()
that is now standard in ECMAScript. Currently, Atlas Functions cannot generate a UUID without resorting to third-party dependencies. I prefer using full UUIDs over Mongo's proprietary ObjectID.2 votes -
List user id in access screen, needed for project owner id in when setting up a project inpulumi
As title. I want to easily find user IDs from teh Atlas UI
1 vote -
CORS on the Atlas API
The Atlas API does not yet support CORS. Without CORS, calling the API from within a browser, using a React Client, for example, fails the 'preflight checks'.
"...has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource...."
If the Atlas API could add the 'Access-Control-Allow-Origin: *in the header response, then browsers would permit the API to be called.
Note: for the pre-flight check, the browsers call the OPTION method.
1 vote -
Set Customer Managed Key (CMK) for wiredtiger encryption at the Organization level
For Organizations with a large number of projects, it is cumbersome to rotate keys for every project. If there was an option to set a default at the Organization level, and maybe override by CMKs set at project level, it will reduce the effort of key rotation for every project.
1 vote -
Enhanced Access to Secrets in the context.environment Object
We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.
This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.
As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not…
2 votes -
SSO + SCIM for Atlas Auth
Support SCIM for SSO as this can allow for more fine grained control for access groups in Atlas. This can help IT groups hit their goal of a consistent RBAC set up and improve the user experience for MongoDB Atlas users (less back and forth with IT).
https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management
19 votes -
Hello, I had a superb consultative experience with Colin Phillips. He assisted me with understanding support options for a website database
Colin Phillips provided superb and outstanding help to me with the next steps for realizing my dream project.
With Gratitude, Amilcar1 vote -
Code support
Your website is a monster where is very difficult to get the useful information.
I wanted to use Realm to use a mongo cluster and after hours trying I give up.
I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)Solution: Let's say I have a single cluster and a single realm app created.
Just give me the code with all the ids necessary.In my case I wanted to run it from the browser.
This is the code I tried to execute:
…const app = new Realm.App({ id: 'tradeapp-bozmd' }); const
1 vote -
storage autoscaling at N %
Dear Mongo Team,
Your engineers advise to add more storage to the clusters when it reach 80 % usage as this is when performance degradation can occur. At the time of writing the autoscaling happens at 90 % disk usage. We want to be able to adjust at what % of usage the autoscaling happens and set it to the value of 80 % basically what your engineers advise.
12 votes -
Monospace font for Atlas project user creation fields
When you start a new project using Atlas, a username and password are suggested. The username and password fields use a font with almost identical lowercase L and capital i.
My suggestion is to use a monospace font in those fields for disambiguation.
I use a password manager on my phone (as do, I imagine, many others), which means it’s very annoying to have to figure out if a character is an l or an I on the computer every time I have to copy down info for a new project.
1 vote
- Don't see your idea?