horaceshmorace / image-flex Goto Github PK

The region is currently hardcoded to us-east-1. The developers should be able to set a region.

Hi, I'm facing the following error with some images that are a little bit heavy, around 5MB. Did you face this error too? Or do you know a workaround for this? Unfortunately, the memory limit to lambda@edge is 256MB :(

{
    "errorType": "Error",
    "errorMessage": "VipsJpeg: Insufficient memory (case 4)\n",
    "stack": [
        "Error: VipsJpeg: Insufficient memory (case 4)",
        ""
    ]
}

From AWS: We are ending support for Node.js 16 in Lambda on June 12, 2024. This follows Node.js 16 End-Of-Life (EOL) reached on September 11, 2023 [1].

I'm sure there would be a way to update this to work on Node 18+ with aws-sdk@2 packaged. But is there interest in upgrading to aws-sdk v3 ? I might have time to pull a PR together @HoraceShmorace - let me know if it would be helpful.

Wafv2 only works with the stack deployed in us-east-1 only so trying to use the -- region won't work unless we move back to WAF v1 or WAF Regional.

original URL: distribution/uploads/test.jpeg?w=200
Error while getting source image object "/uploadstest.jpeg": NoSuchKey: The specified key does not exist.

If the image is in the subfolder i get the following error how to fix it.

Hi,

I'm curios why did you decide to save processed/optimized images to another s3 instead of keeping it at CloudFront cache?
What if I want to invalidate cache of the image, because content of some specific image changed without changing name/path?
Or if I deployed new version of the my AcmeImageFlex with different optimization rules and want to invalidate all webp images in the project.

So what would be benefit of using separate s3 to store processed images? At CF level I can create invalidation at least by file path.

On separate note, great solution, I've learned that much from it and in the process of integrating in our company's production. :)

An error occurred (IllegalLocationConstraintException) when calling the CreateBucket operation: The unspecified location constraint is incompatible for the region specific endpoint this request was sent to.

can you add an AVIF handler to serve which ever image (AVIF, webp, etc..) is smaller in size?

Hie the solution is working great but rather I noted a huge growth in my page size after inspecting thoroughly I found out that if I upload a jpeg with 1200x800 size 88kb then try to resize it to ?w=500 the size actually grows from 88kb to 265kb when it is supposed to have gone down. I tried to change the sharp quality to less than 50 but did not change a thing. thank you bro please look into it.