Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Improve the sample code for Connecting with MongoDB Driver
When in Atlas you click the Connect button and get to the screen 'Connecting with MongoDB Driver', the Java sample isn't using the MongoClientSettings.builder() to set writeConcern and retryWrites. This is done in the connect string instead, even though the builder does provide those two settings.
I suggest only using the MongoClientSettings.builder() for better type safety.1 vote -
Restrict whitelist ip
I would like there to be an option to restrict users to what they can whitelist in network settings for a project. I want there to be option like "only users with owner access can create non-temporary IP whitelistings" so we can avoid having our developers adding IP addresses that gets outdated and pose a potential security risk.
1 vote -
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 -
Alerts for Atlas Limits
It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creating a workaround. E.g. it is not possible to have more than 50 Endpoints per Project. But creating a new project is not a straightforward exercise. If the alert had occurred earlier there would have been more time to account for this.
8 votes -
Granular cost and inventory details
We are building a unified portal to view our databases and almost all other managed cloud providers like AWS provide instance level/node level view of clusters.
Currently, there's no way for me to get instance level/node level inventory details.Also, when billing/cost is generated, it's generated on a cluster-level basis. Since we now have separate sizing for Analytical nodes and Electable nodes, it's better to separate out the cost to be at an instance level.
Again, all cloud providers like AWS do give us instance-level costing for EC2/RDS so I don't see why that can't be technically possible.
Support costs…6 votes -
Add the ability to configure the auto-resume setting for triggers through terraform
Currently MongoDB triggers can be created through the TF, but to enabled the auto-resume setting this needs to be manually done through the Atlas UI. This should be an option on the "mongodbatlaseventtrigger" TF resource, so it can be all configured together.
10 votes -
API to list clusters that has snapshots on it- even deleted clusters
Today we use the API below to list the clusters that exists in a project
GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters?pretty=true
After having the clusters list, we can list the snapshots from one specific clusters using the API:
https://www.mongodb.com/docs/atlas/reference/api/cloud-backup/backup/get-all-backups/
GET https://cloud.mongodb.com/api/atlas/v1.0/groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/backup/snapshots
Now on Mongo Atlas I can delete a cluster and ask not to delete their snapshots. So if I want to use the same functions I can't, because the list of the clusters do not show the clusters that have been deleted but still has snapshots on atlas.
It would be great if the API that lists the cluster also give us…
5 votes -
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.
7 votes -
Integration with Percona Monitoring & Management
Please release Integration to Percona Monitoring & Management. Thank you.
1 vote -
Please let users know you will be making huge charges for no services provided!
Please let know users that Atlas will generate huge charges for NO usage and will be hit with huge bills without having even used your service. Also, please let users know that MongoDB will not build or compile on Raspberry Pi either Ubuntu or Debian!
2 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 -
Restore protection similar to termination protection
A restore protection option similar to the termination protection for clusters.
When a cluster has restore protection enabled, it can't be the target cluster for a restore operation. This will prevent accidental restores to the wrong target cluster from affecting the protected cluster.The motivation is preventing mishaps from affecting critical production clusters.
The UI for selecting the target cluster of a restore operation has you select the cluster from a dropdown and then type in "I Agree". That still leaves you open to mistakenly select the wrong cluster if you aren't paying good enough attention.
The restore protection feature…5 votes -
5 votes
-
Aggregation pipeline support for Online Archive via Custom Criteria
I would like to have the capability to run the Aggregation pipeline via Custom Criteria.
10 votes -
Disable duplicate linked Organization names
Currently, one can create multiple linked sub-organizations under a main billing organization, but having the exact same names. The below API command, run repeatedly, will create the same sub-org name with different orgId's. I believe this only serves to confuse administrators and makes management more difficult -- therefore, I'd rather have the API fail with "HTTP 4xx: Another organization already exists with the same name."
curl -s -X POST --digest -u "$ATLASPUBLICKEY:$ATLASPRIVATEKEY" \
--header "Content-Type: application/json" \
--data '{ "name": "MYORG", "orgOwnerId": "MYORGOWNERID" }' "https://cloud.mongodb.com/api/atlas/v1.0/orgs" \
| jq -r .organization.name2 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 -
mTLS for Atlas Alert Webhook Integration
Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.
2 votes -
Specify allowed values for fields in AWS CDK
Example create database user:
- Allowed values for databaseName are admin or $external in Admin API documentation (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Database-Users/operation/createDatabaseUser)
- Corresponding CDK construct property (https://constructs.dev/packages/@mongodbatlas-awscdk/database-user/v/1.1.0/api/CfnDatabaseUserProps?lang=typescript#property.databaseName) only specifies string without further information
It would be nice to get IntelliSense in IDEs for fields which are enums behind the scenes.
Alternatively, allowed values should be included in error messages. That would make debugging at runtime easier at least.
2 votes -
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 -
Add a button to retry to collect a payment on the billing - invoices tab
Add a button to retry to collect the payment from a credit card on user request. This will help when there are problems with the credit card funds or credit limit.
2 votes
- Don't see your idea?