We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
"OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?

Hello,

after a discussion with a MongoDB architect during a consulting day, the rename of a database was possible in previous version of MongoDB but now, it's impossible without a dump / restore process.

We don't want use a dump/restore process to rename a database because it's use a lot of time.

Could you tell me why this feature was deleted ? and will it be possible in a future MongoDb version ?

thanks.
regards,
David.

I really need to delete my account as this is not what I am looking for.

I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.

As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.

It would be useful to add support for certificate selection.

It would be great to have the option to save Atlas backup snapshots without indexes. When using TTL indexes, when the data is restored, it is automatically removed because it is expired. Being able to create snapshots without indexes would save a lot of time to the current workaround.

on behalf of the customer,
would be great if we could allow tags on Org/ project level for cost allocation reasons (similar to how AWS allows this). When creating a project we can eg. add the type of environment, cost centre, bearer etc - without it showing up in the name. Does not necessarily need to show up on the invoice but we must be able to create a view which includes this info.

Currently, the profiler search is for namespace.collection_name. If I would like to see how all collections for a given namespace or DB are behaving it's a very tedious task and not user friendly at all.

Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.

Some examples of where this would help:

• After creating a restore job, waiting for the snapshot download URL to be ready.


• After modifying the automationConfig, waiting for all agents to report that they're in goal state.

I would like to give colleagues the ability to manage Database Access and Network access for a project without giving the the project owner role.

A way to provide more granular access in Atlas would be nice

We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.

Allow auto-scale for IOPS.

add more IP ranges for VPC peering on Google GCP network in Google Cloud environment. https://cloud.google.com/vpc/docs/vpc#valid-ranges is supported. Docs only show RFC1918 IPs. https://docs.atlas.mongodb.com/security-vpc-peering/#in-configure-your-network-peering-connection-2

It would be good to see Log Redaction work in Atlas as well, similar to On Prem
https://docs.mongodb.com/manual/administration/monitoring/#log-redaction

Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.