Provide Apono with credentials to authenticate an integration
We do not recommend using the Apono Secret alternative in any production environment.
We advise creating a secret in an AWS , Azure , GCP , or Kubernetes environment. Managing secrets in a Secret Store allows Apono to sync and provision access to cloud resources without needing to store credentials for a specific environment in Apono.
During the process of setting up most integrations, you will be prompted to enter secret information associated with the integration, so that the connector can list and provision the integration's resources.
This Apono secret alternative is an authentication solution that allows Apono to sync and provision access to cloud resources with stored credentials. We recommend using this for development and testing purposes.
Add credentials
Follow these steps to add resource-specific credentials to test an integration:
Expand Secret Store, click on the APONO tab.
Enter the required credential information for the resource.
Amazon Redshift
Username
Password
Azure Kubernetes Service (AKS)
Enter the Service Account Token
Elastic Kubernetes Service (EKS)
Enter the Service Account Token
F5 Network
Enter the admin Username
Enter the admin Password
Github
Enter the database Github Token (Personal Access Token)
Google Cloud SQL - MySQL
Enter the database Username
Enter the database Password
Google Cloud SQL - PostgreSQL
Enter the database Username* Enter the database Password
