LogoLogo
Documentation and Guides
Documentation and Guides
  • ABOUT APONO
    • Why Choose Apono
    • Security and Architecture
    • Glossary
  • GETTING STARTED
    • How Apono Works
    • Getting started
    • Access Discovery
    • Integrating with Apono
  • CONNECTORS AND SECRETS
    • Apono Integration Secret
    • High Availability for Connectors
    • Installing a connector with Docker
    • Manage integrations
    • Manage connectors
    • S3 Storage
  • AWS ENVIRONMENT
    • AWS Overview
    • Apono Connector for AWS
      • Installing a connector on EKS Using Terraform
      • Updating a connector in AWS
      • Installing a connector on AWS ECS using Terraform
    • AWS Integrations
      • Integrate an AWS account or organization
        • Auto Discover AWS RDS Instances
        • AWS Best Practices
      • Amazon Redshift
      • RDS PostgreSQL
      • AWS RDS MySQL
      • Integrate with EKS
      • AWS Lambda Custom Integration
      • EC2 via Systems Manager Agent (SSM)
  • AZURE ENVIRONMENT
    • Apono Connector for Azure
      • Install an Azure connector on ACI using Azure CLI
      • Install an Azure connector on ACI using PowerShell
      • Install an Azure connector on ACI using Terraform
      • Updating a connector in Azure
    • Azure Integrations
      • Integrate with Azure Management Group or Subscription
        • Auto Discover Azure SQL Databases
      • Azure MySQL
      • Azure PostgreSQL
      • Integrate with AKS
  • GCP ENVIRONMENT
    • Apono Connector for GCP
      • Installing a GCP connector on Cloud Run using CLI
      • Installing a GCP connector on GKE using CLI (Helm)
      • Installing a GCP connector on GKE using Terraform
      • Updating a connector in Google Cloud
    • GCP Integrations
      • Integrate a GCP organization or project
      • CloudSQL - MySQL
      • CloudSQL - PostgreSQL
      • Google Cloud Functions
      • Integrate with GKE
      • AlloyDB
  • KUBERNETES ENVIRONMENT
    • Apono Connector for Kubernetes
      • Installing a connector on Kubernetes with AWS permissions
      • Updating a Kubernetes connector
    • Kubernetes Integrations
      • Integrate with Self-Managed Kubernetes
  • ADDITIONAL INTEGRATIONS
    • Databases and Data Repositories
      • Microsoft SQL Server
      • MongoDB
      • MongoDB Atlas
      • MongoDB Atlas Portal
      • MySQL
      • Oracle Database
      • PostgreSQL
      • RabbitMQ
      • Redis Cloud (Redislabs)
      • Snowflake
      • Vertica
      • MariaDB
    • Network Management
      • SSH Servers
      • RDP Servers
      • Windows Domain Controller
      • AWS EC2 SSH Servers
      • Azure VM SSH Servers
      • Installing the Apono HTTP Proxy
    • Development Tools
      • GitHub
      • Rancher
    • Identity Providers
      • Okta SCIM
      • Okta Groups
      • Okta SSO for Apono logins
      • Google Workspace (Gsuite)
      • Google Workspace (GSuite) Groups
      • Azure Active Directory (Microsoft Entra ID)
      • Azure Active Directory (Entra ID) Groups
      • Jumpcloud
      • JumpCloud Groups
      • OneLogin
      • OneLogin Group
      • LDAP Groups
      • The Manager Attribute in Access Flows
      • HiBob
      • Ping Identity SSO
    • Incident Response Integrations
      • Opsgenie
      • PagerDuty
      • VictorOps (Splunk On-Call)
      • Zenduty
    • ChatOps Integrations
      • Slack integration
      • Teams integration
      • Backstage Integration
    • Secret Management
      • 1Password
  • WEBHOOK INTEGRATIONS
    • Webhooks Overview
    • Anomaly Webhook
    • Audit Log Webhook
    • Request Webhook
      • Custom Webhooks
      • Communications and Notifications
        • Slack Outbound Webhooks
        • Teams
        • Outlook and Gmail (Using Azure Logic App)
      • ITSM
        • Freshdesk
        • Jira
        • ServiceNow
        • Zendesk
        • Freshservice
        • ServiceDesk Plus
      • Logs and SIEMs
        • Coralogix
        • Datadog
        • Logz.io
        • Grafana
        • New Relic
        • SolarWinds
        • Sumo Logic
        • Cortex
        • Logpoint
        • Splunk
        • Microsoft Sentinel
      • Orchestration and workflow builders
        • Okta Workflows
        • Torq
    • Integration Webhook
    • Webhook Payload References
      • Audit Log Webhook Payload Schema Reference
      • Webhook Payload Schema Reference
    • Manage webhooks
    • Troubleshoot a webhook
    • Manual Webhook
      • ITSM
        • PagerDuty
  • ACCESS FLOWS
    • Access Flows
      • What are Access Flows?
    • Create Access Flows
      • Self Serve Access Flows
      • Automatic Access Flows
      • Access Duration
    • Manage Access Flows
      • Right Sizing
    • Revoke Access
    • Dynamic Access Management
      • Resource and Integration Owners
    • Common Use Cases
      • Ensuring SLA
      • Protecting PII and Customer Data
      • Production Stability and Management
      • Break Glass Protocol
    • Create Bundles
    • Manage Bundles
  • ACCESS REQUESTS AND APPROVALS
    • Slack
      • Requesting Access with Slack
      • Approving Access with Slack
      • Reviewing historical requests with Slack
    • Teams
      • Requesting Access with Teams
      • Approving Access with Teams
    • CLI
      • Install and manage the Apono CLI
      • Requesting Access with CLI
    • Web Portal
      • Requesting Access with the Web Portal
      • Approving Access with the Web Portal
      • Reviewing historical requests with the Web Portal
    • Freshservice
    • Favorites
  • Inventory
    • Inventory Overview
    • Inventory
    • Access Scopes
    • Risk Scores
    • Apono Query Language
  • AUDITS AND REPORTS
    • Activity Overview
      • Activity
      • Create Reports
      • Manage Reports
    • Compliance: Audit and Reporting
    • Auditing Access in Apono
    • Admin Audit Log (Syslog)
  • HELP AND DEBUGGING
    • Integration Status Page
    • Troubleshooting Errors
  • ARCHITECTURE AND SECURITY
    • Anomaly Detection
    • Multi-factor Authentication
    • Credentials Rotation Policy
    • Periodic User Cleanup & Deletion
    • End-user Authentication
    • Personal API Tokens
  • User Administration
    • Role-Based Access Control (RBAC) Reference
    • Create Identities
    • Manage Identities
Powered by GitBook
On this page
  • Prerequisites
  • Define permitted users
  • Define the resource
  • Add a label
  • Review the access flow

Was this helpful?

Export as PDF
  1. ACCESS FLOWS
  2. Create Access Flows

Automatic Access Flows

Automatic access flows automatically grant and revoke access to a resource based on user context. This access flow type is best used for role-based access control (RBAC) and on-call shift baselines.

PreviousSelf Serve Access FlowsNextAccess Duration

Last updated 1 month ago

Was this helpful?

To create an automatic access flow, you must define the permitted users and available resources.


Prerequisites

Item
Description

Cloud resources

One or more resources in a cloud platform that has been integrated with Apono If you have not already, integrate Apono with a cloud platform to control access to its resources:

Apono identities

One or more identity sources in the Apono system There are various ways to add identities to Apono:


Define permitted users

Follow these steps to define the permitted grantees:

  1. Click Automatic. The Automatic fields appear below.

  2. Enter an alphanumeric, user-friendly Access Flow Name.

  3. Click Select attribute to select an IdP attribute, such as User or Group.

  4. (Optional) Click is to select conditional logic from the menu options.

Other operators include the following:

  • Is not

  • Contains

  • Does not contain

  • Starts with

  1. Click Select value to select one or multiple users or groups from the menu options. This selection determines who is permitted to request access.

  2. (Optional) Add another user.

    1. Under the last listed requestor, click +. A new row appears.

    2. Repeat steps 4-7.

    3. Select the conditional logic for the multiple requestors.

      Condition
      Description

      AND

      (Default) Allows the user to request access if they meet all the attributes of the user group

      OR

      Allows the user to request access if they meet any of the attributes of the user group


Define the resource

You can define access to specific resources in an Apono integration, bundle, or access scope.

Follow these steps to define access to specific resources:

  1. Under They will have access to, click Select target > Integrations.

  2. Select an integration. The Select resource type panel appears.

  3. Select the resource type.

  4. Click Done. The panel closes.

  5. Click permissions. The Permissions menu appears.

  6. Select one or more permissions to grant the requester.

  7. (Optional) Refine the available resources:

    1. Click in the populated to field. A list of resources appears.

    2. Select one or several resources.

By default, the user has access to Any resources. However, the following options allow you to define access more granularly:

  • Any resources except specific

  • Select by name

  • Select by tags

  1. (Optional) Add another target:

    1. Click + at the end of the row. A new target row appears.

Follow these steps to define access to a specific bundle:

  1. Under They will have access to, click Select target > Bundles.

  2. Select a bundle.

  3. (Optional) To add another bundle, click +. A new target row appears.

Follow these steps to define access to a specific access scope:

  1. Under They will have access to, click Select target > Access Scope. The Select access scope menu appears.

You may enter keywords into the search bar to locate an access scope.

  1. Select an access scope.

  1. (Optional) To add another access scope, click +. A new target row appears.


Add a label

Follow this step to add an access flow label:

  1. In the Access flow labels, enter a value and press Enter OR select an existing label.


Review the access flow

  1. Click Review and Create. The Automatic Access Flow Summary appears.

The access flow summary provides a visual overview of the relationship between the requesters and the target resource.

  1. Click Create and Grant.

On the page, click Create Access Flow. The Create Access Flow page appears.

To ensure you do not exceed the AWS inline policy character limit, read when adding AWS resources.

Repeat steps 1-7 or add a or .

To ensure you do not exceed the AWS inline policy character limit, read when adding bundles with AWS resources.

Repeat steps 1-2 or add an or .

(Optional) Click (eye icon) to preview the contents of the access scope in a popup window.

You can also click + Create New Access Scope if none of the existing access scopes meet your needs. The Inventory page appears. You can and the new access scope.

Repeat steps 1-3 or add an or .

A label identifies an access flow for streamlined organization and use. When assigned to an access flow, labels appear in the access flow tiles on the page.

After defining the and , follow these steps to review and save an automatic access flow:

Access Flows
AWS Limitations
AWS Limitations
Access Flows
bundle
access scope
integration
access scope
integration
bundle
permitted users
resource
AWS integrations
Azure integrations
GCP integrations
Kubernetes integrations
Integrate an identity provider
Invite a user manually
create
use
Create Access Flow page
Defining grantees
Defining resources
Settings section