The AWS provider currently requires aws_access_key and aws_secret_key in the config block. This blocks running cloudlist in environments where static keys are not used, e.g. IRSA on EKS, EC2/ECS instance profiles, or AWS_* environment variables.
Both keys should be optional. When omitted, the provider should fall back to the AWS SDK default credential chain so credentials are resolved from IRSA web identity, instance/task metadata, environment variables, or shared config.
Requirements:
- Make
aws_access_key / aws_secret_key optional.
- If only one of the pair is set, error out (a half-configured pair is a mistake).
- Keep existing static-key and assume-role flows working unchanged.
Tracked by #751.
The AWS provider currently requires
aws_access_keyandaws_secret_keyin the config block. This blocks running cloudlist in environments where static keys are not used, e.g. IRSA on EKS, EC2/ECS instance profiles, orAWS_*environment variables.Both keys should be optional. When omitted, the provider should fall back to the AWS SDK default credential chain so credentials are resolved from IRSA web identity, instance/task metadata, environment variables, or shared config.
Requirements:
aws_access_key/aws_secret_keyoptional.Tracked by #751.