Abbey Docs
  • 👋Welcome
  • Getting Started
    • Quickstart
    • Step-by-Step Tutorials
      • AWS: Managing Access to Identity Center Groups
      • AWS: Managing Access to Identity Center Permission Sets
      • AWS: Managing Access to IAM Groups
      • Azure AD: Managing Access to Groups
      • Confluent: Managing Access to Kafka ACLs
      • Databricks: Managing Access to Managed Tables in Unity Catalog
      • Databricks: Managing Access to Groups
      • GitHub: Managing Access to Teams
      • Google Cloud: Managing Access to Groups
      • Google Workspace: Managing Access to Google Groups
      • Kafka: Managing Access to ACLs
      • Okta: Managing Access to Groups
      • Postgres: Managing Access to Roles
      • Snowflake: Managing Access to Tables
      • Tabular: Managing Access to Apache Iceberg Roles
      • Tailscale: Managing Access to ACLs
      • Vault: Managing Access to Groups and Policies
      • Integrating Abbey with Terraform Cloud
      • Using Abbey with Atlantis
      • Using Abbey with Spacelift
    • Starter Kits
  • How Abbey Works
    • How Abbey Works
    • Key Concepts
  • Build a Grant Kit
    • Get a Starter Kit
    • Connect a Repo
    • Create a Grant Kit
    • Link Identities
    • Write Access Policies
    • Deploy Your Grant Kit
    • Request Access
    • Approve or Deny Access Requests
  • Use Cases
    • Time-Based Access
      • Expire After a Duration
      • Expire At a Specific Time
    • Approval Workflows
      • Using a Single Approval Step
      • Using Multiple Approval Steps
      • Conditionally Skip Approval Steps
  • Admin
    • User Roles
    • Sign-in and MFA
      • Sign-in Methods
      • Multifactor Authentication (MFA)
      • Enabling Single Sign-On
    • Sources
      • PagerDuty
      • Directory Sync
    • End User Notifications
    • Manage API Tokens
  • Reference
    • Grant Kits
      • Workflows
      • Policies
      • Outputs
    • Referencing Users and Groups
    • Linking Application Identities into Abbey
      • Why do I need to link application identities?
      • How do I Link Application Identities?
      • Supported Application Identity Types and Schemas
      • Application Data Object
    • Access Policies
      • Types of Access Policies
      • Policy Bundles
      • Inline Policies
      • Helper Functions
      • Policy Examples
    • Terms of Service
    • FAQ
      • Troubleshooting
  • Resources
    • Abbey Labs
    • Terraform Registry
    • GitHub
    • System Status
    • Privacy Policy
    • Logo
Powered by GitBook
On this page
  • Abbey secures cloud infrastructure by enabling any engineer to automate user access directly in Terraform.
  • How Abbey Works
  • Get Started
  • Top Tutorials

Welcome

NextQuickstart

Last updated 3 months ago

Abbey secures cloud infrastructure by enabling any engineer to automate user access directly in Terraform.

How Abbey Works

When it comes to employee access to cloud infrastructure, Workflows allow for definition of how someone should get access (who should approve), and Policies define whether someone should have access (or when access should be revoked).

Abbey is built for the Infrastructure engineer, allowing them to define both Workflows and Policies via the Abbey Terraform Provider. Any team can deploy Abbey quickly utilizing your existing Git repository, CI/CD pipeline, and Terraform orchestration system.

Infrastructure engineers can define how access should be granted and when access should be revoked, reducing their manual workload. End users get frictionless access. Security teams can rest easy knowing that a model of least privilege is being followed. And Compliance teams get an automated audit trail of all changes.

Get Started

Top Tutorials

👋

Databricks

Managing Access to Managed Tables in Unity Catalog

Google Cloud

Managing Access to Groups

AWS

Secure Access to IAM Groups

Abbey in 3 minutes
Cover

Deploy Abbey in 30 Minutes

Run a full end-to-end demo to see Abbey in action

Cover

Tutorials

Secure access to critical cloud infrastructure

Cover

Explore Key Concepts

Deep dive into Grant Kits, Workflows, and Policies to understand how we secure access at Abbey