s3 cp is stuck/hanging to complete uploading 1TB file

[ghnp5]

Hi,

I am attempting to upload a 1TB VeraCrypt container to S3 Deep Archive.

I have this profile:

[profile s3bucket]
aws_access_key_id = <key>
aws_secret_access_key = <key>
max_attempts = 10
retry_mode = standard

And ran this command:

aws s3 cp D:\Backup.vc s3://my-bucket-name/ --storage-class DEEP_ARCHIVE --profile s3bucket --output text --debug --cli-connect-timeout 0

It spent several hours uploading all the data (and I could see the progress consistently, going up toward 1TB of data sent). And then I went to sleep.

However, for over 4 hours, it's been stuck here:

2025-04-07 06:31:47,350 - ThreadPoolExecutor-0_8 - s3transfer.utils - DEBUG - Releasing acquire 0/None
2025-04-07 06:31:50,232 - ThreadPoolExecutor-0_3 - urllib3.connectionpool - DEBUG - https://my-bucket-name.s3.us-west-2.amazonaws.com:443 "PUT /Backup.vc?uploadId=[REDACTED]&partNumber=8189 HTTP/1.1" 200 0
2025-04-07 06:31:50,233 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event before-parse.s3.UploadPart: calling handler <function _handle_200_error at 0x000001E7E8017A60>
2025-04-07 06:31:50,234 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event before-parse.s3.UploadPart: calling handler <function handle_expires_header at 0x000001E7E8017880>
2025-04-07 06:31:50,234 - ThreadPoolExecutor-0_3 - botocore.parsers - DEBUG - Response headers: {'x-amz-id-2': '[REDACTED]', 'x-amz-request-id': '[REDACTED]', 'Date': 'Mon, 07 Apr 2025 05:31:09 GMT', 'ETag': '"[REDACTED]"', 'x-amz-checksum-crc64nvme': '[REDACTED]', 'x-amz-server-side-encryption': 'AES256', 'x-amz-storage-class': 'DEEP_ARCHIVE', 'Content-Length': '0', 'Server': 'AmazonS3'}
2025-04-07 06:31:50,234 - ThreadPoolExecutor-0_3 - botocore.parsers - DEBUG - Response body:
b''
2025-04-07 06:31:50,235 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <function _update_status_code at 0x000001E7E8017BA0>
2025-04-07 06:31:50,235 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <bound method RetryHandler.needs_retry of <botocore.retries.standard.RetryHandler object at 0x000001E7EA392D20>>
2025-04-07 06:31:50,236 - ThreadPoolExecutor-0_3 - botocore.retries.standard - DEBUG - Not retrying request.
2025-04-07 06:31:50,236 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <bound method S3RegionRedirectorv2.redirect_from_error of <botocore.utils.S3RegionRedirectorv2 object at 0x000001E7EA392A80>>
2025-04-07 06:31:50,236 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event after-call.s3.UploadPart: calling handler <function enhance_error_msg at 0x000001E7E976A020>
2025-04-07 06:31:50,237 - ThreadPoolExecutor-0_3 - botocore.hooks - DEBUG - Event after-call.s3.UploadPart: calling handler <bound method RetryQuotaChecker.release_retry_quota of <botocore.retries.standard.RetryQuotaChecker object at 0x000001E7EA3920F0>>
2025-04-07 06:31:50,237 - ThreadPoolExecutor-0_3 - s3transfer.utils - DEBUG - Releasing acquire 0/None
2025-04-07 06:31:50,374 - ThreadPoolExecutor-0_4 - urllib3.connectionpool - DEBUG - https://my-bucket-name.s3.us-west-2.amazonaws.com:443 "PUT /Backup.vc?uploadId=[REDACTED]&partNumber=8192 HTTP/1.1" 200 0
2025-04-07 06:31:50,375 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event before-parse.s3.UploadPart: calling handler <function _handle_200_error at 0x000001E7E8017A60>
2025-04-07 06:31:50,375 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event before-parse.s3.UploadPart: calling handler <function handle_expires_header at 0x000001E7E8017880>
2025-04-07 06:31:50,375 - ThreadPoolExecutor-0_4 - botocore.parsers - DEBUG - Response headers: {'x-amz-id-2': '[REDACTED]', 'x-amz-request-id': '[REDACTED]', 'Date': 'Mon, 07 Apr 2025 05:31:33 GMT', 'ETag': '"[REDACTED]"', 'x-amz-checksum-crc64nvme': '[REDACTED]', 'x-amz-server-side-encryption': 'AES256', 'x-amz-storage-class': 'DEEP_ARCHIVE', 'Content-Length': '0', 'Server': 'AmazonS3'}
2025-04-07 06:31:50,376 - ThreadPoolExecutor-0_4 - botocore.parsers - DEBUG - Response body:
b''
2025-04-07 06:31:50,376 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <function _update_status_code at 0x000001E7E8017BA0>
2025-04-07 06:31:50,376 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <bound method RetryHandler.needs_retry of <botocore.retries.standard.RetryHandler object at 0x000001E7EA392D20>>
2025-04-07 06:31:50,377 - ThreadPoolExecutor-0_4 - botocore.retries.standard - DEBUG - Not retrying request.
2025-04-07 06:31:50,377 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event needs-retry.s3.UploadPart: calling handler <bound method S3RegionRedirectorv2.redirect_from_error of <botocore.utils.S3RegionRedirectorv2 object at 0x000001E7EA392A80>>
2025-04-07 06:31:50,377 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event after-call.s3.UploadPart: calling handler <function enhance_error_msg at 0x000001E7E976A020>
2025-04-07 06:31:50,378 - ThreadPoolExecutor-0_4 - botocore.hooks - DEBUG - Event after-call.s3.UploadPart: calling handler <bound method RetryQuotaChecker.release_retry_quota of <botocore.retries.standard.RetryQuotaChecker object at 0x000001E7EA3920F0>>
2025-04-07 06:31:50,378 - ThreadPoolExecutor-0_4 - s3transfer.utils - DEBUG - Releasing acquire 0/None

Absolutely no further output, and doesn't seem "crashed" yet (meaning, the command is still running, not exited),
and the file isn't in listed the bucket yet.

Is this normal?

I'm afraid of killing the command and then have to start over, without any guarantee it won't do the same again.

Any ideas?
Thanks!