Re: help: feedback on infra automation tool

1 view
Skip to first unread message

Andrios Robert

unread,
Sep 8, 2022, 4:41:56 PM9/8/22
to lua...@googlegroups.com
Thought to share this Reddit thread where multiple companies talk about how they manage ad-hoc access to production databases:


Hope it helps.
On August 17, 2022 05:09, Andrios Robert <and...@tryrunops.com> wrote:
Hello, adding a bit more context: my name is Andrios, and I’m the founder of a fresh dev tool company backed by Y Combinator and Global Founders Capital. We help DevOps teams from high growth startups (EBANX, Dock) and public companies (Enjoei, RD Station) controlling prod and PII (sensitive data) access.

It seems like you have these challenges, and I was hoping you’d be able to help us out by sharing your personal feedback and insights on security for k8s, aws, and other cloud tools. Even a quick 10-minute phone conversation while you’re on-the-go (walking your dog, or getting your morning coffee, whichever is easiest for you..), would be much appreciated. Please let me know if possible to arrange, I’ll adjust according to your availability.

Thank you, Andrios.
On August 15, 2022 10:46, Andrios Robert <and...@tryrunops.com> wrote:
Hi, saw you forked redis on Github and wanted to ask for a quick help.

I'm the founder of an open-source core tool that makes it easier and safer to access k8s clusters, aws, databases, and others.

I’d love to connect and hear your thoughts on what we are doing based on your experience these technologies.

Can you spare 15-20 min to help us out over a quick call? Thanks in advance & looking forward to hearing from you.

Andrios.


Andrios Robert

unread,
Sep 15, 2022, 9:20:09 AM9/15/22
to lua...@googlegroups.com
Hi, last ping on this.

It would help us a loooot if you could provide some insights as to how you deal with ad-hoc production access today:

Feel free to reply just with a number:
  1. This is an urgent problem but we don't have time to work on it now.
  2. This is a low priority problem for us at the moment.
  3. We built an in-house solution to solve this.
  4. This isn't a problem.
Thanks a lot!
Reply all
Reply to author
Forward
0 new messages