Sym

Hey Product Hunt! I’m Jon, CEO and co-founder of Sym. We help your teams access production infrastructure safely without friction. I know how hard it is to balance the pressure to ship with the pressure to stay secure. I’ve tried to build least privilege systems that are based on giving users fine-grained permissions to do their jobs. I’ve seen these systems fail, because our jobs are dynamic. The infrastructure and resources we need are changing all the time, and our access management tools can’t keep up. Sym helps you solve security gaps by starting with collaborative review rather than overly tightened policies. Take your existing AWS permissions and wrap them in a Sym workflow. Then use our SDK to route access requests to peers or to the right approvers based on the context of the request. Sym flows are adaptive, so you can automate approvals when it makes sense. You can fast track requests using simple business rules that you write in Python with our SDK. Many teams start by checking a requester’s on-call status in PagerDuty, or by invoking an AWS Lambda to check an internal system for more context. The teams that feel access management pressure are increasingly the same folks that are managing the production infrastructure itself. This is why we’ve made it really easy to manage Sym Flows in Terraform right along with the rest of your stack. When you use Sym, you get to use the same change management process for your access flows as you do for the rest of your infrastructure. I’m excited to launch our free tier and to see all the interesting things folks build on the platform. Many teams come to us with an initial pain point around AWS access, and then stick around to build out access flows for customer data, internal admin panels, deployment gates, and all the other parts of a modern internal platform. Please kick the tires and let us know what you think!

Hello ProductHunt community! I’m Justin and I’m excited to introduce Sym. If you’re a developer who has struggled with how to handle access to your infrastructure…read on. If I say “your infrastructure needs to be secure” nobody would disagree. But how that actually works is a lot less simple. There’s a good chance you’ve got multiple developers with free reign in AWS IAM. Access tends to be all or nothing, instead of just-in-time and just-this-resource. To really make your infra secure and ensure the right people get access to the right things takes a meaningful degree of upfront effort. But it also slows things down continually if your teammates constantly need to be requesting access to the resources they need to build new things. Getting features out quickly is hard enough; the last thing you want to worry about is leaving your developer hanging on a ticket to get access to the S3 bucket they need to implement something new. This was the norm at several companies I’ve worked at: I remember a cool 6 day waiting period to get read-only access to our production database replica at a certain large cloud provider who shall remain unnamed. All of this is why we built Sym! Sym helps developers secure their infrastructure without slowing down. You get everything you need to implement just-in-time access for your team: a Terraform provider for defining roles that match your IAM, a workflow engine for lines out to Pagerduty, Okta, and the like, plus a dead-simple Slack UI where your team can make and approve/reject requests. Sym is built for setup in a few hours instead of a few days, so you can get enterprise-grade infrastructure security without the big up front cost.

How does this work with identity platforms like Okta? Will the enterprises be able to continue using that for core access management and sym to provision JIT/temporary access? VERY COOL