Derived Images not working

If the derived image downloads (jpgs) aren't working then it is either an issue with the code or the S3 bucket configuration. These instructions are similar to the dzi bucket instructions but adjusted for name and variable(s) in the local_env.yml file that are called on.

1. Go to https://status.aws.amazon.com/ and check for the S3 bucket health in the N. Virginia region. If they show as unhealthy, the issue is an AWS-wide problem. This also means the viewer will be broken likely.
2. If the S3 bucket for N. Virginia shows as healthy, it may be a configuration issue.
   1. The CORS configuration needs to be set to allow requests from other domains. Currently we allow requests from any site and it should be:
      1. <?xml version="1.0" encoding="UTF-8"?>
         <CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
         <CORSRule>
         <AllowedOrigin>*</AllowedOrigin>
         <AllowedMethod>GET</AllowedMethod>
         <MaxAgeSeconds>43200</MaxAgeSeconds>
         <AllowedHeader>*</AllowedHeader>
         </CORSRule>
         </CORSConfiguration>
   2. There should also be a bucket policy that allows access to the objects, objects often have a unique policy to allow access, but the Bucket policy confirms that access is allowed and a missing object permission doesn't break something. The policy should be:

      1. {

         "Version": "2012-10-17",

         "Statement": [

         {

         "Sid": "Add Permission to access from staging",

         "Effect": "Allow",

         "Principal": "*",

         "Action": "s3:GetObject",

         "Resource": "arn:aws:s3:::chf-dzi-production/*"

         }

         ]

         }

   3. If both of these are accurate then it is not a policy issue.
3. If it is not an AWS outage or a policy issue, it is probably a code issue.