Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
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 -
Atlas Activity feed flooded with Data-Explorer read-only operation events
As a user I find the Activity Feed overwheliming and want to be able to filter events more granuralry
3 votes -
Compact mode for browsing documents
Could we have a compact mode to view the documents in a collection?
I would enjoy a table-like view, with much less padding, and a column with actions.3 votes -
Expose more data via the Project Events Atlas API: database user addition
The project events API (described at https://docs.atlas.mongodb.com/reference/api/events-projects-get-one/)
returns less fields that presented in the UI.For example, after adding a database user via API, I would like to wait for the database user actually added before attempting to use the user. In the web UI, I see 2 events with all the information I need - "MongoDB user added" and "Deployment configuration published".
When querying the project events API, I see both events (event types MONGODBUSERADDED and AUTOMATIONCONFIGPUBLISHED_AUDIT), but there are no additional fields with the new database user.
3 votes -
Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs
Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.
This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…
2 votes -
(RBAC) Remove CREATE_COLLECTION grant from INSERT permission
In according to the least privilege principle we would like to have a better granularity when defining roles. This feature would help us to have uncontrolled collection creations by applications
2 votes -
Setup the Atlas web user's team membership as part of the invitation.
Doing so, removes the extra step of assigning the team after the user has accepted the invitation.
2 votes -
Support for VPC Lattice
Additionally to the existing VPC PrivateLink Endpoint method to have connectivity it would be great if I could integrate a MongoDB Atlas project via a VPC Lattice service and share that one with customer accounts on AWS. - Red Bull Media House
2 votes -
add cluster manager email
Hi,
It would be nice to be able to assign a cluster manager email / contact per cluster and not per project. We have different team members managing different clusters within each of our projects and it would be great if we could alert them specifically on specific events in a cluster (like new index suggestions, disk increase, etc.)2 votes -
Display a cluster tier size (e.g. M20) on the all Clusters page
I am opening this new feature request on behalf of the customer. Would it be possible to display a cluster size (e.g. M20) on the main status page alongside other cluster information that's already on the page?
2 votes -
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…
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…
2 votes -
Migrate specific collection / database from a replica set to sharded cluster(not empty) without downtime.
It would be great if MongoDB has a tool to migrate specific collections/databases from a replica set to sharded cluster and vice versa. Migrating data with this tool should not cause any downtime in both source and destination clusters.
2 votes -
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 -
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 -
2 votes
-
Lock a user account
We have an occasional need to disable/lock an individual database user. Either because of a run away process or inactivity. We do not want to change the password or drop the user as we may need to reenable the user quickly with the same permissions and password as before.
2 votes -
Feature: Atlas UI -- Star/Favorite/Bookmark of Project
It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search
2 votes -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes
.png){kind=link}
- Don't see your idea?