Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
Share API key cross organizations
Today, it's not possible to share an API key between different organizations (https://www.mongodb.com/community/forums/t/sharing-api-key-between-different-organizations/190785/13)
It makes it impossible to restore snapshots from one organization to another automatically.It's very important for us, as we need this feature to clone our customers clusters into our organization
16 votes -
Allow access to Admin API using AWS IAM role
It's possible to authenticate to a database using AWS IAM role. The same should be possible for the Admin API.
The problem with the API keys is that they can be taken away and used elsewhere. They pose an additional risk in an AWS integrated environment.
This also relates to upcoming Cloudformation Resources where the extension needs to store the API Key in AWS Secrets Manager. The resource already has a role that could simply be configured to be trusted on the Atlas side.
2 votes -
Improve OpsGenie alert mis-categorization
We noticed that alerts sent to Opsgenie using the Integrations is using "https://api.opsgenie.com/v2/alerts" URL, which causes Opsgenie to mis-categorize the alerts for all customers, according to Opsgenie themselves.
Issue re-production steps:
* Create a team in Opsgenie or use an existing team (use a team that is NOT used for the Default API integration)
* Create a MongoDB integration in that team and take note of the API key
* Create an Opsgenie Integration in MongoDB and use that API key
* Generate an alert or Test the integration
* Verify in Opsgenie that the test alert did…1 vote -
storage autoscaling at N %
Dear Mongo Team,
Your engineers advise to add more storage to the clusters when it reach 80 % usage as this is when performance degradation can occur. At the time of writing the autoscaling happens at 90 % disk usage. We want to be able to adjust at what % of usage the autoscaling happens and set it to the value of 80 % basically what your engineers advise.
10 votes -
Don't overwrite explicitl role with default organisation role configured in identity provider
we have user created in Atlas on Organisation level with specific org role. If we configure Identity Provider and set some default role, then after first login this user will receive this default role and original role will be lost. So, even after disabling identity provider, user will have this default role.
Suggestion: explicitly granted roles should be keep untouched, but not be applied in case of active identity provider.
1 vote -
Alert when database user is created or removed
currently there is no alert option for database users
13 votes -
BLACKOUT Period to avoid outage
set up blackout period to avoid sending those alert while performing any index rebuilding in a rolling fashion or disk expansion activity ?
1 vote -
Additional metadata for alerts through the API
The lack of metadata is blocking us from having parity with opsmanager on our production alerting capability. Currently, when some alerts come through the API, there is no information to parse so you can't tell where the issue is happening. Even adding just the cluster would be helpful. As of now there is so little information that alerts using the data dog integration are worthless.
1 vote -
Create Atlas App Services and Link Them To Clusters with Terraform
It would be great to create App Services (Realm Apps) and then create the service link to an Atlas Cluster with Terraform.
This is so that Trigger resources can be created fully within Terraform, rather than having to hack together API calls, CLI commands or manual steps.
5 votes -
Adding indexes(Not search index) using terraform
I would like to create mongodb atlas index using terraform. But as of now we can able to create search index in mongodb atlas using terraform. here the expectation is to create normal index using terraform.
15 votes -
Can you add support for storing the archive data in GCP cloud storage?
The Cold Storage (Archiving) is available only in AWS S3 as of now. Can you please make it available in GCP cloud storage to move all the MongoDB archives?
14 votes -
Ability to restore a single database on a cluster
Hello,
The Atlas portal/API offers the ability to restore a complete database instance from snapshot or restore point. However the scope of this restoration covers the entire instance.
It would be a great asset to be able to restore a simple database from snapshots (encrypted or not). Currently, restoring a database (not a cluster) is a heavy workload that requires outputting data to a local workstation.
Thanks.
10 votes -
Copying gbs of collection data from one project to another project
Currently it is highly time consuming process of copying a 100gb collection from one project to another project. There is no faster and proper way of copying the data. This feature is highly needed. Because each environment resides in different projects. If someone want to copy only handfull of collections from one project to another(dev to prod and vice versa) then its a nightmare for doing this kind of job. Tried mongomirror and mongodump feature but those are not quite impressive.
1 vote -
GCP eu-southwest-1 Madrid Atlas region
Would love to deploy the cluster in the recent GCP eu-southwest-1 region. It is already running, and would be a plus for all Spanish customers reducing latency. It does not yet appear in the Atlas cluster creation page.
2 votes -
1 vote
-
Get all databases from one cluster
Add a new Admin API to Atlas: Get all databases from one cluster
2 votes -
Add option to "Explain" a query from the "Profiler" page.
The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.
2 votes -
Copy/move snapshots from a source to a target cluster
It is recommended that restoring a cluster must either:
1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
(src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.
We would like to take the safer route of…
3 votes -
AWS CMK rotation alert should be changed from 90 to 365 days
Originates from https://github.com/mongodb/terraform-provider-mongodbatlas/issues/805#issuecomment-1241569555
Short: The created default alert for encryption key rotation is configured to 90 days, also when using AWS KMS CMK. The automatic rotation for CMK is 365 on AWS side. So, I would vote for creating the default alert with 365 days, when AWS KMS CMK is selected.
Otherwise we get false alerts, as we rely on the automatic rotation of AWS KMS.
3 votes -
Add Terraform resource for functions
Would be great to have a terraform resource like mongodbatlas_function.
Was mentioned here https://github.com/mongodb/terraform-provider-mongodbatlas/issues/828 but I didn't find the idea mentioned there, so I added this one here.18 votes
- Don't see your idea?