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

As per the title, add a new CFN resource MongoDB::Atlas::PrivateEndpoint to manage PrivateLink interfaces into Atlas, based on https://docs.atlas.mongodb.com/reference/api/private-endpoints/

Atlas does not currently allow to change the default write concern at the cluster level.

It it necessary to have a possibility to change it in order to avoid or minimize rollbackfiles during failover.

It would be interesting, Atlas could also be monitored via SNMP, in order to be monitored by Zabbix.

Many companies have their own CommandCenter, where they centralize monitoring in a single tool.

Getting onto Mongo and learning it the first step in getting to use it for projects and in production.

I am finding that there are many roadblocks to installing and connecting to Mongo.

Getting a standalone mode would make it super intuitive to connect with it and begin using it.

In the comparison between clusters, for Shared clusters M2, M5, vital information is that there are data limits and those limits are shared, not only for you but also together with any other databases of the same cluster.

This was NOT clear at all when we signed up with an M2.