# Apono Secret Alternative

{% hint style="danger" %}
**We do not recommend using the Apono Secret alternative in any production environment.**

We advise creating a secret in an [AWS](https://docs.apono.io/docs/apono-connector-for-aws) , [Azure](https://docs.apono.io/docs/apono-azure-connector) , [GCP](https://docs.apono.io/docs/apono-connector-for-gcp) , or [Kubernetes](https://docs.apono.io/docs/apono-connector-for-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.
{% endhint %}

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

<figure><img src="https://1094436629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv6MBfUGvblSdAz31yJXm%2Fuploads%2Fgit-blob-1f0c4049ab8dbd30527d791e69e29d46cebcb59c%2FApono-Secret-Alternative-1.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Follow these steps to add resource-specific credentials to test an integration:

1. Expand **Secret Store**, click on the **APONO** tab.
2. Enter the required credential information for the resource.

<details>

<summary>Amazon Redshift</summary>

* Username
* Password

</details>

<details>

<summary>Azure Kubernetes Service (AKS)</summary>

* Enter the Service Account Token

</details>

<details>

<summary>Elastic Kubernetes Service (EKS)</summary>

* Enter the Service Account Token

</details>

<details>

<summary>F5 Network</summary>

* Enter the admin Username
* Enter the admin Password

</details>

<details>

<summary>Github</summary>

* Enter the database Github Token (Personal Access Token)

</details>

<details>

<summary>Google Cloud SQL - MySQL</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>Google Cloud SQL - PostgreSQL</summary>

* Enter the database Username\* Enter the database Password

</details>

<details>

<summary>Google Kubernetes Engine (GKE)</summary>

* Enter the Service Account Token

</details>

<details>

<summary>JumpCloud</summary>

* Enter the Jumpcloud API Token

</details>

<details>

<summary>Kubernetes</summary>

* Enter the database Service Account Token

</details>

<details>

<summary>LDAP Group</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>Microsoft SQL Server</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>MongoDB</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>MongoDB Atlas</summary>

* Enter the database Public Key
* Enter the database Private Key

</details>

<details>

<summary>MongoDB Atlas Portal</summary>

* Enter the database Public Key
* Enter the database Private Key

</details>

<details>

<summary>MySQL</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>Okta Group</summary>

* Enter the Okta API Token

OR

* Enter the Okta Client ID
* Enter the Private Key

</details>

<details>

<summary>OneLogin</summary>

* Enter the Client Id
* Enter the Client Secret

</details>

<details>

<summary>Oracle Database</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>PostgreSQL</summary>

* Enter the database Username
* Enter the database Password

</details>

<details>

<summary>SSH</summary>

* Enter the Base64 Private Key OR Password

</details>

<details>

<summary>Vertica</summary>

* Enter the database Username
* Enter the database Password

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apono.io/docs/connectors-and-secrets/apono-secret-alternative.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.