Getting an error now with MySQL source connector:

Internal message: io.airbyte.workload.launcher.pipeline.stages.model.StageError: java.lang.RuntimeException: That secret was not found in the store!

The error message you're seeing indicates that Airbyte is unable to locate the secret for the MySQL source connector in the secret store. This could be due to a few reasons: 1. The secret might not have been correctly stored in the secret store. Airbyte's default behavior is to store connector secrets on your configured database in plain-text. However, it is highly recommended to store connector secrets in an external secret manager like AWS Secrets Manager, Google Secrets Manager, or Hashicorp Vault to ensure secrets are not exposed ([source](https://docs.airbyte.com/deploying-airbyte/integrations/secrets)). 2. There might be an issue with the permissions or access to the secret store. Ensure that the Airbyte server and the entire stack (docker or k8s) has read and write access to the secret vault you choose to use ([source](https://github.com/airbytehq/airbyte/issues/36442)). 3. If you're using a secret manager like Hashicorp Vault, there might be an issue with the SSL connection. There have been instances where an SSL exception is thrown while trying to persist connection secrets/tokens to Hashicorp vault from within the Airbyte UI ([source](https://github.com/airbytehq/airbyte/issues/22065)). If you're still facing issues, it would be helpful to check the logs for more detailed error messages. You can also consider raising an issue in the [Airbyte Github repository](https://github.com/airbytehq/airbyte/issues) or ask for help in the [Airbyte community forum](https://discuss.airbyte.io/).

@kapa.ai Using AWS secrets manager, and all other connectors are working fine

That's great to hear! AWS Secrets Manager is a supported secret manager in Airbyte and it helps to ensure that your secrets (e.g. OAuth tokens, database passwords) are not exposed. However, please note that if you modify the configuration of connector secret storage, all existing connectors will fail. You will need to recreate these connectors to ensure they are reading from the appropriate secret store. If you're authenticating with credentials, make sure you've already created a Kubernetes secret containing both your AWS Secrets Manager access key ID, and secret access key. By default, secrets are expected in the

airbyte-config-secrets

Kubernetes secret, under the

aws-secret-manager-access-key-id

and

aws-secret-manager-secret-access-key

keys. Here is an example of how to configure the secrets manager:

yaml global:     secretsManager:       type: awsSecretManager       awsSecretManager:         region: <aws-region>         authenticationType: credentials ## Use "credentials" or "instanceProfile"         tags: ## Optional - You may add tags to new secrets created by Airbyte.           - key: ## e.g. team             value: ## e.g. deployments           - key: business-unit             value: engineering         kms: ## Optional - ARN for KMS Decryption.

For more information, you can refer to the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/integrations/secrets#values). If you encounter any issues, don't hesitate to report them on the [Airbyte Github page](https://github.com/airbytehq/airbyte/issues).

@kapa.ai if I try to update the MySQL connector, I now get this error

An unexpected error occurred. Please report this if the issue persists. (HTTP 500)

A message from kapa.ai

I'm sorry to hear that you're experiencing issues with updating the MySQL connector. This error message typically indicates a server-side error. Here are a few steps you can take to troubleshoot this issue: 1. Check the server logs: The error message you're seeing is quite generic, so it's hard to determine the exact cause without more information. The server logs should provide more detailed information about what went wrong. You can usually find these logs in the Airbyte dashboard under the

Logs

section. 2. Try updating the connector again: Sometimes, transient issues can cause operations to fail. Try updating the connector again to see if the issue persists. 3. Check the connector version: Make sure that the version of the MySQL connector you're trying to update to is compatible with your current Airbyte instance. If none of these steps help, I would recommend creating a new post on the [Airbyte discussion forum](https://discuss.airbyte.io/) or opening a new issue on the [Airbyte Github page](https://github.com/airbytehq/airbyte/issues) with the error details and server logs. The Airbyte team or community may be able to provide more specific guidance. For more information on troubleshooting, you can refer to the [MySQL troubleshooting guide](https://docs.airbyte.com/integrations/sources/mysql/mysql-troubleshooting) in the Airbyte documentation.