Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

deleted lambda layer version in aws console, not cannot run "amplify push"

See original GitHub issue

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug A clear and concise description of what the bug is.

I deleted lambda layer version in aws console, and now I cannot run “amplify push”, I am stuck trying to do a cloudformation rollback where it is stuck in the “UPDATE_ROLLBACK_FAILED” state, the cloudformation template references a lambda layer that no longer exists. How do I fix this issue? It seems I cannot create a lambda layer with a previously used version

Amplify CLI Version You can use amplify -v to check the amplify cli version on your system

To Reproduce Steps to reproduce the behavior or terminal output if applicable

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. Mac/Windows/Ubuntu]
Node Version. You can use node -v to check the node version on your system

Additional context Add any other context about the problem here.

Issue Analytics

State:
Created 3 years ago
Comments:20 (16 by maintainers)

Top GitHub Comments

7reactions

cellularatomatoncommented, Nov 14, 2020

@cc-bojan : I have been struggling with the same issue for a week now and just resolved it. Here is what I did: Search your source code for the field dependsOn[...]. I did this early on but it didn’t work because the amplify entries in .gitignore were obscuring a number of the files in my IDE (VS Code). Once I temporarily renamed .gitignore to not.gitignore I was able to see the dangling dependsOn[...] references. Upon removing the problematic layer from those dependsOn[...] sections, I was able to successfully run amplify remove function. Hope you are able to benefit from me pulling my hair out over the past week!

0reactions

github-actions[bot]commented, May 25, 2021

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

Top Results From Across the Web

Troubleshoot deployment issues in Lambda

Deployment errors prevent the new version from being used and can arise from issues with your deployment package, code, permissions, or tools. When...

Functions - Reuse code & assets using layers - Amplify Docs

To remove a Lambda layer, run the amplify function remove command and select Lambda layers . Next, you'll be prompted to select which...

AWS: Delete lambda layer still retains layer version history

Deletes successfully, ensured no other version of the layer exists. aws lambda list-layer-versions --layer-name my_layer > { "LayerVersions": [] }.

Bearcam Companion: My First Lambda - DEV Community ‍ ‍

AWS Lambda is a serverless, event-driven compute service that lets you run code for virtually any type of application or backend service ...

How to Reuse Node.js Packages with AWS Lambda Functions ...

No. At the time of writing, we can't test Lambda Layers locally using AWS Amplify. But you're going deploy your project to AWS...