Hi all, I am starting to use MetaFlow again and DevOps kindly restarted and upgraded metaflow in our AWS. They also provided me with credentials for an AWS profile I use in VSC called

metaflow

. Alas, when I run some old flow I now get: 2024-03-14 155544.056 [15/bootstrap/49 (pid 63008)] [4f628202-99d3-45ab-8dd0-968c47c65809] Environment bootstrapped. 2024-03-14 155545.810 [15/bootstrap/49 (pid 63008)] [4f628202-99d3-45ab-8dd0-968c47c65809] <flow BlaFlow step bootstrap> failed: 2024-03-14 155546.795 [15/bootstrap/49 (pid 63008)] [4f628202-99d3-45ab-8dd0-968c47c65809] S3 access denied: 2024-03-14 155546.795 [15/bootstrap/49 (pid 63008)] [4f628202-99d3-45ab-8dd0-968c47c65809] s3://metaflow-684414486554-s3-55ff636/metaflow/BlaFlow/data/d0/d02b58387a6fdeb3e003a4526d3e8960d5f6056e 2024-03-14 155546.795 [15/bootstrap/49 (pid 63008)] [4f628202-99d3-45ab-8dd0-968c47c65809] 2024-03-14 155611.460 [15/bootstrap/49 (pid 63008)] AWS Batch error: 2024-03-14 155611.554 [15/bootstrap/49 (pid 63008)] Essential container in task exited This could be a transient error. Use @retry to retry. I assume this has to do with the fact that the AWS

metaflow

profile I use does not have certain rights? Does this ring a bell? Thanks! I invoke code like so (worked in the past:

python3 BlaFlow.py --environment=conda --package-suffixes .sql run \
--p11 1.00 \
--p2 1.2 \
--s3_bucket_name bal --with batch