#1523 prefer FLYTE_ prefixed AWS creds env vars Pull request opened by flixr TL;DR use FLYTE_AWS_ACCESS_KEY_ID and FLYTE_AWS_SECRET_ACCESS_KEY via config if they exist instead of AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY so that user code can inject and use these default AWS creds env vars Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description flytekit will used the

AWS_ACCESS_KEY_ID

env var instead of the also existing

FLYTE_AWS_ACCESS_KEY_ID

env if the former exists in the container.... this made my task which needs to retrieve data from a different bucket with different creds (injected via secret) fail upon downloading/uploading flyte inputs/output. Tracking Issue NA Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks