I think I’ve got the solution. There’s a problem with the implementation of AWS Dual Stack which is being used to access AWS S3.
The SSL certificate being provided by AWS is for *.s3-ap-southeast-2.amazonaws.com, however this is not actually the base for the subdomain being used to access the images, which is mediaspy-org-s3.s3.dualstack.ap-southeast-2.amazonaws.com - it will cause an issue for anyone with certain high security settings in place.
If there’s a way to disable Dualstack and access the images through https:// mediaspy-org-s3.s3-ap-southeast-2.amazonaws.com that should resolve the problem.
For example:
Using Dualstack:
Not using Dualstack:
