@Marvin my deploy step is blocked at

Running deployment push steps...
 > Running push_to_s3 step...

how can i print out what step is taking so long?

✅ thought for 544.2 seconds

@Nate your boy marvin is always ghosting me 😉

Thanks for the details — this is a common one with the S3 push step. Short answer: the

push_to_s3

step does not print per-file progress, so it can look “stuck” while uploading many files. You can turn on debug logs (including boto3/botocore) to see what it’s doing, and/or add a quick pre-step to print how much you’re uploading. Try this first to crank up logging for Prefect and boto3/botocore:

PREFECT_DEBUG_MODE=1 \
PREFECT_LOGGING_LEVEL=DEBUG \
PREFECT_LOGGING_INTERNAL_LEVEL=DEBUG \
PREFECT_LOGGING_EXTRA_LOGGERS=boto3,botocore \
prefect deploy

(Windows PowerShell)

$env:PREFECT_DEBUG_MODE=1; $env:PREFECT_LOGGING_LEVEL='DEBUG'; $env:PREFECT_LOGGING_INTERNAL_LEVEL='DEBUG'; $env:PREFECT_LOGGING_EXTRA_LOGGERS='boto3,botocore'; prefect deploy

That will surface S3 calls/retries so you can see whether it’s actively uploading or hanging on a request. Helpful quick checks: - Make sure you’re not pushing a giant tree;

.prefectignore

is honored by the step. Common entries:

.venv/
.env
__pycache__/
.git/
node_modules/
data/
dist/
build/
*.parquet
*.csv

- Add a lightweight shell step before the push to understand scope/size:

push:
  - prefect.deployments.steps.run_shell_script:
      command: "echo Files: $(find . -type f | wc -l); echo Size: $(du -sh . | cut -f1); echo 'Top 20 largest:'; du -ah . | sort -hr | head -20"
  - prefect_aws.deployments.steps.push_to_s3:
      bucket: your-bucket
      folder: your-folder

Notes: - There isn’t built-in per-file progress output for

push_to_s3

today. - If botocore logs show a single request stalling, it’s usually networking/credentials/region. Setting AWS env like

AWS_DEFAULT_REGION

and verifying with the AWS CLI (e.g., `aws s3 ls s3://your-bucket/your-folder/`) can help isolate that. If you can, share: - Rough number of files/total size - Your

.prefectignore

contents - Any botocore debug lines where it seems to pause I can help pinpoint the bottleneck from there.

good bot

shame driven RAG