Glacier Deep Storage

Hello.

As you can see from the image, all of the files with a file size of "-" are folder files.
S3 folders themselves are not files, so file sizes are not displayed.
You need to click on the folder in question to directly view the sizes of the files underneath it.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-folders.html

When you create a folder in Amazon S3 console, S3 creates a 0-byte object. This object key is set to the folder name that you provided plus a trailing forward slash (/) character. For example, in Amazon S3 console, if you create a folder named photos in your bucket, the Amazon S3 console creates a 0-byte object with the key photos/. The console creates this object to support the idea of folders.

When you store objects in S3 Glacier Deep Archive, the way file sizes are displayed in the AWS Management Console can sometimes be confusing. The "-" you're seeing for some files doesn't necessarily mean there's no data or that the files are empty.

This is likely happening because S3 Glacier Deep Archive is designed for long-term archival storage with infrequent access. Objects stored in this storage class are not immediately accessible and require a restore operation before you can access them. The console may not display the size for these archived objects until they're restored.

Additionally, there are a few other factors that could contribute to this display issue:

1. The files might still be in the process of transitioning to the Glacier Deep Archive storage class, as transitions are asynchronous and can take some time to complete.

2. There might be a display issue in the console itself, where it's not showing the size for certain archived objects.

3. For objects in Glacier Deep Archive, AWS adds 40 KB of additional metadata (32 KB for identification and retrieval data, plus 8 KB for maintaining user-defined name and metadata), which might affect how sizes are calculated and displayed.

If you want to verify the actual size of these objects, you could use the AWS CLI with the s3api list-objects-v2 command to get more detailed information about your objects, including their exact byte sizes.

Rest assured that if you successfully uploaded your 4K video files to the bucket, they should still be there with their content intact, even if the size isn't displaying properly in the console.
Sources
Understanding S3 Glacier storage classes for long-term data storage - Amazon Simple Storage Service
S3 Glacier Deep Archive file size discrepancy | AWS re:Post