• Add AWS_SDK_GO_LOG_LEVEL environment variable support for configurable AWS SDK logging
• Add comprehensive test coverage for parseAWSLogLevel function
• Implement backward compatibility (defaults to retries,request when not set)
• Support comma-separated, case-insensitive log level values
• Update README.md with AWS SDK logging configuration documentation

Problem

Previously, the AWS SDK configuration was hardcoded to log all retries and requests (aws.LogRetries|aws.LogRequest), which could be noisy in production environments. Users had no way to control this logging behavior.

Solution

Added a new parseAWSLogLevel() function that reads the AWS_SDK_GO_LOG_LEVEL environment variable and configures the AWS SDK logging accordingly. The implementation:

• Maintains backward compatibility: When the environment variable is not set, it defaults to the original behavior (retries,request)
• Supports flexible configuration: Accepts comma-separated, case-insensitive values
• Handles invalid input gracefully: Falls back to default behavior for unrecognized values

Supported Log Levels

# Disable all logging
export AWS_SDK_GO_LOG_LEVEL=off

# Log only specific types
export AWS_SDK_GO_LOG_LEVEL=retries
export AWS_SDK_GO_LOG_LEVEL=request
export AWS_SDK_GO_LOG_LEVEL=response

# Combine multiple types
export AWS_SDK_GO_LOG_LEVEL=retries,request
export AWS_SDK_GO_LOG_LEVEL=request,response,signing

# Available options: off, retries, request, request_with_body, response, response_with_body, signing

Changes Made

1. Modified pkg/awsclicompat/session.go:

   • Added parseAWSLogLevel() function to parse the environment variable
   • Updated newConfig() to use configurable log level instead of hardcoded value
   • Added comprehensive documentation for supported values

2. Added pkg/awsclicompat/session_test.go:

   • Comprehensive test coverage for all log level combinations
   • Tests for case-insensitivity, whitespace handling, and invalid values
   • Explicit backward compatibility verification

3. Updated README.md:

   • Added AWS SDK Logging Configuration section
   • Documented all supported log levels and usage examples
   • Explained backward compatibility behavior

Impact

This change affects all AWS providers in vals (SSM, Secrets Manager, S3, KMS) that use the awsclicompat package, giving users fine-grained control over AWS SDK request logging without breaking existing functionality.

Fixes #769.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.