uclaeamsavino

Is there a long term solution for this? Has anyone tried the recommendation in the serverless message? I wasn't sure what to put for `````` and ``````

We fixed the lambda states issue by upgrading Serverless Next from 1.18 to 3.6.0 in the serverless.yml file.

> ```js > const Amplify = require('aws-amplify').default; > > Amplify.configure({ > API: { > aws_appsync_graphqlEndpoint: 'https://xxxxxxxxxxxxxxxxxxxxxxxxxx.appsync-api.us-east-1.amazonaws.com/graphql', > aws_appsync_region: 'us-east-1', > aws_appsync_authenticationType: 'NONE', > graphql_headers: async () => ({ > 'Authorization':...

> https://aws.amazon.com/blogs/mobile/amplify-next-js-13/ I just came here to post that. We've been playing around with it and it looks promising. > Today, [AWS Amplify Hosting](https://aws.amazon.com/amplify/hosting/) announces Next.js 12 and 13 support....

No, I think they just didn't implement it, and it seems like they're done with this project. Here's the spec on the .well_known file: https://openid.net/specs/openid-connect-discovery-1_0.html Here's an example from AWS...

Man this would be a nice feature. No idea why the CRA maintainers are so opposed to it.

I found this thread because I'm finding AppSync expects incoming AWSJSON input to be double-stringified, and AWSJSON responses from appsync have to be parse twice. Weird.

Elon is saying those are the only three.

Looks good now!

Well now it seems to be broken again.