buoyant marsh
I'm working on the SST adapter for Astro and running into issues getting the assets functionality working on Lambda functions. The issue is that the relative paths passed into the astro-assets-services endpoint aren't really useful, since the client directory that the paths are referencing are on S3. I would expect the best way to solve this problem would be to allow an override of the loadLocalImage method in assets/endpoints/node.ts to use something like an S3 CLI call to pull the file down to ephemeral storage and load it from there. This doesn't appear to be supported and I suspect it's a fairly large undertaking so I'll assume it's not a realistic solution.
The next best solution seems to be supported (using a remote path), but while the endpoint supports ingesting remote paths, the pages are rendered with relative paths. Is there a way to recompose the image paths at render time to include a full URL as the href in the request OR to perform a local resource to remote resource mapping in the asset service? Has anyone solved this for Lambda functions already?