Target API credentials / Environment variables support

[AliAllomani]

Is your feature request related to a problem? Please describe.

I would like to run load testing using locust on an API which requires authentication, I could not find a method in the docs or the UI to define environment variables, or secrets references (e.g. from Secrets Manager) for credentials to be provided to the test.

Describe the feature you'd like

Additional context

[daznian]

At this time, DLT does not have built-in support for injecting environment variables or secrets into test containers. The ECS task environment only receives test metadata (test ID, S3 bucket, etc.), and there is no UI mechanism to define custom environment variables or reference secrets.

As a workaround, you can retrieve credentials programmatically within your test script using the AWS SDK, since the test container runs as an ECS Fargate task with an IAM task role. You would also need to attach a policy granting the appropriate read permissions to the DLT task execution role.

We'd like to better understand your use case. Which AWS service were you planning to use to store your secrets (e.g., AWS Secrets Manager, SSM Parameter Store)? This would help us prioritize and scope native support for this feature.

[AliAllomani]

Thanks @daznian for the prompt response

I’m aware of the manual changes that can be done to achieve the required results but I was looking for more of out of the box method as part of the solution.

Ideally I would like to see options to define environment variables as part of the scenario definition, string environment variables for non-sensitive values and secrets references for sensitive values either from parameter store or secrets manager. automatically creating/updating ecs tasks roles with the required scoped permissions per test scenario would be a big advantage as well.

[daznian]

Thank you for the feedback @AliAllomani. Our team will review this information and prioritize it appropriately.