So as the title denotes when image is uploaded via awscli on the storage backend the file is still a file. Awscli for writing or pulling is able to work on the file as expected. With s3fs mounted on 8.8 or 8.10 redhat though new image content shows as a folder. However S3 acl is identical between old and new images. Old images show up as expected. Backed storage which is a powerscale the files show up as expected and identical ls -led outputs. I would assume if the permissions were different per file in different folders on the backend that might explain it as a bug potentially but unfortunately not the case.

s3fs --version
Amazon Simple Storage Service File System V1.95 with OpenSSL

pkg-config --modversion fuse
2.9.7

Readable File

-rwxrwxr-x 1 root root 1378439799 Sep 25 14:40 File_Old.svs

Non-Readable File

drwxrwxr-x 1 root root 4096 Oct 9 10:21 File_New.svs

Mounting Logs

Oct 14 10:33:25 LocalServer s3fs[1164138]: s3fs_logger.cpp:LowSetLogLevel(233): change debug level from [CRT] to [DBG]
Oct 14 10:33:25 LocalServer s3fs[1164138]: PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40777)
Oct 14 10:33:25 LocalServer s3fs[1164138]: Loaded mime information from /etc/mime.types
Oct 14 10:33:25 LocalServer s3fs[1164138]: The path to cache top dir is empty, thus not need to check permission.
Oct 14 10:33:25 LocalServer s3fs[1164138]: Free space ratio default to 10 %, ensure the available disk space is greater than 13919.600 MB
Oct 14 10:33:25 LocalServer s3fs[1164139]: init v1.95 with OpenSSL, credential-library(built-in)
Oct 14 10:33:25 LocalServer s3fs[1164139]: check services.
Oct 14 10:33:25 LocalServer s3fs[1164139]: check a bucket path(/).
Oct 14 10:33:25 LocalServer s3fs[1164139]: URL is https://S3_Storage:port/bucket/
Oct 14 10:33:25 LocalServer s3fs[1164139]: URL changed is https://S3_Storage:port/bucket/
Oct 14 10:33:25 LocalServer s3fs[1164139]: computing signature [GET] [/] [] []
Oct 14 10:33:25 LocalServer s3fs[1164139]: url is https://S3_Storage:port
Oct 14 10:33:26 LocalServer s3fs[1164139]: HTTP response code 200
Oct 14 10:33:26 LocalServer s3fs[1164139]: Any threads are running now, then nothing to do.
Oct 14 10:33:26 LocalServer s3fs[1164139]: Start worker thread in ThreadPoolMan.
Oct 14 10:33:26 LocalServer s3fs[1164139]: Start worker thread in ThreadPoolMan.
Oct 14 10:33:26 LocalServer s3fs[1164139]: Start worker thread in ThreadPoolMan.
Oct 14 10:33:26 LocalServer s3fs[1164139]: Start worker thread in ThreadPoolMan.
Oct 14 10:33:26 LocalServer s3fs[1164139]: Start worker thread in ThreadPoolMan.
Oct 14 10:33:28 LocalServer s3fs[1164139]: [path=/][pid=1164153,uid=0,gid=0]
Oct 14 10:33:28 LocalServer s3fs[1164139]: [tpath=//]
Oct 14 10:33:28 LocalServer s3fs[1164139]: [tpath=//][bpath=][save=][sseckeypos=#'s]
Oct 14 10:33:28 LocalServer s3fs[1164139]: URL is https://S3_Storage:port/bucket//
Oct 14 10:33:28 LocalServer s3fs[1164139]: URL changed is https://S3_Storage:port/bucket//
Oct 14 10:33:28 LocalServer s3fs[1164139]: computing signature [HEAD] [//] [] []
Oct 14 10:33:28 LocalServer s3fs[1164139]: url is https://S3_Storage:port
Oct 14 10:33:28 LocalServer s3fs[1164139]: HTTP response code 200
Oct 14 10:33:28 LocalServer s3fs[1164139]: add stat cache entry[path=/]