Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
- or
1371 results found
-
Support for CDK SAM Template in Publishing Serverless Applications in AWS
I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.
Error Message:
Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]
While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for seamless deployment and publication processes.
Thank you for considering this feedback.
I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.
Error Message:
Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]
While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for…
1 vote -
Allow Organizations without a Subscription to have linked organizations
Currently, to be able to link organizations to a single paying organization (ie. linked organizations), it requires an active (paid) subscription.
My use-case is that we have an enterprise subscription on our production organization, but wish to have a sandbox organization to test infrastructure as code, creating/deleting sub-organizations, and linking API keys.
In my opinion, developers / administrators should be able to test out managing the org structure in a separate account without affecting the primary "root" paying account structure.1 vote -
Always show an option for both SRV Connection String and Standard Connection String
There are more than a few examples where users DNS does not resolve SRV Connections strings. They are often directed to select an old version / legacy connection string.
Two issues with this are:
1. Sometimes outdated/deprecated options are provided (ssl=true)
2. Serverless does not provide this.1 vote -
Azure VNet terminology needs updating
Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.
Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.
The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name
Currently:
Directory/Tenant ID
This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active Directory / Properties. Show Instructions
Navigate to Azure Active Directory / Properties. Your Directory/Tenant ID is shown under Directory properties.
Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.
Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.
The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name
Currently:
Directory/Tenant ID
This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active…
1 vote -
Terraform provider should handle pagination for mongodbatlas_atlas_users resource
The resource mongodbatlasatlasusers limits results returned by page with a default of 100 and max of 500. Attempting to retrieve a complete list of users where that list is not a known size isn't possible because of Terraform limitations on dynamic blocks. It would be quite helpful if the Terraform provider handled pagination and this resource by default returned a complete list.
1 vote -
Customer feedback around the UI of Atlas - unable to edit multiple documents at once
The customer wanted me to provide product feedback around the inability to edit multiple documents at once from the Atlas UI. The customer uses a 3rd party tool to do this instead and thought it would be better and more intuitive if this was built right into the Atlas UI.
1 vote -
More Granular Node Read Preference Tags
I would like the ability to set tags on individual nodes so that I can change the read preference with more granularity.
Mongo supports these tags on non-Atlas deployments: https://www.mongodb.com/docs/manual/core/read-preference-tags/#std-label-replica-set-read-preference-tag-sets
Analytic Nodes are very useful, and they are built as way of isolating workloads. The problem is that you can only really isolate into two different buckets (well three if you consider local read nodes). What I'd like to do is isolate more than two different sets of users and queries, so say user reporting and internal dev activities have their own sets, and they work independently.
You could kind of achieve what I want, by just letting me configure multiple sets of analytic nodes and then give each one a custom name, that appears as a tag, that I can use the readPreferenceTags option to select: https://www.mongodb.com/docs/v3.0/reference/connection-string/#uri.readPreferenceTags
I would like the ability to set tags on individual nodes so that I can change the read preference with more granularity.
Mongo supports these tags on non-Atlas deployments: https://www.mongodb.com/docs/manual/core/read-preference-tags/#std-label-replica-set-read-preference-tag-sets
Analytic Nodes are very useful, and they are built as way of isolating workloads. The problem is that you can only really isolate into two different buckets (well three if you consider local read nodes). What I'd like to do is isolate more than two different sets of users and queries, so say user reporting and internal dev activities have their own sets, and they work independently.
You could kind…
1 vote -
Stop scamming your users
How about you stop scamming your users with deceptive instruction on your download pages.
1 vote -
Terraform Downward Autoscaling "Use Smallest possible" placeholder
When setting "providerautoscalingcomputemininstancesize", is it possible to either;
- Loosen the validation by ignoring current disk configuration size.
- Create a placeholder to indicate "Use smallest possible value".
Atlas appears to support invalid values, provided it was entered when it was valid.
I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
1. I define an M30 Cluster with a Disk Size of 64gb and a minimum Cluster size of M10 through Terraform.
2. The Cluster's Disk Size is scaled to 129gb
3. Time passes.
4. I execute/run my previously valid Terraform definition, Terraform returns a validation failure.
This matters to us because it would simplify our MongoDB operations. "providerautoscalingcomputemininstancesize" is a parameterized value where, if empty, we use an instance size of M10. Having the deployment fail unexpectedly when updating/creating a cluster can be a frustrating experience (Especially when people do not read error messages).
When setting "providerautoscalingcomputemininstancesize", is it possible to either;
- Loosen the validation by ignoring current disk configuration size.
- Create a placeholder to indicate "Use smallest possible value".
Atlas appears to support invalid values, provided it was entered when it was valid.
I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
1. I define an…1 vote -
serverless concurrent connection limit
Increase to the 500 concurrent connections hard limit so that we can use this in a production domain service. We would also need connection pooling / proxy as described in another idea.
1 vote -
Restore a snapshot from one organization to another organization via API call
I have tried to create automation to restore the snapshot from One organization cluster to other organization cluster. Example Prod cluster from Organization A -> Stage cluster from Organization B.
currently this method is not possible to restore a snapshot from one organization to another organization via API call as API key cannot be shared over the scope of different organization.( As per mongo atlas support Engineer)
Please enable this feature to automate the snapshot restore instead of using UI for restore.
1 vote -
Analytics node with NVMe option
We currently have use mongodb mainly to correct data and visualize with chart features. Some chart require heave disk read operation and need more performance. We need fast storage access only for analytics nodes. If we can select NVMe option only for analytics nodes, we use it but we don't want to switch whole clusters to it since main cluster don't need higher cpu/memory/stroage/iops. We just want to use NVMe only with analytics nodes. Some restriction such as min storage size for main cluster is acceptable but don't want to upgrade to higher tier of main cluster.
1 vote -
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
1 vote -
View all documents in a collection on Atlas UI
The current limitation in Atlas restricts viewing documents within collections to a maximum of 200 per view. It would be beneficial to have the functionality to scroll through all documents without encountering the message: "To view additional results, connect to your cluster using the mongo shell."
1 vote -
Make IP linking easy for Atlas customers deployed on Google Cloud
I know it may not seem MongoDB's responsibility, but understanding how to get IP addresses for my Google app engine services so that I can put them in MongoDB (which for some reason wants IP addresses instead of URLs) it's difficult. If MongoDB wants to sell to Google Cloud customers they should make it easy to set up, not only for the billing.
1 vote -
Define the secret name for the connection string output from the operator
Hello all, instead of using a predictable naming convention for secrets:
$project-$cluster-$username
I'd like to be able to nominate the output secret name similar to how crossplane does this.
More details found at the Github Issue: https://github.com/mongodb/mongodb-atlas-kubernetes/issues/1369
1 vote -
automatic upgrade
Forced automatic major version database upgrade.
When there is an extension the automatic database upgrade, remove the banner that says it is going to upgrade at the previous date. This is confusing and unnerving as it looks like it is going to upgrade.
1 vote -
Default Maintenance Window to Out of Hours
With Atlas MongoDB, maintenance windows when not defined default in many cases to periods during peak hours. With maintenance such as automated rolling upgrades, this can impact performance. I would suggest defaulting this to a time overnight relative to the hosted region of the cluster.
In addition, there appears to be no obvious way to see what the maintenance window is without inspecting automated updates in the Activity Feed. If this is the case, adding it to the interface would be useful. Note that even toggling the manual setting of the maintenance window to on will default to the first items in the drop down boxes as opposed to the actual current maintenance window.
With Atlas MongoDB, maintenance windows when not defined default in many cases to periods during peak hours. With maintenance such as automated rolling upgrades, this can impact performance. I would suggest defaulting this to a time overnight relative to the hosted region of the cluster.
In addition, there appears to be no obvious way to see what the maintenance window is without inspecting automated updates in the Activity Feed. If this is the case, adding it to the interface would be useful. Note that even toggling the manual setting of the maintenance window to on will default to the first…
1 vote -
CDK L3 Resource for Atlas Streams Resource
Would help my organization get started faster with Atlas Streams Processing
1 vote -
Start/Stop Atlas instance from external script
Currently the ability to stop or restart an Atlas instance is not allowed from the customer's side of things, and is an action that can only be performed by MongoDB Support.
We would like to have this feature added.This use case very important for our organization as different application teams should be able to bring up or down the database as they need.
We cannot grant permissions on Atlas console to all the teams in our setup.
Instead, we may have a custom script developed using Javascript or similar scripting languages and enable users to start or stop Atlas instances from a front end, something like chatbot.We have successfully implemented this for other RDS instances like AWS Aurora.
However not able to do the same for MongoDB Atlas instances.Hope such features get added to MongoDB Atlas at the earliest.
Thanks for your support.Currently the ability to stop or restart an Atlas instance is not allowed from the customer's side of things, and is an action that can only be performed by MongoDB Support.
We would like to have this feature added.This use case very important for our organization as different application teams should be able to bring up or down the database as they need.
We cannot grant permissions on Atlas console to all the teams in our setup.
Instead, we may have a custom script developed using Javascript or similar scripting languages and enable users to start or stop Atlas…1 vote
- Don't see your idea?