- Newest
- Most votes
- Most comments
Hi,
Note: I haven't tried adding the Layers based off of the link you provided (so apologize in advance if you wanted help with this specific method). However, I was able to successfully follow the directions in the following link:
https://aws.amazon.com/blogs/compute/working-with-aws-lambda-and-lambda-layers-in-aws-sam/
which allowed me to create a lambda layer and invoke it locally from my desktop.
Hope this helps,
-randy
Hi Randy,
Thanks for trying this. Both articles seem to use the same method of adding the Layer Version ARN to the template.ymal.
The URL it is trying to connect to doesn't look right: "https://lambda.eu-west-1a.amazonaws.com/2018-10-31/layers/arn%3Aaws%3Alambda%3Aeu-west-1%3A326436164324%3Alayer%3AGlobal/versions/7". Does your output show the Layer endpoint URL when running the local invoke command? If not would you be able to change your Layer ARN to something random to attempt to recreate the error so I have another URL to check mine against?
Kind regards,
Darren
I've found the issue. My ~/.aws/config file had the region set to "eu-west-1a" when it should have been "eu-west-1".
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 months ago