Environment variables are not getting resolved when passing config through SSM

[anilgvpcoe]

Describe the question
We are using aws distro sidecar for our ECS tasks. Based on config-through-ssm we configured a secret and are passing the config to AWS distro, this works fine when config has actual values as below

receivers:
    otlp:
      protocols:
          grpc:
          http:
    prometheus:
      config:
        scrape_configs:
          - job_name: 'local-spring-boot-actuator'
            metrics_path: '/<service-name>/mgmt/prometheus'

However in our case we want to use env variables instead of hardcoding values in config. So we updated config to

receivers:
    otlp:
      protocols:
          grpc:
          http:
    prometheus:
      config:
        scrape_configs:
          - job_name: 'local-spring-boot-actuator'
            metrics_path: '/${SERVICE_NAME}/mgmt/prometheus'

and added SERVICE_NAME env variable in container. Now when aws-distro starts it is unable to reach the same destination we keep getting connect exception in logs.

Is this expected and are there sample configs we can refer to for using env variables in config file

Steps to reproduce if your question is related to an action
Add some env variables in ECS task container. Use the env variables in a config file and load the config file through SSM or secret. Check if env variables are resolving to actual values at runtime.

What did you expect to see?
ENV variables should be resolved to actual values as mentioned here

Environment

• ECS task with aws-distro as a sidecar container
• Config is being loaded via AOT_CONFIG_CONTENT pointing to a secret

Additional context
Please let me know if you need more info

[jefchien]

Hi @anilgvpcoe,

This is a known issue and a fix was made in #774. Two patches are being released (v0.14.2 and v0.15.1) today to fix this. I will let you know when it is available.

[jefchien]

We've released v0.14.2 and v0.15.1 (latest). Please use one of these releases.

[anilgvpcoe]

Awesome thank you so much for quick response @jefchien 🙏 , I will try v0.15.1

[anilgvpcoe]

thank you, can confirm this is working with 0.15.1