Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
435 results found
-
Adjust the Blue Mode into the actual Dark Mode
Thanks a lot for the newly added "Dark Mode", it looks awesome. One suggestion would be to shift the blueish tone to a more grey tone instead. As we know blue light disrupts sleep :)
1 vote -
Support the unlimited mode for t3 AWS instances (M10 and M20)
We use M10/M20 instances (AWS backend), which accumulate CPU credits over time. The problem is that when Atlas nodes run out of CPU credits, performance goes down and we see a lot of CPU steals. This is a common issue with AWS EC2 instances. We would like to have an option within Atlas UI (a tick box perhaps) to enable the unlimited mode for t3 instances (M10/M20).
1 vote -
Sign Up Process Security
I have recently signed up for a developer account. I have used a Microsoft email address during registration. As soon as I submitted it, I have received an account login MFA message from Microsoft indicating that someone is trying to sign into Microsoft with it. I obviously used it to just register with Atlas as an ordinary email address. Being security savvy, it indicated a red flag. There is a potential that your registration system is compromised (hacked) by a malicious actor. Please forward this message to a security team.
1 vote -
Ability to create mirror/snapshot clusters for load and behavior testing
We would like to request the following:
- The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
- This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
- The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
- The mirrored cluster should be allowed to…
1 vote -
Manage Feature Compatibility Version (FCV) flag separately from version upgrade
When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.
We would like to see this be a two-step, i.e.
1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.
We understand that some users don't care about…
1 vote -
Enforce MFA for google login users
Our organization needs to enforce MFA for users signing in with google login. Is there any way to do it other than "Require MFA"?
1 vote -
Retrieve latest/max oplog timestamp via the Atlas Administration API
At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.
For example, in the UI it states:
You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.
Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.
2 votes -
Change global default compressor setting
Hello,
I wanted to request a feature that would enable us to change the global default compressor setting ourselves? Something that could possibly be exposed on the Advanced Configuration settings page in Atlas? We're looking to re-compress our existing collections usingzstdfrom the defaultsnappyoption and we want to create future collections using thezstdblock compressor automatically.Today, we have to create a support ticket and co-ordinate with them. It would be great if we could have this feature on the Atlas portal so that we can monitor the progress and trigger it whenever we want to…
1 vote -
Hyperlink to "all cases" that's under the "create new case" link
To access the support portal from the projects page:
- Navigate to Support to the left side of the page
- Click on Visit Support Portal button under Request Support
It will be easier to navigate if a hyper link of "all cases" can be added to "create new case" from the "get help" drop down as in screenshot attached.
2 votes -
Remove the requirement to have an API Access List CIDR before being able to manage backup schedules
The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952
Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedulesOur request is that the requirement to have an API Access List to manage backup policies be removed.
At the very least,…
3 votes -
Google Private Service Connect
Greeting from Fivetran!
This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.
From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed to AWS…
2 votes -
List user id in access screen, needed for project owner id in when setting up a project inpulumi
As title. I want to easily find user IDs from teh Atlas UI
1 vote -
CORS on the Atlas API
The Atlas API does not yet support CORS. Without CORS, calling the API from within a browser, using a React Client, for example, fails the 'preflight checks'.
"...has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource...."
If the Atlas API could add the 'Access-Control-Allow-Origin: *in the header response, then browsers would permit the API to be called.
Note: for the pre-flight check, the browsers call the OPTION method.
1 vote -
Activate bypass saml only for select users
We have recently activated SAML SSO on our Organization and we would like to only have 1 user that is able to bypass SSO as like a "break the glass" user in case our IDP fails. It would be ideal that not every user is able to use the bypass url.
Currently any users can use the bypass sso url
2 votes -
Set Customer Managed Key (CMK) for wiredtiger encryption at the Organization level
For Organizations with a large number of projects, it is cumbersome to rotate keys for every project. If there was an option to set a default at the Organization level, and maybe override by CMKs set at project level, it will reduce the effort of key rotation for every project.
1 vote -
Enhanced Access to Secrets in the context.environment Object
We would like to see an improvement where secrets can be accessed as environment variables directly through the context.environment object. For example, if we have a secret called myApiKey, we would like to be able to access it in a function using context.environment.secrets.myApiKey.
This would make the process of storing and accessing environment-specific sensitive data like API keys, access tokens, etc., much more straightforward and error-proof.
As it stands, we're creating a workaround by saving env specific API keys as secrets, and then using some logic with context.environment.tag to fetch the correct environment API key. However, this approach is not…
2 votes -
Hello, I had a superb consultative experience with Colin Phillips. He assisted me with understanding support options for a website database
Colin Phillips provided superb and outstanding help to me with the next steps for realizing my dream project.
With Gratitude, Amilcar1 vote -
Code support
Your website is a monster where is very difficult to get the useful information.
I wanted to use Realm to use a mongo cluster and after hours trying I give up.
I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)Solution: Let's say I have a single cluster and a single realm app created.
Just give me the code with all the ids necessary.In my case I wanted to run it from the browser.
This is the code I tried to execute:
…const app = new Realm.App({ id: 'tradeapp-bozmd' }); const1 vote -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
1 vote -
Monospace font for Atlas project user creation fields
When you start a new project using Atlas, a username and password are suggested. The username and password fields use a font with almost identical lowercase L and capital i.
My suggestion is to use a monospace font in those fields for disambiguation.
I use a password manager on my phone (as do, I imagine, many others), which means it’s very annoying to have to figure out if a character is an l or an I on the computer every time I have to copy down info for a new project.
1 vote
.png){kind=link}
- Don't see your idea?