Kyle
My feedback
25 results found
-
14 votes
An error occurred while saving the comment An error occurred while saving the comment Kyle
commented
Is there any update on this? I know we initially asked for this two years ago and was curious on an update on this.
Kyle
supported this idea
·
-
8 votesKyle
supported this idea
·
-
4 votesKyle
shared this idea
·
-
8 votesKyle
shared this idea
·
-
3 votesKyle
supported this idea
·
-
7 votes
An error occurred while saving the comment Kyle
commented
Any status on this? There are certain countries we can't build clusters in until these redaction options are in place.
An error occurred while saving the comment Kyle
commented
Items we need to comply with data privacy rules:
1. Log redaction turned on (this appears to be available via a support ticket)
2. Ability to enable log redaction via automation (API, terraform, console)
3. Ability to validate that log redaction is enabled via API/consoleAn error occurred while saving the comment Kyle
commented
Hi Salman,
That's good to know. I was told this wasn't even an option right now.
When can we turn this on via automation (terraform)? Ideally this option would be allowed to be configured by your customers instead of having to open a ticket with support to enable it each time.
Thanks,
KyleAn error occurred while saving the comment Kyle
commented
Any progress on this? There are certain government regulations that make this a requirement if personal data is being stored in log files. I'm curious how you are solving this for your customer bases that want to build clusters in places like South Korea.
An error occurred while saving the comment Kyle
commented
Andrew, what about the ability to redact the logs on the fly when we download them (either through the UI or via API calls)?
We currently pull logs and store them in CloudWatch so we can search more easily for issues without the need to grant everyone access to Atlas in our organization. But we'd prefer to not have CRUD operations show up in those logs if possible.
Thinking the API call could include a redact option (true/false) and the UI can have a check box to turn it on when you pull it down manually.
Kyle
supported this idea
·
-
2 votesKyle
supported this idea
·
-
4 votesKyle
supported this idea
·
-
25 votes
An error occurred while saving the comment Kyle
commented
We would like this feature as well, if not just for a "backdoor" user to be able to use Atlas auth in case SSO is broken.
Kyle
supported this idea
·
-
2 votes
An error occurred while saving the comment Kyle
commented
Using a service record to be consistent with the desired connection string path that Atlas is focusing on everywhere else within the mongomirror call would be ideal. The 2 factors above are also valid for sure.
Kyle
supported this idea
·
-
73 votes
An error occurred while saving the comment Kyle
commented
This would be great. Why hasn't there been any feedback on this since May?
Kyle
supported this idea
·
-
22 votesKyle
supported this idea
·
-
16 votes
An error occurred while saving the comment Kyle
commented
Agreed, we really need the ability to rename databases via mongomirror. Without it, we have to use mongodump/mongorestore which is really slow for decent sized databases.
Kyle
supported this idea
·
-
14 votesKyle
shared this idea
·
-
23 votes
An error occurred while saving the comment Kyle
commented
Yeah, showing our custom cluster name instead of (or in addition to) the default unreadable cluster name is super helpful when you have many clusters in a given project.
Good: my-test-cluster
Bad: atlas-abc123-shard-0Kyle
supported this idea
·
-
3 votesKyle
shared this idea
·
-
13 votesKyle
shared this idea
·
-
32 votesKyle
supported this idea
·
-
4 votesKyle
shared this idea
·
-
11 votesKyle
shared this idea
·
Any update?