Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
468 results found
-
max database users not visible
We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.
16 votes -
Set schedules for pausing clusters
It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.
16 votes -
[Atlas] Enforce password policy for DB access
Currently is not possible to enforce any kind of password policy via Atlas UI.
Would be nice to let user define an expiration time and password policy that user should meet.16 votes -
Support for AWS China (Beijing/Ningxia) regions
Please make Atlas available in AWS's Beijing/Ningxia regions. This is important to due to China's internet restrictions to achieve the best possible performance/latency for our Mainland China customers.
14 votes -
mongomirror with db rename
We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?
14 votes -
Allow Alerts to be sent to an Atlas Team
Alerts can be configured to send to specific Atlas Users, but not Atlas Teams, which diminishes the value of setting up a team of users.
14 votes -
Ability to choose a Primary shard for newly created database
In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy
13 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 -
Use wildcard databases in user role privileges (like collections)
Use wildcard databases in user role privileges (like collections)
12 votes -
Set MongoDB Production Support Employee Access to Atlas Backend Infrastructure at Project Level
The Restrict MongoDB Production Support Employee Access to Atlas Backend Infrastructure is currently set on the organizational level. This should also be possible at the project level. Secondly, add the possibility to grant access indefinitely until revoked.
12 votes -
configure IP whitelisting on database user level
enable the user creation to have the following option
authenticationRestrictions: [
{
clientSource: ["<IP>" | "<CIDR range>", ...],
serverAddress: ["<IP>" | "<CIDR range>", ...]
},
...
],12 votes -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
12 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
12 votes -
Provide Atlas support for "Classic" VNet Peering topology
Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT
12 votes -
Extend / Configurable retention time of audit logs
This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.
12 votes -
UUID Schema Validation
It would be very handy to have the ability to specify a schema validator using bson type UUID (binData subtype 4) instead of the more generic binData subtype 0.
11 votes -
Allow db.killOp() and manual restarts on secondaries
Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
Also please add the ability to manually restart secondaries, not just failover the primary.Thanks.
11 votes -
Ability to schedule monthly maintenance windows
Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.
I realize we have the ability to defer maintenances for a week, which is great. However, we're now…
11 votes -
Have the ability to downgrade
Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?
As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster…
11 votes -
Log browser and log search capability across replicaset nodes.
Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.
11 votes
- Don't see your idea?