Jay
Yeah this is a little different. This is basically saying there is no AWS account so store the state for my app locally.
Might be worth creating a separate example for your case though. If you have a snippet that works let me know and I can document that.
Thanks for reporting. I'll take a look and fix the docs.
We should open a separate PayloadCMS related issue. This original issue should be fixed, image optimization using sharp should be automatically supported. I added an example with it https://github.com/sst/sst/tree/dev/examples/aws-nextjs-sharp
Here's how to do it in Pulumi: https://www.pulumi.com/blog/automatically-enforcing-aws-resource-tagging-policies/#automatically-applying-tags From https://discord.com/channels/983865673656705025/1177071497974648952/1243307231794172166
Does all of this happen consistently. > The issue disappears if I invalidate the cache of the cloudfront distribution. The issue returns after a period of time after the revalidation....
We'll take a look but also happy to look at a PR.
Just as a sanity check, if you deploy a new stage do you still get the error?
Thanks for taking a crack at this. It's been on our roadmap.