Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
488 results found
-
Add filters for easily finding projects that have encryption/audit enabled in the UI
The https://cloud.mongodb.com/v2#/clusters has certain filters to get specific Atlas clusters. Can we add couple of more filters that can easily identify, whether that project has been enabled for encryption at rest or if the auditing has been enabled/disabled. This will help us easily generate reports for cis20 reporting.
1 vote -
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 falsedoes not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
Feedback and public roadmap.
I have voted and written since 2020 several improvement ideas for your platform.
Being a client for a major insurance company, I'm disappointed to see that for several suggestions dating back more than 12 months, it doesn't even seem to have been looked at by your team.
It would be more than interesting to have an idea for your roadmap as well as a dynamic management of the catalog of ideas (feedback) maintained by your customers.
I consider this a lack of respect for your users and customers.
Some examples:
https://feedback.mongodb.com/forums/924145-atlas/suggestions/40638277-atlas-backup-to-second-region
https://feedback.mongodb.com/forums/924145-atlas/suggestions/43289796-max-database-users-not-visible
https://feedback.mongodb.com/forums/924145-atlas/suggestions/42163234-authentication-on-azure-iam
3 votes -
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 -
Reshard Global Writes Collections
MongoDB supports resharding, so not being able to change the global writes shard configuration is very strange. It makes it impossible to fix mistakes with the shard configuration. Even if it requires blocking to redo or remove the shard configuration it should be possible.
2 votes -
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 -
Make Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler GDPR compliant
As the data used for Real Time Performance Panel, Data Explorer and Performance Advisor and Profiler are processed/routed in/over the USA european customers that need to be GDPR compliant can't activate those three options. Unfortunately these three features offer a great feature set which really hurts to not have. This is a high prio topic for us.
2 votes -
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 -
Atlas UI Show Snapshot ID in web
Please provide a capability to show the snapshot ID of a snapshot in the web GUI, currently we have to make an API call to get the snapshot-id
4 votes -
Add ability to chose the new primary node when you perform a test election
There's a "test failover" option, which shuts down the primary and forces an election. However, you have no control over which new primary will be elected (just the preferred region) which sometimes does not work as expected.
It would be really useful if you have the possibility to manually chose which node will be elected as the new primary.
6 votes -
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 -
AWS multi-region key (CMK)
While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.
https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html
6 votes -
Control IP Access list for project-only API keys at the project-level exclusively
When setting up API keys as a project owner, you only get one opportunity to manage the access list without getting an Organization Owner to modify it thereafter.
This creates a bottleneck where users need to ask for their API key access list to get changed (or alternatively make a new keypair, and have the API Keys list cluttered).
If a key is only being used in one project, it should be allowed by the project owner to update the access list at any time since there is no risk of it affecting the organization.
19 votes -
Deploy Custom Role to specific clusters only.
You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.
Can you extend this functionality to "custom role" also %
13 votes -
Create Atlas UI Triggers Programatically
Currently, a trigger which gets displayed on the Atlas UI (under Data Services > Triggers) cannot be created programmatically, they may only be created by clicking through the Atlas UI.
The triggers created from the Atlas UI automatically creates a new realm app named "TriggersRealmApp" even when a realm app with the same name already exists. There is no way to have any of the triggers created under any other realm app displayed in the Atlas UI. The only way is to create them under the auto generated "TriggersRealmApp" which gets created after the first trigger from the…
6 votes -
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
- Don't see your idea?