22 results found

1. API - Version 2

   We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

   We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
   Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

   to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
   "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

   What I need to change is only the "instanceSize":"M10", but I need to use IN A PATCH all this other parameters. It doesn't make any sense to need to inform all of this if I'm using a PATCH (it is not a PUT, it should work fine receiving only what I'm about to change)

   It would be great if this could be fixed so it would work just receiving what we want to change, or at least just receiving the parameters that v1 needed.

   We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

   We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
   Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

   to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
   "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

   What I need to change is only the… more

   37 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable Terraform export of HCL for existing Atlas configurations

   Allow for a standardized export tool that outputs Terraform HCL from existing, manually provisioned Atlas resources (e.g., projects, clusters, users, role mappings, et cetera). This would be similar to GCP's Terraformer or Azure's Export for Terraform.

   10 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Improve Admin API for API keys rotation

   Given we have security mandates where we need to rotate API keys for an organization, every 365 days. It would be ideal if when calling
   https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Programmatic-API-Keys/operation/getApiKey

   getApiKey from admin api that it should return the created date. This way programmatically we can rotate keys and maintain security posture. As well if there was a way to just refresh the api secret and not generate a new one that would be a plus

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Improved deletion protection against malicious users

   Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).

   It would be good to have some less impactful way of protection against malicious users.

   For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days. This does not impact regular operation but also effectively prevents malicious users from causing permanent damage.

   Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).

   It would be good to have some less impactful way of protection against malicious users.

   For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days.… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Return 'CreatedAt' for Programmatic API keys endpoints

   We have an issue where we get emails from our internal Cybersecurity team 90 days after creating a MongoDB Atlas API key for rotation purposes.

   For other SaaS providers we're able to stay ahead of those emails by querying their APIs and getting the date at which an API key will expire or the date after 90 days of when it has been created. This allows us to rotate keys before emails from Cyber.

   The Mongo Atlas Administration API doesn't seem to provide that capability with the Programmatic access endpoints (though I am able to see the CreatedAt date in the UI). It would be great if this field could be returned in the response body for those endpoints.

   Endpoints:
   https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Programmatic-API-Keys

   Existing forum issue:
   https://www.mongodb.com/community/forums/t/get-org-api-key-creation-date/270594

   Related feedback ideas:
   https://feedback.mongodb.com/forums/924145-atlas/suggestions/48729215-improve-admin-api-for-api-keys-rotation
   https://feedback.mongodb.com/forums/924145-atlas/suggestions/43396818-api-key-expiration-date

   We have an issue where we get emails from our internal Cybersecurity team 90 days after creating a MongoDB Atlas API key for rotation purposes.

   For other SaaS providers we're able to stay ahead of those emails by querying their APIs and getting the date at which an API key will expire or the date after 90 days of when it has been created. This allows us to rotate keys before emails from Cyber.

   The Mongo Atlas Administration API doesn't seem to provide that capability with the Programmatic access endpoints (though I am able to see the CreatedAt date in… more

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Make the to delete indexes endpoint public

   In the Performance Advisor, the recommended indexes to drop are only avaible throw the cnsole. We would like to have this information available from the API.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Safe mode to pause non-essential changes

   I'd like to be able to put the cluster into a "Safe Mode" during an incident.

   For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I also don't want to have to know what changes are scheduled, I want to pause them all regardless.

   This would pause any scheduled or non-critical changes, like upgrades, building indexes, probably resyncs, etc.

   But it would keep running cluster-safety/health-supporting mechanisms like auto-heal, and probably backups.

   And it would put up a banner on the cluster so everyone else interacting with it knows that it's in safe mode.

   I'd like to be able to put the cluster into a "Safe Mode" during an incident.

   For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I also don't want to have to know what changes are scheduled, I want to pause them all regardless.

   This would pause any scheduled or non-critical changes, like upgrades, building indexes, probably resyncs, etc.

   But it would keep running cluster-safety/health-supporting mechanisms like auto-heal, and probably backups.

   And it would put up a banner on the cluster… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. BI connector host name via API call

   BI connector hostnames in the Atlas UI: https://www.mongodb.com/docs/atlas/bi-connection/ is not supported via API , Currently, customer has to manually copy and store the values to be reused by other applications. The customers are hoping to get these values in an automated way, for example with API calls or SDK.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Include “Tag” Field in the Cost Explorer API Response

   We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
   https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

   Background

   Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
   • Organization ID
   • Project ID
   • Cluster Name

   To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing us to categorize costs accurately.

   Challenge

   While the current CSV file approach works, it requires downloading, parsing, and managing files, which introduces unnecessary complexity and file management overhead. Including the tag field directly in the API response would allow us to streamline this process and avoid handling files entirely.

   Request

   We kindly request the addition of a “tag” field in the response of the API endpoint mentioned above. This enhancement will enable us to:
   1. Automate our cost categorization and reporting process.
   2. Eliminate the need for manual file parsing and management.
   3. We can calculate costs by department or application and use resources more efficiently.

   We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
   https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

   Background

   Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
   • Organization ID
   • Project ID
   • Cluster Name

   To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Option to prevent backups restores into particular cluster

    Today it is possible to accidentally restore backup into live production database. There is a "I confirm" dialog in the UI but it is not fool proof, plus when using terraform provider you still could do yourself harm.

    It would be nice to have an option similar to Termination Protection where I could mark a cluster that it should be impossible to restore backup into. If I want to restore backup into existing cluster I would have to turn the restore protection off. Or I could restore into a new cluster.

    Another way to do it would be to have backup restores possible only into a new cluster (similar to AWS Backup restores). That way you would never accidentally destroy your live production data by restoring old backup into existing cluster. In order to not break current functionalities this option could be turned on for the project. With the option off you could still restore into the existing cluster. With the option on you have to restore into new cluster.

    Today it is possible to accidentally restore backup into live production database. There is a "I confirm" dialog in the UI but it is not fool proof, plus when using terraform provider you still could do yourself harm.

    It would be nice to have an option similar to Termination Protection where I could mark a cluster that it should be impossible to restore backup into. If I want to restore backup into existing cluster I would have to turn the restore protection off. Or I could restore into a new cluster.

    Another way to do it would be to have… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Allow move jumbo chunks to admin users

    As an administrator I want to be able to move jumbo chunks by myself. Currently we are not allowed to clean the jumbo flag, so we need Support to do this.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Edit PSC connections

    Allow admins to edit existing GCP PSC networks -- currently, if a client wants to increase the number of IPs allocated in a PSC, they have to increase the limit, delete the PSC, then create a new PSC.

    In a Production environment, this can cause 2 hours of downtime while reprovisioning PSC IPs that don't need to be provisioned, rather than scaling the number of IPs in-place.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. There is no way I can delete my account.

    There is no way I can delete my account. It says I have to get rid of active organizations. When I try to get rid of my organization it says I have to get rid of my active clusters. When I try to get rid of my clusters. In clusters page it says I have no clusters.
    I tried to sign out and wait but the same problem continues.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Not even able to close my free account

    Hi I have opened my free account and now i am not able to close this account. Even there are no available clusters showing on my account then also Project0 is not getting deleted. kindly help to close

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. API change date format for log download

    While programming a script to download the activity feed and audit logs, we found out that the date format which is accepted for API calls does not match. While the Activity Feed is fetched with a date in the ISO 8601 format (&minDate=2024-01-24T12:30:06.415944), the audit log accepts only an epoch timestamp (...?endDate=1702632210&startDate=1702625017).

    This causes several conversion issues when automating log-fetching. To avoid these issues, we suggest changing the API call to use the same date format.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Sync Atlas alert configurations between projects.

    Since we can export all Alert configurations from a project, add the ability to sync alerts on all the projects to be consistent with notifications/alerts.

    Alerts can be created individually but not in bulk. Please enhance the Mongo Atlas API for the following functionalities:

    • The ability to sync all alerts from one project to another.

    Thank you

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Manage authentication tokens in account overview

    When using Atlas CLI, you need to authenticate your account so that you can access the organisation/cluster. Unfortunately, there is no way to manage a list of previous authentications in your account settings.
    This is important in case you are working on a machine that you have no control over and don't have a change to start the logout process from Atlas CLI on the machine you logged in.
    A central UI that would allow to revoke previously granted access would be very helpful.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Administration API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Add search nodes to /processes API endpoint

    I am trying to auto scale my search nodes based on CPU usage.

    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Monitoring-and-Logs/operation/listAtlasProcesses does not list search node processes

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Add search nodes to /processes API endpoint

    I am trying to scale my atlas search nodes based on CPU usage.

    https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Monitoring-and-Logs/operation/listAtlasProcesses only lists processes for the regular atlas cluster, no search nodes are listed.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Atlas API access to discover Parent Atlas Organization cascading access into Service Now
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating