Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
483 results found
-
Allow multiregion sharded clusters to have Primary nodes in multiple regions
For multi-region sharded clusters, the primaries for each shard remain in a single (highest priority) region in Atlas. If these primaries can be spread across multiple regions, that will a) provide consistent average response time for applications that connect from multiple regions as active-active b) Limit the blast radius if the highest priority region is unavailable c) Better distribution of workload from an application side.
This architecture is currently possible with EA deployments but not with Atlas.
6 votes -
Support Ticket subject lines
MongoDB Support to have nicer subject lines for the notification emails sent out by the MongoDB Support Portal.
There's nothing distinguishing except a case number (which mean nothing), and it’s hard for me to differentiate or even show up in local searches. Going to an external ticket tracking system is a bit of a hassle, and won’t be integrated with any of our local search or content management stuff.
It would be good to have it headed with what my case is about.
1 vote -
4 votes
-
Please make it possible to deploy instances to AWS local zones
Please make is possible to be able to deploy instances in AWS local zones, to be able to comply with local regulations, where data needs to be stores in a specific country,
1 vote -
Custom the time interval when do the primary failover manually
Currently, the time interval of the primary failover manually is done within several seconds. We want to increase the time interval of the primary failover, so the chaos engineer could be done in our server which connects to Atlas.
1 vote -
sort custom roles
Sort custom roles dropdown when choosing to assign to a user. Currently when creating a new user and selecting a custom role, the roles are ordered by creation date which makes it hard to find when many exist.
1 vote -
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 -
Suggestion to make the Organization Role Mappings page easier to navigate to
Make Organization Role Mappings page in the Federation Management App quicker to navigate to. Currently the quickest way is to click the "Create Role Mapping" from the Overview page under "Optional: Set Up Advanced Settings" and then click Cancel.
If the "Optional: Set Up Advanced Settings" box is not longer available in the Overview page, you'll have to click the Organization tab from the side navigation bar > [Organization Name] > Create Role Mapping > Cancel in order to reach the Organization Role Mappings page.
3 votes -
providing the service as quoted
Very angry and having suffered twice now through the lies told about only going to take 7-10minutes for an upgrade on y to be edging toward an hour now. Last time i have issues with a snapshot being deployed that never fully populated the DB when restored, disgrace, clients only get interruptions, business downtime and you want more money for better service to provide a fix to a problem that you created? its a joke, your company should be investigated by authorities.
1 vote -
Find Database on Multiple Cluster
Enable the search box on Database Deployments to search for a particular database on all clusters under the project.
This would be helpful when having different databases on many isolated clusters.
1 vote -
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 -
Allow multiple VPC CIDR ranges in Peering connection
Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.
Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
Today, I need to create a separate private link connection to be able to connect to the second CIDR range.31 votes -
Feature: Atlas UI -- Star/Favorite/Bookmark of Project
It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search
2 votes -
Memory managed on the mongodb atlas nodes
we recently had a major outage due to OOM on the mongodb shard nodes . we would suggest help preventing this by providing below features so this can be managed properly going forward
- Set the memory allocated to the WireTiger Cache
- Configure more memory for a tier. The current tier is M50 (8 vCPUs, 32GB memory). We would like to be able to allocate more memory for M50 to handle more connections and memory use for workloads. Scaling up to M60 will double the vCPUs to 16 which we do not want. Perhaps offer tier with high memory usage for…
1 vote -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
og the size of oplog-mongomirror.bson.sz at time of deletion in mongomirror logs
currently when we run the mongomirror with --oplog, it does the status when it is deleted.
It will be good , to add the size information ofoplog-mongomirror.bson.sz
, that will help us to decide the appropriate disk .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/
10 votes -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes -
secrets versioning for database users
We would like to have secrets versioning on atlas end so that secrets rotation is easier - as it is a periodic procedure in most companies, would be great to refer to a new secret version of an existing user instead of recreating the user.
also considering this is sadly not gonna be handled https://feedback.mongodb.com/forums/924145-atlas/suggestions/44283477-vault-should-return-users-only-once-they-can-be-us would be cool to make rotation easier.1 vote -
There is a grammatic error in button text.
The button says "Do not me show again"; it should say "Do not show me again".
Thank you,
Alpesh1 vote
- Don't see your idea?