Trying to setup AWS Secrets Manager, and added the values in the .env file for

SECRET_PERSISTENCE

,

AWS_ACCESS_KEY

, and

AWS_SECRET_ACCESS_KEY

based on this documentation: https://docs.airbyte.com/operator-guides/configuring-airbyte/ but I’m getting this error when I bring Airbyte back up

| 2023-05-22 13:56:11 ERROR i.m.r.Micronaut(handleStartupException):338 - Error starting Micronaut server: Error instantiating bean of type  [io.airbyte.config.persistence.split_secrets.SecretsHydrator]
airbyte-worker                    |
airbyte-worker                    | Message: awsAccessKey cannot be empty, to use a default region call AWSSecretManagerPersistence.AWSSecretManagerPersistence()
airbyte-worker                    | Path Taken: new ApplicationInitializer() --> ApplicationInitializer.checkConnectionActivities --> List.checkConnectionActivities([CheckConnectionActivity checkConnectionActivity]) --> new CheckConnectionActivityImpl(WorkerConfigsProvider workerConfigsProvider,ProcessFactory processFactory,[SecretsHydrator secretsHydrator],Path workspaceRoot,WorkerEnvironment workerEnvironment,LogConfigs logConfigs,AirbyteApiClient airbyteApiClient,String airbyteVersion,AirbyteMessageSerDeProvider serDeProvider,AirbyteProtocolVersionedMigratorFactory migratorFactory,FeatureFlags featureFlags) --> SecretsHydrator.secretsHydrator([SecretPersistence secretPersistence])
airbyte-worker                    | io.micronaut.context.exceptions.BeanInstantiationException: Error instantiating bean of type  [io.airbyte.config.persistence.split_secrets.SecretsHydrator]
airbyte-worker                    |
airbyte-worker                    | Message: awsAccessKey cannot be empty, to use a default region call AWSSecretManagerPersistence.AWSSecretManagerPersistence()

A message from kapa.ai

Airbyte version

0.44.5

I was looking into this issue, and it looks like the variables from

.env

are not set in

docker-compose.yaml

to get passed to the container. You will need to add some lines in

docker-compose.yaml

under

services: server: environment:

- AWS_ACCESS_KEY=${AWS_ACCESS_KEY}
      - AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY}

I have not been able to test this out, but if that doesn’t work, you may need to add the lines under

services: worker: environment:

as well. Let me know if you have any issues!

🤔 that makes sense; will test (once the syncs finish) and let you know!