-
Notifications
You must be signed in to change notification settings - Fork 63
InvokeSync stage failing on fresh deployment #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
What is the output in CloudWatch Logs? Please check for sensitive information before posting here. |
I apologize, github notifications got the better of me. If this is helpful in any way, CloudWatch log for the failing function:
|
Please try updating your "SyncLambdaFunction" AWS Lambda function with the latest version of the code in s3://run.alestic.com/lambda/aws-lambda-git-backed-static-website.zip You can do this in that function's AWS Lambda console page with "Code entry type" of "Upload a file from AWS S3" and set "S3 link URL" to "https://s3.amazonaws.com/run.alestic.com/lambda/aws-lambda-git-backed-static-website.zip". Other attributes of the AWS Lambda function can remain the same. You can then push a change in your Git repository, or go to the AWS CodePipeline console and click [Release change] on your pipeline page to run the pipeline again. |
I followed your instructions but get the following error: 22:29:22 Would you be able to update your stack so we do not need to do manual changes to the stack since the function is managed by cloudformation? |
I think I have the CloudFormation stack and AWS Lambda deployment ZIP file in sync everywhere now. You can either start a new stack, referencing existing resources, or upload the SyncLambdaFunction as described above. |
It looks like syncing files to the bucket fails with the following error:
Can you please advice on how to go from here?
The text was updated successfully, but these errors were encountered: