Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1359 results found
-
Surface hourly usage data and charges
Usage pattern can change very quickly throughout the day so a daily granularity of usage/cost is not sufficient for us to analyse usage behaviour.
We need a further granularity which is the hour by hour usage and charges in order to help us monitor cost and spot pattern/irregularities.
4 votes -
Backup Snapshot Distribution: allow to choose which policies should be copied to other region
Currently we can choose only a policy type (e.g. hourly, daily).
If we have multiple hourly policies with different retention times, we would like to choose which one should be replicated to another region. Currently it would replicate all the policies with hourly schedule.End goal:
We would like to setup a backup policy where the snapshots are retained in the secondary region for one day only (or less if we had hourly option), while the snapshots in primary region are retained for 7 days. For the same hourly schedule.2 votes -
OIDC Authentication Terraform Provider
Hi,
it should be possible to authenticate with a service account from Entra ID to MongDB Atlas with the Usage of OIDC.
Here is an example of this in azurerm: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_oidcpros:
- no password / private key needed
- no rotation of credentials needed1 vote -
Archival size
Currently the jobs archive only 1.93GB per run which restricts the amount of data archived per day . Is there any way to increase this limit so that it can archive bigger chunks in the scheduled window ?
1 vote -
Show warning when user is configured with access to invalid resources
When an invalid resource is specified in data plane user's access policy ("grant access to") authentication errors are misleading.
For Example: if user "John" is limited access to cluster "xo" but cluster is created as "x0" by mistake, when John is authenticated against "x0" we simply get "user not found error" in client.
If the Atlas UI can highlight the potential error, that cluster "xo" is not found, as cluster cannot be implicitly created. it will save valuable time for developers debugging entitlement issues.
2 votes -
Set project limits in AtlasProject CRD
It would be great to be able to set the project limits (API reference: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Projects/operation/setProjectLimit) in the Atlas Kubernetes Operator through the AtlasProject CRD.
Specific use case for us is the ability to set "atlas.project.deployment.privateServiceConnectionsPerRegionGroup" to tweak the number of PSC connections. Now we have to circumvent the operator to be able to tweak this value.
1 vote -
Higher memory hardware option in NVMe
By experience, an optimized MongoDB usually needs more IO and memory, so we can enable a horizontal scale during the live incident.
So a larger memory SSD would be preferred.
For AWS, eg. x2iedn or x8g(require to switch ARM) would be an option.1 vote -
Improve labeling experience in Network Access
I see option "add my current IP address in allow list" quite handy.
After I click that button there is no labeling option near.
I could use a search bar of browser to find a recent ip address but that is too tedious.I want labeling input just after added the address into allowed list.
One more cool option would be to choose a label color.
That way I can manage or distinguish all addresses/hosts simply in a instant look.
1 vote -
Add a Atlas control plane in UK region
Currently Atlas control plane IP addresses originate from your AWS us-east-1 region. With our region being UK, security team does not like request into our network originating from US.
Request a control place in UK region.2 votes -
Add boolean for applying changes only during maintenance window
Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.
E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.
See DocumentDB as an example for this feature.
https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html4 votes -
we can set up alerts in Mongo Atlas for the failed integration for datadog /slack etc\
If integration fails for any available third-party tool, we can get notified from Atlas Alert, which helps in saving any issues from metrics and 3rd party tool always functioning .
1 vote -
Show Mongos Connection Number in Overview.
Currently, the connection number shown in Overview is shard connection, it is the connection from Mongos to Mongod, which should usually be lower than the Mongos connection.
The connection limit for MongoDB is referring to Mongos connection which should be shown in overview or otherwise very misleading when we received connection % alert.1 vote -
We would need the GCP project number associated with a certain Atlas project
We would need the GCP project number associated with a certain Atlas project. Preferably we would need this integrated in the Terraform provider and in an API.
Having the GCP project number corresponding to a certain Atlas project would allow ACL creation with the various features provided by the cloud provider.0 votes -
mongodbatlas_cloud_backup_snapshot_restore_job
Add waitforcompletion field to mongodbatlascloudbackupsnapshotrestore_job to wait untile restore job has finished
1 vote -
In the Project Overview interface of Atlas, show users that the set of clusters is incomplete
In the Project Overview web interface, in the Clusters pane, four of our clusters are listed. I am new to our MongoDB deployment and to this UI. I had no way of concluding we had more than four clusters. I thought that was the complete list.
I feel strongly that if you are going to show only a subset of clusters in a UI, you need to also give users some visual clue that this is only a subset, that the list is incomplete, and that more can be found somewhere.
1 vote -
Auto downscale - Scaling down during peak moments
The auto downscale checks for the average of usage for the last 4h. But, sometimes we have a cluster with little usage for almost all the 4 hours, but at the last 30, 15 minutes, it starts to consume more CPU (something higher than 60% or even higher).
As the autoscale only checks at the last 4h it sometimes happen that a cluster does a auto downscale when it shouldn't. A litler time after it needs to scale back up because the usage goes higher than 90% (or at least higher than 75%)
It would be much better if the…
2 votes -
Configuring provider with shared credentials file for secrets manager
Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.8 votes -
Granular permissions needed with Federated Authentication in Atlas
Granular permissions needed with Federated Authentication in Atlas
For example(but not limited to), it would be good to assign to an external role, via Federated Authentication:
-to create RS users;
-to restore a RS.1 vote -
Alert When Cluster Nodes Not Regionally Fault Tolerant
If a cluster is not regionally fault tolerant, generate alert to associated email address(es). Since regional fault tolerance is typically only a concern in production environments, provide the ability to only alert on clusters that contain specific tag values. Also, it would be helpful to see the lack of regional fault tolerance as an icon in the console screen for the end user.
1 vote -
1 vote
- Don't see your idea?