Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
495 results found
-
Increase maximum storage size for M60 servers
Currently the maximum storage size allowed for an M60 tier is 4TB. Our cluster is approaching this size, and we're facing having to shard our data, which we would really prefer not to do.
I understand that the maximum sizes are selected for performance reasons, but not every cluster is the same - ours is doing just fine and not struggling at all at this data size, and we would like to be able to continue to grow over time.
5 votes -
Ability to add multiple IP's to the whitelist and download the current whitelisted IP's
If I want to add comma separated IP's it is not possible. We have to add each IP painfully from the UI. Please allow to add comma or semicolon separated IP's to be added at once.
Also, why can't I download the current whitelisted IP's as a CSV or other file?
5 votes -
invoice should show support costs under project and not organization
We need the support costs (in our case Atlas Pro) to show up for each cluster under the project on the invoice. Right now, it shows up as a separate line item in a lump sum under the organization. It makes it difficult or impossible to properly bill the individual cost centers for support costs for their clusters.
If those costs showed up next to the clusters within the project, it would be easy to say project1 goes to cost center 1, but now we have to do project 1 goes to cost center 1 plus some percentage of the…
5 votes -
Sort IP Whitelists in Atlas
Enable sorting and filtering on the whitelist management screen.
There is no logical order to the list of ips.5 votes -
Shorter Temporary Durations for Network Access whitelist
Hello,
it would be nice if you could add options for temporary whitelist entries that are shorter than 6 hours. Often in our Team we find ourselves just needing to whitelist an ip for a short amount of time to look up some documents or fix a bug.
For that case it would be nice to have additional shorter options like 3h, 1h, 30m, 15m.Thanks for taking a look
5 votes -
Migration Tutorial Video
I did a live migration from mLab to Atlas quite recently. Although, the steps for migration were simple and easy to execute it took me alot of time to get over the fear of migrating without losing any data. A tutorial video of the entire process would have calmed my nerves and helped me take a lot less time in the process.
5 votes -
Ability to create and update database triggers via API
It would be really usefule to have the ability to create and update database triggers via the API. Currently, updates to triggers cannot be integrated into our testing and deployment process because the only way to update them is manually through the interface.
5 votes -
It would be useful to have an ability to pragmatically keep up to date with the latest prices in a RESTful fashion.
Something like /offerings/aws/compute/M10 returns:
{
// some metadata about this pricing api.
"prices": [
{
"priceId": "c800b6d9163b0db7",
"region": "us-east-1",
"charges": {
"compute": {
"price": 0.11,
"interval": "hourly",
"currency": "USD"
},
"storage-GB-month": {
"price": 0.015,
"interval": "hourly",
"currency": "USD"
},
"backup-GB-month": {
"price": 2.5000000001,
"interval": "hourly",
"currency": "USD"
}
}
}
]
}Use case: For those that use programs to calculate costs, this will reduce some of the guesswork involved by looking at cryptic documentation and invoices to calculate and forecast costs and be able to charge appropriately to match systems with demand.
Amazon has similar API endpoints available:
https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json…
5 votes -
Terminate existing connections from IPs when removed from the whitelist
When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be…
5 votes -
Description field for VPC peering page
Add a description field to easily identity the peering items in Peerings tab. Example: "Peering for Stage Kubernetes cluster apps"
5 votes -
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
5 votes -
Add Atlas instance in GCP Sweden
Hi! We have applications running in GCP Sweden (europe-north2). Do you have any plans to add support for Atlas in that region?
4 votes -
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.net4 votes -
Manage Feature Compatibility Version (FCV) flag separately from version upgrade
When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.
We would like to see this be a two-step, i.e.
1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.
We understand that some users don't care about…
4 votes -
Enable database users separate read/write permissions based on cluster
We have multiple clusters in the same project, and we need to limit write access to certain CLUSTERS while leaving read only access to any other cluster. The problem is that we cannot do this by DATABASE name as there are many of them, as well as dynamically addition of new ones in clusters, so it will become obsolete and very hard to maintain.
Trying to use the restriction does not help as it limits all access, including read only, to those clusters.
What we'd like to see is that we can limit write access by cluster (not database/collection) and…4 votes -
Remove the requirement to have an API Access List CIDR before being able to manage backup schedules
The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952
Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedulesOur request is that the requirement to have an API Access List to manage backup policies be removed.
At the very least,…
4 votes -
MongoDB Connection Pool Proxy
Currently there is no Connection Pool proxy supported by MongoDB.
With the ever increasing use of serverless and containers, clusters will need to be over provisioned in order to account for the increased connection counts.
A better solution would be a Connection Pool proxy allowing for a many-to-one relation for connections to MongoDB.
In the case of Lambda, this would reduce the number of Zombie connections (Connections that have been terminated on the Lambda side but are still open on the server side.)
4 votes -
Create TTL index based on local timezone as opposed to UTC time
Create TTL index based on local timezone as opposed to UTC time
4 votes -
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).
3 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
- Don't see your idea?