Francesc Navarro

I added the hosting like they explain here https://docs.amplify.aws/cli/hosting so now I have a backend environment(S3AndCloudFront), but still don't see how is connected to my repo. I need to go...

Thanks, I'm just giving up this is what I get:

So after an infinite loading... I tried from frontend environments, and works but now I have 2 hosting. Is it any guide to follow somewhere?

+1 `postDeploy` step, in our case we need to invalidate other caches after the deploy. I've seen workarounds configuring alerts and checking the email that arrives there... Maybe too complex...

Next.js 13, Does it work on other platforms a part from Vercel? Maybe Netlify? Having it in running as a server on an EC2 is not the best scenario.

@cmaerz as far as I know those technologies are on not on the edge, but I could be wrong. I supose you can use cloudfront with a proper cache policy...

With Amplify and nx-cloud the build is quiet fast, I think now is faster that it was before with next.js 12 and serverless, but still slow compare with Vercel.

Amplify now supports next.js 13 and a custom serverless setup doesn't. I'm thinking to move to Amplify again but I really need the cloudfront headers available in my next.js app...

is it possible that AWS has fixed this issue for all apps? even for old ones? I've been testing it and now I don't face this problem but few months...

I don't think they added cloudfront headers in the new releases but I'm gonna give it a try today and see.