Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

144 results found

  1. Support native Azure authentication for the DB, e.g. service principal

    Customers often want centralized permissioning for the database and LDAP is not generally supported well in the cloud. If a customer is using Azure, they want us to support Azure AD for database authentication. I believe that means using service principals

    32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  IAM  ·  Admin →

    Your applications can now access Atlas Clusters with Azure Service Principals including Azure Managed Identities using MongoDB Workload Identity Federation (https://www.mongodb.com/docs/atlas/workload-oidc/). The feature is supported by MongoDB 7.0.11 dedicated clusters (M10 and above).


    For your workforce access, we recommend to use Workforce Identity Federation (https://www.mongodb.com/docs/atlas/workforce-oidc/) with your corporate identity provider such as Azure Entra ID.


    Thank you for your feedback.

  2. atlas portal ip whitelist

    We were given this idea from a security audit.

    From a security-in-depth perspective we would like to be able to restrict logins on the atlas portal to only whitelisted IP's, this would be analog as to how API whitelisting works at the organization level.
    This is to prevent login's other than from our permitted sites.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  6 comments  ·  IAM  ·  Admin →
  3. SSO integration for Atlas UI

    Enabling SSO for the Atlas interface would limit the ability for outside people to gain access to our accounts. It would also provide us with enterprise tools for managing user access.

    Currently we are using Atlas credentials to log into the Atlas frontend. This appears to be a security risk long term as people could hack into our account and create/destroy resources.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Admin →
  4. Atlas Activity feed should be searchable by cluster

    The Atlas activity feed is currently searchable by Type of event. It should have an option to search by cluster name to quickly narrow down any particular activities relating to a particular cluster

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  5. Allow Pending Users to be Added to a Team

    When trying to implement Atlas infrastructure for Organization/Project users, the Teams functionality is useless unless we can add pending users to a Team. Right now, if a new user doesn't login for two weeks, we can't assign them to a Team until two weeks after the implementation was supposed to be configured.

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  IAM  ·  Admin →
  6. "Chaos testing" for Atlas - simulate node(s) down

    The current "Test Failover" feature supports testing application/driver resiliency in case of elections. For additional testing, we want to be able to cause a node or nodes to be shut down and started up in a cluster. There should be selectivity allowing the entire node or just the mongod or mongos process to be shut down and started up.

    33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  6 comments  ·  Other  ·  Admin →
  7. Support a broader range of 2FA providers

    Introduce compatibility with additional 2FA providers for Atlas customers, such as:
    - Authy
    - Microsoft Authenticator
    - Okta Verify
    - Duo

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Admin →
  8. LDAP configuration using Terraform

    We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.

    The functionality is available via the API:
    https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/

    However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.

    36 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  9. Cluster Termination Protection

    It is possible to quickly delete an entire cluster, for example through terraform, if you're not careful.

    It would be great to have a "Termination Protection" feature that can only be disabled in the Admin UI and not via the public APIs.

    In terraform I could then enable it like so

    
    
    resource "mongodbatlas_cluster" "my_cluster" {
      enable_delete_protection = true
    }
    

    When I would run terraform destroy the cluster should not be destroyed and instead the API returns an error saying that the Cluster has Termination Protection enabled. If I want to disable it, I can login to the Admin UI, select…

    66 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Other  ·  Admin →
  10. Allow to set teams to users by Federated Authentication

    When an Atlas User logs in by a Federated Authentication (like Okta) there is only a "Default User Role" to control its permission, so all users get the same role. And after that, we must manually add to teams, or change their roles. It would be better to allow the IdP to set (and update) the groups/teams for each user automatically.

    32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  IAM  ·  Admin →
  11. DNS

    In much the same way that Amazon RDS has a public/private setting, could you add a setting to Atlas that lets us make the DNS entries for our cluster resolve to their private IPs all the time instead of just inside a VPC?

    This would improve security by routing our connection through a VPN into a VPC that has a peering connection with Atlas' VPC. To accomplish this now, one must to find the private IPs of a cluster and create local, manual DNS entries in a router or on a machine.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Admin →
  12. Add 1 second granularity to ATLAS metrics

    At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
    reducing the granularity to 1 second would give more insight

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  13. Service status

    Well, my DB is down... I would like to have a link to a page where you list real time status of your services and if down, the current status of the ongoing fix

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Admin →
  14. Mongodb 4.2 pit_enabled argument on mongodbatlas_cloud_provider_snapshot_restore_job

    While version 0.4.0 of the MongoDB Atlas Terraform provider did introduce the pitenabled argument on the mongodbatlascluster resource, it does not appear that the mongodbatlascloudprovidersnapshotrestore_job was updated to be able to restore from a point-in-time.

    Currently, the option is available in the Web UI but there is no way to automate it via Terraform scripts.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  15. Enable the use of the timeouts { ... } block in resource declarations.

    Enable the use of the timeouts { ... } block in resource declarations. I consistently get a timeout error on destroy of resources:

    Error: error deleting MongoDB Private Endpoints Connection(5e4e93f3c0073240658e5b1f): timeout while waiting for state to become 'DELETED, FAILED' (last state: 'DELETING', timeout: 2m0s)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    The timeout on this resource has been increased (https://github.com/mongodb/terraform-provider-mongodbatlas/issues/151) and since then we’ve seen no reports hitting the timeout before completion of the deletion. If this is encountered again please file an issue at https://github.com/mongodb/terraform-provider-mongodbatlas/issues/ letting us know what resource is hitting a timeout, what version of the provider and terraform you are using, and any relevant logs.

    Thank you!

  16. Add a resource to configure the backup policy for Cloud Provider Snapshots

    Please add support to change the backup policy for Cloud Provider Snapshots.

    This is the API I am referring to:
    https://docs.atlas.mongodb.com/reference/api/cloud-provider-snapshot-schedule-modify-one/

    Thanks.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  17. Add Atlas instance in Azure Norway

    We host data that is preferred to reside in Norway. Do you have plans to expand to the newly added Azure Norway data center?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Other  ·  Admin →
  18. Add support for name as argument for the team data sources

    Currently, there is a datasource for team, but it requires an ID as argument.
    There are available APIs with look ups by ID but also by name.
    Can we support the data source look up by name as well? That would be interesting as could avoid knowing the ID of the project or team and look up that ID via name.

    Thanks.

    (Note Admin edit -> as project missing name as an argument was a regression that is corrected in v0.4.1. However team is still up for later consideration for name expansion so leaving for feedback.)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  19. Ability to create mongodbatlas database user with certificate X.509

    It would be great to have the ability to create mongodbatlas database user with certificate X.509 and get back certificate encoded or not in the output.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

  20. gsuite access

    I'd love to see better integration with google services as authentication provider. The current workflow of manually setting up the identity providers/domains in atlas & custom saml endpoints(even without a preset) is pretty complicated imo.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  IAM  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base