The MongoDB integration helps you to securely discover and manage your MongoDB resources through Apono.

After integrating MongoDB with Apono, you'll be able to:

• Automate resource discovery and mapping across your MongoDB infrastructure

• Enable administrators to implement just-in-time, least-privilege access policies and securely manage permissions

• Allow users to request temporary access to specific clusters, roles, databases, and collections

Review the following prerequisites and implementation steps to complete this integration.

Prerequisites

Create a user

You must create a MongoDB user for the Apono connector.

Follow these steps to create a user:

1. In your MongoDB instance, switch to the admin database.

use admin;

1. Create a user (user) and password (pwd) for the Apono connector.

db.createUser({
    user: "apono-connector",
    pwd: "password",
    roles: [
        {
            "role" : "clusterMonitor",
            "db" : "admin"
        },
        {
            "role" : "userAdminAnyDatabase",
            "db" : "admin"
        },
        {
            "role" : "readWriteAnyDatabase",
            "db" : "admin"
        },
        {
            "role" : "clusterManager",
            "db" : "admin"
        }
    ]
});

1. Create a secret with the credentials from step 2. Use the following key-value pair structure when generating the secret. Be sure to replace #PASSWORD with the actual value. If you used a different name for the user, replace apono-connector with the name you assigned to the user.

"username": "apono-connector",
"password": "#PASSWORD"

Integrate MongoDB

Follow these steps to complete the integration:

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

2. Under Discovery, select one or multiple resource types.

1. Click Next. The Apono connector section expands.

2. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

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

   Address of the MongoDB instance

   Port

   Network port the MongoDB instance is listening on for connections

   By default, MongoDB uses port 27017.

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 MongoDB instance.

Microsoft SQL Server is a reliable and secure relational database management system. It can be used as the main data store for various applications, websites, and products.

Microsoft enables developers to create cloud-hosted SQL Server databases.

Through this integration, Apono helps you securely manage access to your Microsoft SQL Server database.

Prerequisites

Create a Microsoft SQL Server user

You must create a user in your Microsoft SQL Server instance for the Apono connector.

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

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

CREATE LOGIN apono_connector WITH PASSWORD = 'password';

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

GRANT VIEW ANY DATABASE TO apono_connector;

1. Grant the ALTER ANY LOGIN database permissions to the user in all the databases.

 USE master GRANT ALTER ANY LOGIN TO apono_connector;

1. Grant the user ADMIN permissions: Allows Apono to grant users administrative-level access, including the ability to execute and drop tables\

USE master GRANT CONTROL SERVER TO apono_connector;

USE master ALTER SERVER ROLE securityadmin ADD MEMBER server_principal

Integrate Microsoft SQL Server

Follow these steps to complete the integration:

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

1. Click Next. The Apono connector section expands.

2. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

Overview

Overview

• Reduce Over Privileges - Discover existing privileges to MySQL databases and convert them to on-demand access flows to reduce over-privileges.

• Self Service Access - Empower your developers to gain self-servable access to databases using Slack.

• Automated Approval Workflows - Create approval workflows to specific sensitive databases.

• Restricted Third Party Access - Grant third-party (customer or vendor) time-based access to specific databases with MFA verification.

• Review Access - View a detailed access audit of who was granted access to which databases with what permission level and why.

Step by step guide

Prerequisites

• An Apono connector installed with network access to the MySQL databases

  • Minimal Apono connector version: 1.3.0 (visit the Connectors Page and update the connector if needed)

• A user for Apono to your MySQL with the following permissions

• A secret created in Secret Store with the following params:

  • Key username, Value MySQL USERNAME

  • Keypassword, Value USERNAME PASSWORD

📘 Why does Apono need secrets?

Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal security.

How to create a MySQL user for Apono

1. Create user for Connector in the instance, type in some secure password

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

1. Using aws-cli, store in AWS Secret Manager, make sure to replace #SECRET_NAME,#REGION,#USERNAME, #PASSWORD

aws secretsmanager create-secret --name "#SECRET_NAME" --tags '[{"Key":"apono-connector-read","Value":"true"}]' --region #REGION --secret-string '{  
    "username":"'"apono_connector"'",  
    "password":"'"#PASSWORD"'"  
}'

1. Expose databases to apono_connector

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

1. Grant CREATE USER to apono_connector in all the databases

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

1. Select and grant apono_connector ONE of the following READ_ONLY, READ_WRITE, ADMIN permissions, this will function as the highest permission level you would like to provision with Apono

READ_ONLY

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

READ_WRITE

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'@'%';

ADMIN

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'@'%';

Required for MySQL 8.0 and above

GRANT ROLE_ADMIN on *.* to apono_connector;

How to integrate MySQL

📘 Is your MySQL running on a cloud service?

If you are trying to connect to an RDS MySQL or a CloudSQL MySQL you should use the specific cloud service integration.

1. Click on Integrations Catalog.

3. Pick a connector with network access to the MySQL databases (see prerequisites)

4. Specify the integrations details:

   • Integration name – type the name of the integration &#xNAN;When building an Access Flow you will reference this name

   • Hostname – specify the hostname of the MySQL you are connecting

   • Port – 3306

5. Provide the secret (see prerequisites)

6. Click "Connect"

MongoDB Atlas is a fully-managed cloud database service that automates database administration tasks for MongoDB. It supports multiple cloud providers and offers advanced features like real-time analytics and security controls. Atlas simplifies database management, allowing organizations to focus on application development with a scalable, flexible database solution that adapts to changing needs and workloads.

Through this integration, Apono helps you securely manage access to your MongoDB Atlas UI Organizations and Projects.

Single Mongo Cluster Integration

Prerequisites

Create an API key

You must create an API key with the Organization User role for the Apono connector.

Follow these steps to create the API key:

1. In the Atlas CLI, create the API key. The following command will return the public and private API keys in the response.

atlas organizations apiKeys create --role ORG_OWNER --desc apono_connector --orgId <ORGANIZATION_ID>

1. Using the keys from the previous step, create a secret for the MongoDB Atlas UI instance.

// Replace #PUBLIC_KEY and #PRIVATE_KEY with the actual key values.

"public_key": "#PUBLIC_KEY"
"private_key": "#PRIVATE_KEY"

You can now integrate your MongoDB Atlas UI resources .

Integrate MongoDB Atlas UI

Follow these steps to complete the integration:

1. On the Catalog tab, click Mongo Atlas Portal. The Connect Integration page appears.

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

1. Click Next. The Apono connector section expands.

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

   Organization ID

   ID of the organization of the MongoDB Atlas UI instance to connect

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.

Multiple Mongo Clusters Integration ("deep discovery")

Apono provides enhanced integration capabilities with MongoDB Atlas Portal, permitting the discovery and management of multiple clusters simultaneously. This guide outlines the prerequisites and detailed steps necessary for setting up and configuring the deep discovery integration.

To discover multiple clusters in an Organization, Apono creates a Sub Integration for every discovered cluster, with its own Databases, Documents, and Roles.

Prerequisites

Ensure you have the following items before beginning the integration process:

Create an API Key

You must create an API key with the Organization Owner role for the Apono connector.

Follow these steps to create the API key:

1. In the Atlas CLI, create the API key. The following command will return the public and private API keys in the response.

atlas organizations apiKeys create --role ORG_OWNER --desc apono_connector --orgId <ORGANIZATION_ID>

1. Using the keys from the previous step, create a secret for the MongoDB Atlas UI instance.

// Replace #PUBLIC_KEY and #PRIVATE_KEY with the actual key values.

"public_key": "#PUBLIC_KEY"
"private_key": "#PRIVATE_KEY"

Configure Apono Integration

1. Navigate to the Apono Catalog and select MongoDB Atlas Portal integration.

2. Click Connect Integration.

3. Under Discovery, select your desired resource types. Make sure to select resources under both Integration and Sub Integration: \
4. Choose your Apono Connector from the dropdown menu.

5. Enter a unique integration name.

6. Provide your MongoDB Atlas Organization ID.

7. Select the secret created in Step 2.

Configure Network Access (If Required)

For clusters in different networks or VPCs:

1. Create additional Apono Connectors in each network/VPC hosting clusters.

2. Tag each Mongo Cluster:

   Copy

   Key: apono-connector-id
   Value: <CONNECTOR_ID>

   Replace <CONNECTOR_ID> with the ID of the Apono Connector in the cluster's network.

Configure Connection Types (If Required)

Choose the appropriate connection type:

1. Standard connection: No additional configuration needed.

2. Private connection: Tag the cluster with:

   Copy

   Key: apono-connection-type
   Value: Private

3. Private endpoint connection: Apply these tags:

   Copy

   Key: apono-connection-type
   Value: PrivateEndpoint

   And:

   Copy

   Key: apono_private_endpoint_id
   Value: <PRIVATE_ENDPOINT_ID>

Finalize Integration

1. Review all configurations in the Apono integration form.

2. Click Confirm to complete the setup.

Limitations

• Deep discovery currently supports only AWS and Azure secret stores.

• All Apono Connectors must have proper network access to their MongoDB Atlas clusters.

Explore additional Apono capabilities for access management in the Apono Catalog.

Now that you have completed this integration, you can create access flows that grant permission to your MongoDB Atlas UI Organizations and Projects.

Elasticsearch is a distributed, RESTful search and analytics engine designed for horizontal scalability, reliability, and real-time search. It enables users to store, search, and analyze big volumes of data quickly and in near real-time. Elasticsearch is widely used for log and event data analysis, full-text search, and complex searches across large datasets.

Through this integration, Apono helps you securely manage access to your Elasticsearch instance.

Prerequisites

Integrate Elasticsearch

Follow these steps to complete the integration:

2. Under Discovery, click Next. The Apono connector section expands.

3. From the dropdown menu, select a connector.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Get more with Apono section expands.

4. Define the Get more with Apono settings.
5. Click Confirm.

MongoDB Atlas is a fully managed and scalable cloud database service. It provides a flexible and secure platform for storing and managing data across various applications.

Developers can easily deploy, manage, and scale MongoDB databases in the cloud. Features like automated backups, global clusters, and real-time monitoring simplify database management.

Through this integration, Apono helps you discover and securely manage access to the resources in your MongoDB Atlas instance.

Prerequisites

Create a project owner API key

A project owner API key enables Apono to control Atlas user access across a or projects.

atlas projects apiKeys create --desc cli-created --projectId "#PROJECT_ID" --role GROUP_OWNER

"public_key": "#PUBLIC_KEY",
"private_key": "#PRIVATE_KEY"

atlas projects apiKeys create --desc cli-created --projectId "#PROJECT_ID" --role GROUP_OWNER

atlas projects list

atlas projects apiKeys assign #API_KEY_ID --role GROUP_OWNER --projectId #PROJECT_ID

"public_key": "#PUBLIC_KEY",
"private_key": "#PRIVATE_KEY"

Integrate MongoDB Atlas

Follow these steps to complete the integration:

2. Under Discovery, select one or multiple resource types.

1. Click Next. The Apono connector section expands.

2. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

Snowflake is a fully managed, cloud-based data platform that functions as a data warehouse, data lake, and data sharing solution. With features such as automatic scaling, secure data sharing, and robust data integration, Snowflake offers high performance and flexibility, ensuring seamless data management and analytics.

Through this integration, Apono helps you securely manage access to your Snowflake instance.

Prerequisites

Integrate Snowflake

Follow these steps to complete the integration:

2. Under Discovery, select one or multiple resource types for Apono to discover in all instances of the environment.

3. Click Next. The Apono connector section expands.

4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.\
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

Vertica is a scalable and high-performance analytics database optimized for fast querying and analysis of large datasets. It delivers speed and flexibility for business intelligence and data warehousing applications.

Through this integration, Apono helps you securely manage access to your Vertica database and just-in-time (JIT) access to built-in and custom roles.

Prerequisites

Create a Vertica user

You must create a user in your Vertica database instance for the Apono connector and grant that user permissions to the database resources.

Follow these 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. Grant the pseudosuperuser role to the user. This allows Apono to create or drop tables and manage user roles and permissions within the Vertica database.

   Copy

   GRANT pseudosuperuser TO apono_connector;
   ALTER USER apono_connector DEFAULT ROLE pseudosuperuser;

3. Using the credentials from step 1, for the database instance.\

   Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal .

Integrate Vertica

Follow these steps to complete the integration:

2. Under Discovery, click Next. The Apono connector section expands.

3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

Redis Cloud is a fully managed, in-memory data store that functions as a database, cache, and message broker. With features such as data persistence, replication, and clustering, Redis Cloud provides high availability and fault tolerance, seamless scalability, and automated maintenance for optimal performance and reliability.

Through this integration, Apono helps you securely manage access to your Redis Cloud instance.

Prerequisite

Integrate Redis Cloud (Redislabs)

Follow these steps to complete the integration:

1. On the tab, click Redis Cloud (Redislabs). The Connect Integration page appears.

2. Under Discovery, select one or multiple resource types for Apono to discover in all instances of the environment.

3. Click Next. The Apono connector section expands.

4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

Oracle Database is a relational database management system (RDBMS) developed by Oracle Corporation. It enables organizations to store, manage, and retrieve data using Structured Query Language (SQL). The database includes features for ensuring data integrity, performing backup and recovery, controlling access, and tuning performance.

Oracle Database supports both on-premises and cloud-based deployments through Oracle Cloud Infrastructure.

Through this integration, Apono helps you securely manage just-in-time, just-enough access to your Oracle Database, tables and custom roles.

Prerequisites

Create an Oracle Database user

You must create a user in your Oracle Database instance for the Apono connector.

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

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

CREATE USER apono_connector IDENTIFIED BY password;

1. Grant the user permission to connect to the Oracle Database.

GRANT CREATE SESSION TO apono_connector;

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

GRANT SELECT ANY TABLE TO apono_connector;

1. Grant the user permissions to query data from any object, create new user accounts, modify existing user accounts, and remove user accounts from the database.

GRANT SELECT, CREATE, ALTER, DELETE FROM DBA_USERS TO apono_connector;

Integrate Oracle Database

Follow these steps to complete the integration:

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

1. Click Next. The Apono connector section expands.

2. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

PostgreSQL databases are open-source relational database management systems emphasizing extensibility and SQL compliance.

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

To enable Apono to manage 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.

Follow these 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 SUPERUSER role to the user in the database instance.

   Copy

   CREATE USER apono_connector WITH ENCRYPTED PASSWORD 'password';
   ALTER USER apono_connector WITH SUPERUSER;  

2. Using the credentials from step 1, for the database instance.

Integrate PostgreSQL

Follow these steps to complete the integration:

2. Under Discovery, select one or multiple resource types for Apono to discover in all instances of the environment.

3. Click Next. The Apono connector section expands.

4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.\
3. Click Next. The Secret Store section expands.

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

6. Define the Get more with Apono settings.\
7. Click Confirm.

​

Overview

MariaDB is a popular open-source relational database management system. Through this integration, Apono helps you securely manage access to your MariaDB database and provides just-in-time (JIT) access to built-in and custom roles, databases, and tables.

Prerequisites

• An Apono connector installed with network access to the MariaDB databases

  • Minimal Apono connector version: 1.3.0 (visit the Connectors Page and update the connector if needed)

• A user for Apono to your MariaDB with the following permissions

• A secret created in Secret Store with the following params:

  • Key username, Value MariaDB USERNAME

  • Keypassword, Value USERNAME PASSWORD

📘 Why does Apono need secrets?

Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal security

Step-by-step guide

Create a MariaDB User

1. Create user for Connector in the instance, type in some secure password

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

1. Using aws-cli, store in AWS Secret Manager, make sure to replace #SECRET_NAME,#REGION,#USERNAME, #PASSWORD

aws secretsmanager create-secret --name "#SECRET_NAME" --tags '[{"Key":"apono-connector-read","Value":"true"}]' --region #REGION --secret-string '{  
    "username":"'"apono_connector"'",  
    "password":"'"#PASSWORD"'"  
}'

1. Expose databases to apono_connector

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

1. Grant CREATE USER to apono_connector in all the databases

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

1. Select and grant apono_connector ONE of the following READ_ONLY, READ_WRITE, ADMIN permissions, this will function as the highest permission level you would like to provision with Apono

READ_ONLY

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

READ_WRITE

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'@'%';

ADMIN

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'@'%';

Integration Steps

1. On the Catalog tab, click MariaDB.

2. Pick a connector with network access to the MariaDB databases (see prerequisites)

3. Specify the integrations details:

   • Integration name – type the name of the integration &#xNAN;When building an Access Flow you will reference this name

   • Hostname – specify the hostname of the MariaDB you are connecting

   • Port – 3306

4. Provide the secret (see prerequisites)

5. Click "Connect"