Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.7.1

Current Behavior

Hi Team,

Kong version: 3.7.1 (OSS)
Deployed on AWS EKS version 1.32

I trying to integrate basic_auth credentials as envrionment variable rather hardcoded value in my kong config.
If I use hardcoded value it works and I get 200 OK.
Same value created as K8s secret and integrated as env variable on kong pod throws 401 error.

Here is my config looks like:
dblessConfig:
vaults:
- name: env # This name must match the 'env' in vault://env/
description: "Environment Variable Vault Backend"
config: |
_format_version: "1.1"
consumers:
- acls:
- group: monitoring
basicauth_credentials:
- password: "{vault://env/MONITORING_BASICAUTH}"
username: monitoring
username: monitoring

The env name: MONITORING_BASICAUTH is present in pod and value is all correct.

My final requirement is to fetch the secret from AWS secret manager and use it as env variable, which partialy working as env variable coming from AWS to k8s pod but using the same didnt work and getting 401 error.
So I tried creating k8s secret and checked but same result.

Expected Behavior

Secret created as env variable should work and give 200 OK.

Steps To Reproduce

No response

Anything else?

No response