Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
471 results found
-
Allow --removeAutoIndexId option to Atlas live migration as default
Apparently Atlas live migration does not support --removeAutoIndexId option due to which some collections having
autoIndexId set to false
does not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
API for Granting Infrastructure Access to MongoDB Support for 24 Hours
As per documentation at https://www.mongodb.com/docs/atlas/security-restrict-support-access/#grant-infrastructure-access-to-mongodb-support-for-24-hours one can grant access for support for 24h only via the UI. It would be very useful to be able to do this via the Atlas API.
1 vote -
Trigger runtime is US by default which is not GDPR compliant for EU countries
The ATLAS Trigger UI should let the user select the region for the realm deployment done in the background. At the moment it's not fair because (1) at no moment you're noticed the runtime will be in the US (and for UE countries it matters a lot, it's not GDPR compliant) and (2) it makes the nice ATLAS Trigger UI useless for UE countries...
We're forced to create a realm app manually to be able to select a local deployment. We appreciated the 'trigger' section on the ATLAS side. It's more integrated and makes following trigger operations easier. Now trigger…
1 vote -
Data migration from Cloud manager to Atlas
With reference to case https://support.mongodb.com/case/00918578 we experienced situation where the migration was in a stuck state eternally. If the validation checks fail, then it is only fair and logical to fail the migration with a relevant error rather than the status lying about your shard migration is in progress.
Also, emit status updates on the migration, such as pre-validation checks passed, syncing data, and % complete on data migration or initial sync rather than just a green bar, and whatever else such as if it is building indexes, etc during migration. Basically, make the status as readable and logical as…
1 vote -
MFA Painful to use due to need for frequent logins
Even though I use the same computer, I need to re-login every single day (possibly more frequent) - which is even more painful when using MFA.
Should have the option to stay logged in longer on same machine/IP address - perhaps make it an configurable option1 vote -
We can provide a resume / pause option to Mongodb export & import
The Mongodb export and import when used for uploading large or very large files are susceptible for interruptions.
It would be great, if we can provide a resume options while import or exporting the files like how we have in Oracles expdp1 vote -
Provide "Password Age" for Atlas password auth users via Atlas API
Similar to "Last Login Date" suggestion, add the age of the password for SCRAM users. I see that https://jira.mongodb.org/browse/SERVER-3197 was closed as "Won't Fix", but this will at least allow reporting, audit, external maintenance, etc.
1 vote -
Add an option to include sample data during cluster build
When working through tutorials or University courses, often you need to build a new cluster and then add sample data to it. It would be nice if you could just check a box in the cluster creation page to have the cluster brought up with sample data already provisioned, thus combining two commonly used steps, into one.
1 vote -
Enable and disable balancing on a collection
Shell commands sh.enableBalancing() and sh.disableBalancing() were not permitted on Atlas hosted MongoDB. Is it possible to grant this permission?
Currently it failed with error:
…
uncaught exception: Error: command failed: {
"ok" : 0,
"errmsg" : "not authorized on config to execute command { update: \"collections\", ordered: true, writeConcern: { w: \"majority\", wtimeout: 60000.0 }, lsid: { id: UUID(\"ed83ed26-e07b-4f34-a90a-a145bbe58a48\") }, $clusterTime: { clusterTime: Timestamp(1646788928, 17), signature: { hash: BinData(0, 347249E35ED43BDADAE12FB0F794C091CB86206E), keyId: 7052082196881866761 } }, $db: \"config\" }",
"code" : 13,
"codeName" : "Unauthorized",
"operationTime" : Timestamp(1646788928, 18),
"$clusterTime" : {
"clusterTime" : Timestamp(1646788928, 18),
"signature" : {
"hash" : BinData(0,"NHJJ417UO9ra4S+w95TAkcuGIG4="),
"keyId"1 vote -
Separate Data Lake Administrative Permissions into Roles
Currently Project Owner permission is required to create and manage data lake clusters. This requires dangerously elevated privileges simply to manage Data Lake.
I simply would like to either use existing project roles or create new roles specific to Data Lake with similar duty segregation: Data Lake Manager(similar to Project Cluster Manager), Read-Only, Read-Write, etc.
Project Owner should not be required to administer or use data lake features. Non-granular roles are fine for this urgent need, we simply need reasonable coarse-grained roles that would satisfy usage in any security-minded enterprise.
1 vote -
bad experience
sorry to say but your service is very bad because when i upload a data collection after few hours my data automatically jumbled.
please send me the reason why this is happening.
1 vote -
Specific Privilege selection on Org Level
It would be great to select specific privileges for on the Organization Level as well. Similar to what one can do on the Project Level. E.g. Org Member but without being able to see billing.
1 vote -
B2B marketing is pretty slow
We had just migrated to another platform probably we did not approach you earlier
Target all Users of SAP !
1 vote -
connecting from ubuntu to mongodb atlas is terrible
kamal@zehan:~/Desktop/mongodb$ mongo "mongodb+srv://cluster0.d9ct7.mongodb.net/myFirstDatabase" --username mongo
MongoDB shell version v5.0.5
Enter password:
connecting to: mongodb://cluster0-shard-00-00.d9ct7.mongodb.net:27017,cluster0-shard-00-02.d9ct7.mongodb.net:27017,cluster0-shard-00-01.d9ct7.mongodb.net:27017/myFirstDatabase?compressors=disabled&gssapiServiceName=mongodb&ssl=true*** You have failed to connect to a MongoDB Atlas cluster. Please ensure that your IP allowlist allows connections from your network.
Error: bad auth : Authentication failed. :
connect@src/mongo/shell/mongo.js:372:17
@(connect):2:6
exception: connect failed
exiting with code 11 vote -
1 vote
-
Atlas should allow deployments of non-voting members on region for tiebreaking purposes
No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.
This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.
1 vote -
Ability to read the logs in old format
there should be option to download log files as native format, as we need to download multiple tools to get it to normal!!
1 vote -
Feature Request: DNS record per zone for global cluster
Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.
This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…
1 vote -
Atlas Screen Navigation
In both Atlas & Ops Manager, on screen navigation is not good. When I click an icon or item, the screen shows different layouts for each click.
For example, if I want to see Billing info, I have to click little 'mongo logo' icon, then Bill menu appears.
Then if I click All Cluster item, the Bill menu disappears and left navigation/ menu also disappear.
I have click multiple times, different icon, or menu to get what we want.
There is no consistency in the screen appearance when we click an 'icon or menu'. Each click shows different screens.
Same…
1 vote -
Setting up the New MFA/Adding a disabled user back to project
The whole process of setting up the new 2FA or MFA is very tiring. It should be simplified with the roles who can add new members and set up the method for new team members.
Chat was helpful but it's not easy to follow up for every team person.Also for a change in phone or lost device should have some details to get ahead for the user to access the db, after authentication.
As authenticator app gets lost with the device, it should not end in loop where it keep asking for Admin password.
1 vote
- Don't see your idea?