MariaDB
Create an integration to manage access to a MariaDB instance
The MariaDB integration enables you to securely manage just-in-time (JIT) access to roles, databases, and tables within your MariaDB instance.
Prerequisite
Apono Connector
On-prem connection serving as a bridge between a MariaDB instance and Apono:
Create a MariaDB user
You must create a user in your MariaDB instance for the Apono connector and grant that user permissions to your databases.
Follow these steps to create a user and grant it permissions:
In your preferred client tool, create a new user. Use apono_connector or another name of your choosing for the username. Be sure to set a strong password for the user.
Expose the databases to the user. This allows Apono to view database names without accessing the contents of each database.
Grant database permissions to the user. The following commands grant Apono the following permissions:
Creating users
Updating user information and privileges
Monitoring and troubleshooting processes running on the database
Grant the user only one of the following sets of permissions. The chosen set defines the highest level of permissions to provision with Apono.\
Click on each tab to reveal the SQL commands.
Allows Apono to read data from databases
Create a secret with the credentials from step 1. 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, replaceapono-connector
with the name you assigned to the user.
You can also input the user credentials directly into the Apono UI during the integration process.
You can now integrate your MariaDB database.
Integrate MariaDB
You can also use the steps below to integrate with Apono using Terraform.
In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.
Follow these steps to complete the integration:
On the Catalog tab, click MariaDB. The Connect Integration page appears.
Under Discovery, click Next. The Apono connector section expands.
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.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).
Click Next. The Integration Config section expands.
Define the Integration Config settings.
SettingDescriptionIntegration Name
Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow
Hostname
Hostname of the MariaDB instance to connect
Port
Port value for the instance By default, Apono sets this value to 3306.
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.\
SettingDescriptionCredential 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
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
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
Enter a Key name. This value is the name of the tag created in your cloud environment.
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.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your MariaDB database.
Last updated
Was this helpful?