You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.
I've tried to deploy this example as my first foray into appsync. I merely select the 'blog' option, and wait for deployment. After some time in creating status, it says rollback is in progress and then rollback is complete.
In the events log for 'AppSyncRDSLambda' it says "The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: f8f22b02-ecef-40f8-876f-705c569e6933)"
It then declares failure and rolls back.
The text was updated successfully, but these errors were encountered:
Apologies, that was my bad. The code was updated here correctly, but the launch buttons from the readme pull a duplicate version of the sample from an s3 bucket, and that was not. I just updated it, and have confirmed it builds to completion from there now.
Let me know if you have any issues!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've tried to deploy this example as my first foray into appsync. I merely select the 'blog' option, and wait for deployment. After some time in creating status, it says rollback is in progress and then rollback is complete.
In the events log for 'AppSyncRDSLambda' it says "The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: f8f22b02-ecef-40f8-876f-705c569e6933)"
It then declares failure and rolls back.
The text was updated successfully, but these errors were encountered: