Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
63 results found
-
Support for customer-managed keys (CMK) on the volume-level instead of Encryption-at-Rest
For some customers managing a set of low-latency workloads is crucial, so volume-based encryption using their own KMS encryption keys is preferred over the encryption-at-rest feature of the WiredTiger storage engine. https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html
The support is required for clusters, their backups and Atlas Data Lake.3 votes -
Send Atlas logs to S3
I would like to automatically send my cluster logs to my S3 bucket. I could then use Atlas Data Lake to query them and Charts to create visualizations on them, or inspect them with other tools.
64 votes -
Custom metric option on Datadog
Currently, there is no option to use the custom metric option when using the Atlas Datadog integration.
We would like to use this functionality in Atlas : https://docs.datadoghq.com/integrations/guide/mongo-custom-query-collection
12 votes -
Import IP ranges from cloud-provider list
Automatic rules based on cloud-provider list (region/zones selected by user).
Source for AWS IP ranges: https://docs.aws.amazon.com/pt_br/general/latest/gr/aws-ip-ranges.html
1 vote -
Discord Integration
Hi, I would like to know if there is a possibility to deploy Discord (webhook) integration like Slack.
1 vote -
SEIM integration between Splunk and MongoDB
I'd like formal integration between Splunk and MongoDB for the SEIM use case.
8 votes -
8 votes
-
Database user credentials rotation with AWS SecretManager
- Similar to the HashiCorp Vault integration, you should offer the option to use AWS SecretManager in the same way
- Rotating dbuser credentials is a common best practice. Many people that are "AWS" shops chose AWS-native solutions over 3rd- party.
- We use SecretManager, so this would save us from having to write something of our own.
7 votes -
Send alerts to Azure Log Analytics
Similar to the 3rd party integrations already in Atlas, it would be helpful to have integration with Azure Log Analytics for alerts and metrics instead of writing it ourselves with the Atlas API
13 votes -
KMIP-based Encryption at Rest
Problem Statement,
What is the problem?
As of now (2021-03-09) Atlas does not support KMIP-based Encryption at Rest. Currently supported (as of 2021-03-09) encryption key sources are,
* AWS Key Management Service (AWS KMS)
* Azure Key Vault
* Google Cloud Key Management Service (Google Cloud KMS).Why is this a problem? Customers who use KMIP to source encryption keys are not able to use Encryption at Rest (https://docs.atlas.mongodb.com/security-kms-encryption/) feature of Atlas.
**Proposal,**
* Add KMIP support for Encryption at Rest feature of Atlas.9 votes -
Atlas API to update Project Timezone
At the moment, Project Timezone setting can only be done via Atlas UI. We are automating project and cluster creation and setup for our application. We need an API to update Project Timezone setting just like other project settings. This feature is important for our organization to keep all the project with the same settings without a manual intervention.
19 votes -
Zabbix integration
It would be interesting, Atlas could also be monitored via SNMP, in order to be monitored by Zabbix.
Many companies have their own CommandCenter, where they centralize monitoring in a single tool.
1 vote -
Provide callback method for API calls to avoid polling
Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.
Some examples of where this would help:
- After creating a restore job, waiting for the snapshot download URL to be ready.
- After modifying the automationConfig, waiting for all agents to report that they're in goal state.
3 votes -
Display the MongoDB Network Peering Container ID in the console
Instead of forcing use of the API, why not display the MongoDB Network Peering Container ID for the peering connection in use?
1 vote -
Allow customers on Atlas to use Redseal to collect VNET/NSG configuration information
We use a tool named Redseal (https://www.redseal.net/) to collect and report on network devices and boundaries. Redseal supports an Azure "plug-in" that calls the Azure portal and retrieves security-relevant VNET and NSG information. The plug-in's configuration requirements are attached (see page 2), along with our proposed use of them (page 3).
We already use Redseal to gather information for vnets spread across several subscriptions in our Azure tenant, including one managed in our address space by a third party. We'd like to extend this ability into our area of the Atlas tenant.
The value to us is that…
1 vote -
Support Dynatrace integration for monitoring with Atlas
This is a request to support an integration with Dynatrace for monitoring MongoDB deployments in Atlas.
18 votes -
Access Total Memory from Mongo clusters
Could the MongoDB metrics available in Datadog get expanded to include total memory? For setting up thresholds to track the resident memory of each client, it would be ideal to standardize these thresholds across clients. To do so would require displaying resident memory as a percentage, which would the total memory to calculate for each client. Please let me know if total memory can be a metric available in the Datadog integration or perhaps how I can find it if it already exist or can be created.
15 votes -
Please bring Atlas to digital ocean PaaS as a first class offering!
Hey there,
I know it's hard for big companies to get along, but I'd love to have a seamless experience for using MongoDB alongside DO's new PaaS offering. Can you all strike a deal please?
2 votes -
mongoexport with Client Side Field Level Encryption
I would like to have mongoexport and mongodump tools with Client Side Field Level Encryption /Decryption. Please consider while developing new feature.
3 votes -
Allow Network Peering to be used by Atlas Triggers / Realm Apps
What is the problem that needs to be solved? Some users want to receive outgoing network connections (e.g. with HTTP/HTTPS traffic) from Atlas (Atlas Triggers / Realm Apps) via their configured Network Peering, i.e. via private IP address space (so that everything is kept in private IP address space and nobody outside could reach it). Example: customer would like to have Atlas Trigger / Realm App which will notify (via HTTP) some of customer's internal system(s) about a change/trigger.
Why is it a problem? (the pain) Current Atlas (Atlas Triggers / Realm Apps) behavior does not allow to use private…
4 votes
- Don't see your idea?