Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
Customer feedback around the UI of Atlas - unable to edit multiple documents at once
The customer wanted me to provide product feedback around the inability to edit multiple documents at once from the Atlas UI. The customer uses a 3rd party tool to do this instead and thought it would be better and more intuitive if this was built right into the Atlas UI.
1 vote -
Stop scamming your users
How about you stop scamming your users with deceptive instruction on your download pages.
1 vote -
Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs
Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.
This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…
2 votes -
Restore a snapshot from one organization to another organization via API call
I have tried to create automation to restore the snapshot from One organization cluster to other organization cluster. Example Prod cluster from Organization A -> Stage cluster from Organization B.
currently this method is not possible to restore a snapshot from one organization to another organization via API call as API key cannot be shared over the scope of different organization.( As per mongo atlas support Engineer)
Please enable this feature to automate the snapshot restore instead of using UI for restore.
1 vote -
Analytics node with NVMe option
We currently have use mongodb mainly to correct data and visualize with chart features. Some chart require heave disk read operation and need more performance. We need fast storage access only for analytics nodes. If we can select NVMe option only for analytics nodes, we use it but we don't want to switch whole clusters to it since main cluster don't need higher cpu/memory/stroage/iops. We just want to use NVMe only with analytics nodes. Some restriction such as min storage size for main cluster is acceptable but don't want to upgrade to higher tier of main cluster.
1 vote -
Altas CIDR ranges for network containers are too restrictive
Background:
For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.AWS minimum imposed CIDR value/subnet size: /28
MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24Azure minimum imposed CIDR value/subnet size: /29
MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…
3 votes -
Push Logs to AWS S3 bucket: IAM role Max_Session expect 12hours
With respect to the feature "Push Logs to AWS S3 bucket " Atlas expect max-session-duration for IAM cross account role is : 43200 (12HRS) by default.
Some organizations like us have limitations on max-session. We reached out MongoDB Support, They said " The Atlas team has confirmed that currently, we do not support max session durations of less than 12 hours. However, there is an internal ticket for improvement, where session duration can be internally configurable via MongoDB's internal support UI. Case ref: 01276442This will provide a flexibility for the organizations to have max-session configured according to their internal…
1 vote -
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
1 vote -
Export logs to S3 at the organization level rather than project level
Currently if we have to export logs to S3 we need to enable log export to S3 at project level. If I multiple projects then same things needs to be done, there should be an option to send logs to S3 on organization level when setup should send the logs to S3 bucket with path name (projectname+'/'+clustername).
1 vote -
Support for Push-Based Logging to Azure and GCP
Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/
1 vote -
(RBAC) Remove CREATE_COLLECTION grant from INSERT permission
In according to the least privilege principle we would like to have a better granularity when defining roles. This feature would help us to have uncontrolled collection creations by applications
2 votes -
Default Maintenance Window to Out of Hours
With Atlas MongoDB, maintenance windows when not defined default in many cases to periods during peak hours. With maintenance such as automated rolling upgrades, this can impact performance. I would suggest defaulting this to a time overnight relative to the hosted region of the cluster.
In addition, there appears to be no obvious way to see what the maintenance window is without inspecting automated updates in the Activity Feed. If this is the case, adding it to the interface would be useful. Note that even toggling the manual setting of the maintenance window to on will default to the first…
1 vote -
Start/Stop Atlas instance from external script
Currently the ability to stop or restart an Atlas instance is not allowed from the customer's side of things, and is an action that can only be performed by MongoDB Support.
We would like to have this feature added.This use case very important for our organization as different application teams should be able to bring up or down the database as they need.
We cannot grant permissions on Atlas console to all the teams in our setup.
Instead, we may have a custom script developed using Javascript or similar scripting languages and enable users to start or stop Atlas…1 vote -
VPC flow log to identify the rejected source IP by IP access list
Customers can identify the source IP addresses dropped by Atlas IP access list if cloud provider flow log like VPC flow log is enabled and stored in the storage like S3.
1 vote -
Atlas DNS name more than 23 characters from the cluster name.
Allow users to have longer DNS name from the cluster name. Currently, Atlas cuts the first 23 characters from the cluster name and the users can't check the cluster name inside the mongo shell.
Example:
Cluster name longer than 23 characters : xxxx-us-east-1-multi-use-1
DNS name : xxxx-us-east-1-multi-us.xsj8t.mongodb.net3 votes -
View Atlas user sign in method in logs or UI
We'd like to see how are users are signing into Atlas.
At the moment we can just see username, email and permissions.I want to see which Auth method they used to sign in e.g. email & password, GitHub SSO, Google SSO, AD etc.
1 vote -
All Clusters permission for ORG level roles
Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.
When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.
6 votes -
View Epoch in Compass
I use epoch times in almost every collection for created time, last modified, etc. Currently I have to copy the time value and paste it into epochconverter.com. It would be very handy if the time showed as a string in a bubble when you hovered over it in Compass.
1 vote -
Larger disk for smaller cluster tier (instance type)
We have TB-scale data in production, and we also have several databases of the same-size for development environment.
Since Atlas's smaller cluster tier such as M20, M30 doesn't support large disks, we need to pay a lot for staging environment too even though we don't need many CPUs / RAMs.
We hope Atlas to support varied storage options in smaller cluster tier
1 vote -
Setup the Atlas web user's team membership as part of the invitation.
Doing so, removes the extra step of assigning the team after the user has accepted the invitation.
2 votes
- Don't see your idea?