Geoffrey
My feedback
160 results found
-
18 votesGeoffrey
supported this idea
·
-
54 votesGeoffrey
supported this idea
·
-
41 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
shared this idea
·
-
3 votesGeoffrey
shared this idea
·
-
4 votesGeoffrey
supported this idea
·
-
12 votes
An error occurred while saving the comment Geoffrey
supported this idea
·
-
5 votesGeoffrey
supported this idea
·
-
6 votes
I'm excited to announce that we recently released tags on database deployments.
https://www.mongodb.com/docs/atlas/tags/
Tags on projects is coming soon! If you want to be one of the firsts to test out tags on projects, let me know!
An error occurred while saving the comment Geoffrey
commented
I'm not familiar with AWS, but on Azure, all components have the possibility to add tags
An error occurred while saving the comment Geoffrey
commented
The visibility and management of tags/labels allows us to add information specific to our organization. We use this information for different use cases.
Examples:
-> Categorize a data asset (Availability, Integrity, Confidentiality) Tag: DIC=444. This allows us to identify if the asset is configured correctly.
-> Owner of a data asset. TAG: Owner = Individual Insurance; Contact = John Smith
-> Last Compliance Auditor Check: TAG: Compliance=2022-02-22; Listener = William Smith; Status = Passed
-> Associated system name
-> Cost center TAG: BillTo=CCCC-111232These are just a few examples that we do with the use of tags/labels. Having it at the API level is handy, but having it at the UI level would be EXTREMELY helpful.
Geoffrey
supported this idea
·
-
15 votesGeoffrey
supported this idea
·
-
3 votesGeoffrey
supported this idea
·
-
4 votesGeoffrey
supported this idea
·
-
2 votesGeoffrey
supported this idea
·
-
8 votes
An error occurred while saving the comment Geoffrey
commented
Hello MongoDB,
We have a problem last week with Encryption at rest. MongoDB was not able to reach our Key Manager on Azure even it was available. MongoDB decide to shutdown our cluster for 3 hours. Do you plan to prioritize this feature request. Dont have this can compromize the usage of MongoDB in production.
See ticket: 00859378: Encryption at rest using Key stored in KeyVault failed
Geoffrey
shared this idea
·
-
9 votesGeoffrey
supported this idea
·
-
29 votesGeoffrey
supported this idea
·
-
5 votesGeoffrey
supported this idea
·
-
17 votesGeoffrey
supported this idea
·
-
12 votesGeoffrey
supported this idea
·
-
2 votesGeoffrey
supported this idea
·
Have possibility the manage this limite by ourself.
Also as long as talked about safety. Target clusters for users can be identified. However, this cannot be done for "custom roles". This feature is important because currently, security by "custom role" is deployed on all clusters of a project. This forces us to create one project per cluster to be able to manage database access security.