PostgreSQL databases are open-source relational database management systems emphasizing extensibility and SQL compliance. Microsoft enables developers to create cloud-hosted PostgreSQL databases.

Through this integration, Apono helps you securely manage access to your Azure PostgreSQL instances.

To enable Apono to manage Azure PostgreSQL user access, you must create a user and then configure the integration within the Apono UI.

Prerequisites

Create a PostgreSQL user

You must create a user in your PostgreSQL instance for the Apono connector and grant that user permissions to your databases.

Use the following steps to create a user and grant it permissions:

1. In your preferred client tool, create a new user. Use apono_connector for the username. Be sure to set a strong password for the user. You must also grant the azure_pg_admin role to the user in the database instance.

CREATE USER apono_connector WITH ENCRYPTED PASSWORD 'password';
ALTER USER apono_connector WITH CREATEROLE;
GRANT azure_pg_admin TO apono_connector;

1. Grant privileges to the azure_pg_admin role on all databases except template0 and azure_sys. This allows Apono to perform tasks that are not restricted to a single schema or object within the database, such as creating, altering, and dropping database objects.

DO $$
DECLARE
  database_name text;
BEGIN
  FOR database_name IN (SELECT datname FROM pg_database WHERE datname != 'template0' AND datname != 'azure_sys' AND datname != 'azure_maintenance') LOOP
    EXECUTE 'GRANT ALL PRIVILEGES ON DATABASE ' || quote_ident(database_name) || ' TO azure_pg_admin WITH GRANT OPTION';
  END LOOP;
END; $$

1. For each database to be managed through Apono, connect to the database and grant azure_pg_admin privileges on all objects in the schemas. This allows Apono to perform tasks that are restricted to schemas within the database, such as modifying table structures, creating new sequences, or altering functions.

DO $$
DECLARE
  schema text;
BEGIN
  FOR schema IN (SELECT schema_name FROM information_schema.schemata WHERE schema_name NOT LIKE 'pg_%' AND schema_name != 'information_schema' AND schema_name != 'cron') LOOP
    EXECUTE 'GRANT ALL PRIVILEGES ON SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
  END LOOP;
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON TABLES TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON SEQUENCES TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON FUNCTIONS TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON SCHEMAS TO azure_pg_admin WITH GRANT OPTION';
END; $$

1. Connect to the template1 database and grant azure_pg_admin privileges on all objects in the schemas. For any new databases created in the future, this allows Apono to perform tasks that are restricted to schemas within the database, such as modifying table structures, creating new sequences, or altering functions.

DO $$
DECLARE
  schema text;
BEGIN
  FOR schema IN (SELECT schema_name FROM information_schema.schemata WHERE schema_name NOT LIKE 'pg_%' AND schema_name != 'information_schema' AND schema_name != 'cron') LOOP
    EXECUTE 'GRANT ALL PRIVILEGES ON SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
    EXECUTE 'GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA ' || quote_ident(schema) || ' TO azure_pg_admin WITH GRANT OPTION';
  END LOOP;
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON TABLES TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON SEQUENCES TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON FUNCTIONS TO azure_pg_admin WITH GRANT OPTION';
  EXECUTE 'ALTER DEFAULT PRIVILEGES GRANT ALL PRIVILEGES ON SCHEMAS TO azure_pg_admin WITH GRANT OPTION';
END; $$

5. Using the credentials from step 1, create a secret for the database instance and associate it to the Azure connector.

Integrate Azure PostgreSQL

Follow these steps to complete the integration:

1. On the Catalog tab, click Azure PostgreSQL. The Connect Integration page appears.

2. Under Discovery, click one or more resource types to sync with Apono.

1. Click Next. The Apono connector section appears.

2. From the dropdown menu, select the connector that has been granted read access to the secret for the PostgreSQL instance.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.\

   Setting

   Description

   Integration Name

   Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

   Hostname

   Hostname of the PostgreSQL instance to connect

   Port

   Port value for the database By default, Apono sets this value to 5432.

   Database Name

   Name of the database to integrate By default, Apono sets this value to postgre.

   SSL Mode

   (Optional) Mode of Secure Sockets Layer (SSL) encryption used to secure the connection with the SQL database server

   • require: An SSL-encrypted connection must be used.

   • allow: An SSL-encrypted or unencrypted connection is used. If an SSL encrypted connection is unavailable, the unencrypted connection is used.

   • disable: An unencrypted connection is used.

   • prefer: An SSL-encrypted connection is attempted. If the encrypted connection is unavailable, the unencrypted connection is used.

   • verify-ca: An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass.

   • verify-full: An SSL-encrypted connection must be used and a server certification verification against the provided CA certificates must pass. Additionally, the server hostname is checked against the certificate's names.

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Get more with Apono section expands.

6. Define the Get more with Apono settings.\

   Setting

   Description

   Credential Rotation

   User cleanup after access is revoked (in days)

   (Optional) Defines the number of days after access has been revoked that the user should be deleted

   Custom Access Details

   (Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.

   Integration Owner

   1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.

   2. From the Value dropdown menu, select one or multiple users or groups.

   NOTE: When Resource Owner is defined, an Integration Owner must be defined.

   Resource Owner

   1. Enter a Key name. This value is the name of the tag created in your cloud environment.

   2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

   NOTE: When this setting is defined, an Integration Owner must also be defined.

7. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your Azure PostgreSQL instances.

Discover SQL Databases in Azure

Azure SQL databases provide powerful and flexible relational database services in the cloud. This guide shows you how to enable Apono to discover and manage your Azure SQL databases, including MySQL and PostgreSQL instances.

Prerequisites

Before you start, ensure you have:

1. One or more Apono connectors installed with network access to your Azure SQL databases.

   • Minimum required version: 1.3.6

2. Permissions to create and manage Azure Key Vault secrets and tag Azure resources.

3. Access to your Azure Subscription or Management Group.

Steps to Enable SQL Database Discovery

Create Secrets

1. Create secrets in Azure Key Vault for your MySQL and PostgreSQL database credentials.

2. Follow the required format for each database type:

   • For MySQL read more here

   • For PostgreSQL read more here

Example commands:

az keyvault secret set --vault-name "<KEYVAULT_NAME>" --name "<MYSQL_SECRET_NAME>" --value '{"username": "<USERNAME>", "password": "<PASSWORD>"}'
az keyvault secret set --vault-name "<KEYVAULT_NAME>" --name "<POSTGRESQL_SECRET_NAME>" --value '{"username": "<USERNAME>", "password": "<PASSWORD>"}'

Tag Your SQL Databases

For each database you want Apono to discover:

1. Navigate to the database resource in the Azure portal.

2. Add these tags:

   • Key: vault-url, Value: <URL of the Azure Key Vault containing the secret>

   • Key: secret-name, Value: <Name of the secret in Azure Key Vault>

Example:

• Key: vault-url, Value: https://mystore.vault.azure.net/

• Key: secret-name, Value: db-credentials

3. Set Up Apono Integration

1. Go to the Integrations Catalog in the Apono web application.

2. Click "Azure" and select either "Management Group" or "Subscription". Make sure to pick resources under Connect Sub Integrations:\
3. Choose the Apono connector set up for your Subscription or Management Group. Read more here.

4. Complete the integration by providing:

   • Integration Name: A descriptive name for your integration

   • Azure Subscription ID or Management Group ID (as applicable)

Verifying Discovery

1. Apono will discover tagged SQL databases during its next sync.

2. Check the Integrations page to see the main integration and the discovered databases.

Important Notes

• Ensure your Apono connector has network access to all SQL databases you want to discover.

• Multiple Apono connectors may be needed if databases exist in different network environments.

• The discovery process uses Azure Resource Graph and doesn't require direct database access for initial discovery.

For any questions about the discovery process, contact Apono support.

MySQL is a reliable and secure open-source relational database system. It serves as the main data store for various applications, websites, and products. This includes mission-critical applications and dynamic websites.

Microsoft enables developers to create cloud-hosted MySQL databases.

Through this integration, Apono helps you securely manage access to your Azure MySQL databases.

Prerequisites

Before starting this integration, create the items listed in the following table.

Create a MySQL user

You must create a user in your MySQL instance for the Apono connector and grant that user permissions to your databases.

Use the following steps to create a user and grant it permissions:

1. In your preferred client tool, create a new user. Be sure to set a strong password for the user.

   Copy

   CREATE USER 'apono_connector'@'%' IDENTIFIED BY 'password';

2. Expose databases to the user. This allows Apono to view database names without accessing the contents of each database.

   Copy

   GRANT SHOW DATABASES ON *.* TO 'apono_connector'@'%';

3. Grant the user database permissions. The following commands grant Apono the following permissions:

   • Creating users

   • Updating user information and privileges

   • Monitoring and troubleshooting processes running on the database\

   Copy

   GRANT CREATE USER ON *.* TO 'apono_connector'@'%';
   GRANT UPDATE ON mysql.* TO 'apono_connector'@'%';
   GRANT PROCESS ON *.* TO 'apono_connector'@'%';

4. Grant the user only one of the following sets of permissions. The chosen set defines the highest level of permissions to provision with Apono. Expand each of the following options to reveal the SQL commands:

GRANT SELECT ON *.* TO 'apono_connector'@'%';
GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%';

GRANT SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%';
GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%';

GRANT EXECUTE,DROP,SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%';
GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%';

1. (MySQL 8.0+) Grant the service account the authority to manage other roles. This enables Apono to create, alter, and drop roles. However, this role does not inherently grant specific database access permissions.

GRANT ROLE_ADMIN on *.* to 'apono_connector';

1. Using the credentials from step 1, create a secret for the database instance and associate it to the Azure connector.

You can now integrate Azure MySQL.

Integrate Azure MySQL

Follow these steps to complete the integration:

1. On the Catalog tab, click Azure MySQL. The Connect Integration page appears.

2. Under Discovery, click one or more resource types and cloud services to sync with Apono.

1. Click Next. The Apono connector section appears.

2. From the dropdown menu, select a connector.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting

   Description

   Integration Name

   Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

   Hostname

   Hostname of the MySQL instance to connect

   Port

   Port value for the database By default, Apono sets this value to 3306.

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Custom Access Details section expands.

6. Define the Get more with Apono settings.\

   Setting

   Description

   Credential Rotation

   User cleanup after access is revoked (in days)

   (Optional) Defines the number of days after access has been revoked that the user should be deleted

   Custom Access Details

   (Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.

   Integration Owner

   1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.

   2. From the Value dropdown menu, select one or multiple users or groups.

   NOTE: When Resource Owner is defined, an Integration Owner must be defined.

   Resource Owner

   1. Enter a Key name. This value is the name of the tag created in your cloud environment.

   2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

   NOTE: When this setting is defined, an Integration Owner must also be defined.

7. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your Azure MySQL database instance.

Apono offers Azure users a simple way to centralize cloud management through our platform. Through a single integration, you can manage multiple Azure services across various management groups and subscriptions.

Prerequisites

Integrate Azure

Now that you have completed this integration, you can create access flows that grant permission to your Azure services.

With Azure Kubernetes Service (AKS) on Microsoft Azure, AKS simplifies the management complexities of Kubernetes.

Through this integration, Apono helps you securely manage access to your Microsoft Azure Kubernetes cluster.

Prerequisites

Integrate Azure Kubernetes Service (AKS)

Follow these steps to complete the integration:

1. On the Catalog tab, click Azure Kubernetes Service (AKS). The Connect Integration page appears.

2. Under Discovery, click one or more resource types and cloud services to sync with Apono.

1. Click Next. The Apono connector section appears.

2. From the dropdown menu, select a connector.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting

   Description

   Integration Name

   Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

   Server URL

   (Optional) URL of the Kubernetes API server used to interact with the Kubernetes cluster

   Certificate Authority

   (Optional) Certificate that ensures that the Kubernetes API server is trusted and authentic Leave this field empty if you want to connect the cluster where the connector is deployed.

   Resource Group

   Cluster Name

   Subscription ID

   (Optional) Subscription ID where the cluster is deployed

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Get more with Apono section expands.

6. Define the Get more with Apono settings.\

   Setting

   Description

   Credential Rotation

   User cleanup after access is revoked (in days)

   (Optional) Defines the number of days after access has been revoked that the user should be deleted

   Custom Access Details

   (Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.

   Integration Owner

   1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.

   2. From the Value dropdown menu, select one or multiple users or groups.

   NOTE: When Resource Owner is defined, an Integration Owner must be defined.

   Resource Owner

   1. Enter a Key name. This value is the name of the tag created in your cloud environment.

   2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.

   NOTE: When this setting is defined, an Integration Owner must also be defined.

7. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your Azure Kubernetes Service cluster.

If your organization uses Azure as a cloud platform, Apono can help you securely manage access to your Azure cloud-based services, subscriptions, and resource groups.

By identifying and transforming existing privileges, Apono can shift your cloud management from broad permissions to on-demand . Through our integrations, Apono enables you to perform the following access tasks:

• Limit Access: Discover existing privileges in Azure and convert them to just-in-time Access Flows.

• Enable Self-Service Access: Allow developers to request access to Azure services, buckets, and instances via Slack.

• Automate Approval Workflows: Create automatic approval processes for sensitive Azure resources.

• Restrict Third-Party Access: Grant third-parties (customers or vendors) time-based access to specific services with MFA verification.

• Review Access: Audit user cloud access, permissions granted, and reasons for access across Azure.