Image do not show AWS S3 images - "url" parameter is valid but upstream response is invalid

What version of Next.js are you using?

12.0.2, 12.0.7

What version of Node.js are you using?

16.13.0

What browser are you using?

Chrome

What operating system are you using?

Linux

How are you deploying your application?

next start

Describe the Bug

Possible duplication of https://github.com/vercel/next.js/issues/31377 Showing protected images from AWS S3 resulting with error:

"url" parameter is valid but upstream response is invalid

The s3 bucket policy:

{
    "Version": "2012-10-17",
    "Id": "http referer policy example",
    "Statement": [
        {
            "Sid": "Allow get requests originating from domainss",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject",
                "s3:GetObjectVersion"
            ],
            "Resource": "arn:aws:s3:::web/*",
            "Condition": {
                "StringLike": {
                    "aws:Referer": [
                        "http://localhost:3000/*"
                    ]
                }
            }
        }
    ]
}

nextjs config:

  images: {
    domains: [
      'localhost',
      'web.s3.eu-west-1.amazonaws.com'
    ],
  },

Code:

<Image src={`${assets}/img/home-page/plugins.png`} width="800" height="470" alt="Plugins" />

Only way to make it work is by adding the unoptimized={true} for Image.

Expected Behavior

Show optimized Image from aws S3

To Reproduce

Use code from the description.

[styfle]

Feel free to create a new Discussion to discuss this idea further.

We would want to see more about how users would use this feature before implementing. Some topics of discussion:

• Should Referrer be hardcoded or should it be forwarded so it matches the browser?
• Are there other headers that should be assigned such as User-Agent?
• Whats preventing other proxies from mimicking these headers to retrieve the source image? (not a real form of security IMO)

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.