@ancient-wolf-19325, I get the following error: │ │ /opt/venv/lib/python3.10/site-packages/flytekit/bin/entrypoint.py:442 in │ │ _execute_task │ │ │ │ ❱ 442 │ │ _dispatch_execute(ctx, load_task, inputs, output_prefix) │ │ │ │ /opt/venv/lib/python3.10/site-packages/flytekit/bin/entrypoint.py:215 in │ │ _dispatch_execute │ │ │ │ ❱ 215 │ ctx.file_access.put_data(ctx.execution_state.engine_dir, output_pr │ │ │ │ /opt/venv/lib/python3.10/site-packages/flytekit/core/data_persistence.py:593 │ │ in put_data │ │ │ │ ❱ 593 │ │ │ raise FlyteUploadDataException( │ ╰──────────────────────────────────────────────────────────────────────────────╯ FlyteUploadDataException: SYSTEMUploadDataError error=Failed to put data from /tmp/flytefppywths/local_flytekit/engine_dir to s3:///metadata/propeller/flytesnacks-development-fksdi-c3m2/ n1/data/0 (recursive=True). Original exception: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to., cause=The unspecified location constraint is incompatible for the region specific endpoint this request was sent to.

It seems likely that the error you're encountering is related to a mismatch between the S3 bucket's region and the endpoint being used for the upload. This can happen if the S3 bucket is created in a specific region, but the request is being sent to a different region's endpoint. My understanding is that you should verify the region configuration for your S3 bucket and ensure that the Flyte setup is using the correct endpoint for that region. You might need to check your AWS configuration or Flyte's deployment settings to ensure they align with the S3 bucket's region. Would you like more details on how to address this issue or any other aspect of Flyte? Sources: - Flyte Community Discussion 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@quaint-spring-40580 please. move this convo either to #C06H1SFA19R or #CP2HDHKE1. Thanks