Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
470 results found
-
private link - common dns suffix
when creating a private link, the resulted dns for the cluster is in the form of "cluster-pl-.{somerandomstring}.mongodb.net"
the only difference from the public endpoint is the 'pl' addition in the first section.in order to configure the vpn wildcards and rules,
it can be extremely helpful to have this separation more general, for example
cluster.{randomstring}.pl.mongodb.net -- private links
cluster.{randomstring}.mongodb.net -- publicthat way we can use the wild card *.pl.mongodb.net to differentiate and route the traffic accordingly
2 votes -
Terraform for LDAP user/groups
We'd love to be able to create LDAP user and group accounts in Atlas via terraform. The existing mongodbatlasdatabaseuser resource doesn't support LDAP, so we are forced to use the API to create those users and groups.
3 votes -
support
Being unable to lodge a support ticket without paying for a support plan - when we are paying for a premium service is seriously f'ed up
1 vote -
It would be useful to have an ability to pragmatically keep up to date with the latest prices in a RESTful fashion.
Something like /offerings/aws/compute/M10 returns:
{
// some metadata about this pricing api.
"prices": [
{
"priceId": "c800b6d9163b0db7",
"region": "us-east-1",
"charges": {
"compute": {
"price": 0.11,
"interval": "hourly",
"currency": "USD"
},
"storage-GB-month": {
"price": 0.015,
"interval": "hourly",
"currency": "USD"
},
"backup-GB-month": {
"price": 2.5000000001,
"interval": "hourly",
"currency": "USD"
}
}
}
]
}Use case: For those that use programs to calculate costs, this will reduce some of the guesswork involved by looking at cryptic documentation and invoices to calculate and forecast costs and be able to charge appropriately to match systems with demand.
Amazon has similar API endpoints available:
https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json…
3 votes -
mongorestore
As per the mongorestore
- to preserve UUID must use drop collection
- if the collection is dropped then it will affect user/login access.
This cascading effect makes it's impractical to use. We wanted to use mongorestore UUID as an idempotent operation, in case halfway things go wrong and have to start again then it's useful to preserve UUID.
Also, in the mongorestore there should be an option to ignore/skip index creation, we were trying to bring data from the legacy app without indexes. It seems that's not possible at this moment.
1 vote -
default country
When I tried to register for Atlas webinar, host country selection was mandatory. By default it displays the USA first value in the dropdown and have to scroll down to select another country. It would be a good user experience if on the registration page visitor/user's country is identified and by default selected, this will prevent unnecessary scrolling.
Also, a very annoying thing is that in order to register for the webinar have to agree to subscription. Subscription to email and other notification should be optional, otherwise, it's a bit dodgy tactic more suitable to some social media companies who…
1 vote -
Terminate existing connections from IPs when removed from the whitelist
When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be…
4 votes -
CLI for working with atlas
Revive this tool https://github.com/ralphcapassomongo/atlas-cli and create a formal CLI for working with Atlas in the command line.
3 votes -
Expose oauth apps to let other services integrate with Atlas
Expose oauth apps to let other services integrate with Atlas, this way other platform can integrate with atlas for provisioning a mongodb instance.
It would allow for a lot of opportunities for developers like automatic mongodb provisioning for a deployment platform
Right now if you deploy with platforms like Zeit or Heroku you have to create a mongodb database and whitelist the right iP manually
1 vote -
Give an option to pause the cluster as a parameter, at the moment it is auto activating after 30 days of cluster pause which is not required
Give an option to pause the cluster as a parameter for specific duration of time, at the moment it is auto activating after 30 days of cluster pause which is not required for all the users and manually we have to keep an eye on this at the moment.
6 votes -
Make a more realist design, with hack themes, and fancy UI
Please look at the images, try to make similar UI, it would improve a lot the productivity
1 vote -
Show billing amount on top all the time
Would be nice if I can see my current billing on top all the time, even in Atlas, like it used to be before UI change. Thanks.
1 vote -
Support multiple LDAP servers and TLS connection options
When integrating my Atlas project with an LDAP service, we want to specify multiple LDAP servers rather than just one, and to specify options for the TLS connection such as allowing invalid hostnames. Both of these can be done in self-managed MongoDB Enterprise.
1 vote -
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
8 votes -
Make use of lazyloading, and use dynamic frontend components
The cloud atlas frontend is very buggy, and not usable at all, even with a fast connection takes minutes to load a page on click.
I think we are loading all the components and required data from server side.
Instead we can simply load the core components, and show a user friendly spinner, that will stop spinning once content is loaded via an XHR request. This would be so much more user friendly, just showing them a spinner (maybe estimated time as well).Currently the page stays blank white, which is terrible UX.
1 vote -
Project Homepage / Ability to add descriptions to Atlas projects
We have a lot of Atlas projects in our org, some are outdated, unused, orphaned, some important and used for production. It would be great to have a way to describe what each of them are for, who to contact for questions, etc.
For example, when you switch to a project, you land on the project homepage that has the description right there, alongside an overview of how many clusters, users, last change, if whitelists are enabled etc. Even better if I can use Markdown or some other "rich" editing experience to create the description and add links, bullet points,…
2 votes -
mongodb compass
a faster mongodb compass installation that is taking forever to do so.
1 vote -
Stitch email translations
The Stitch confirmation and reset password emails for the Email/Password Provider are now only in English.
A page where you could translate these emails, would be very useful.
Now we must use the function method, which is more work. I suspect a lot of people would want this feature (all non English markets).
1 vote -
Allow me to pay for a month of "developer" level support without committing to a subscription
AWS lets you pay for a month of support at any time.
My understanding of MongoDB support is that if you discontinue support and then start again a year later, you have to pay for all the interim months.
Another way of doing this would be to pay per-incident. I like the monthly model better because it would work for people just getting started to ask a lot of questions.1 vote -
Zapier Integration
Currently The Mongo Atlas connection string is not supported by Zapier! What??
1 vote
- Don't see your idea?