Unable to include from CLI about git-lambda-layer HOT 8 CLOSED

I suspect this must be an issue with your user permissions – the layer itself allows lambda:GetLayerVersion to be called from any Principal.

Try adding the lambda:GetLayerVersion permissions to the user explicitly and see if that works:

https://docs.aws.amazon.com/lambda/latest/dg/lambda-api-permissions-ref.html#permissions-resources-layers

from git-lambda-layer.

Experiencing the same when deploying from Serverless

User: arn:aws:iam::886182114158:user/silviulucian-alt is not authorized to perform: lambda:GetLayerVersion on resource: arn:aws:lambda:us-east-1:553035198032:layer:git:3 (Service: AWSLambdaInternal; Status Code: 403; Error Code: AccessDeniedException; Request ID: ebbb27dc-0d1b-11e9-b997-7b10317a7e42).

As with romaninsh's account above, this user is a

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "*",
      "Resource": "*"
    }
  ]
}

from git-lambda-layer.

Well if it works from the AWS console, then I think everything must be fine on the layer end – so I still suspect it's some sort of permissions issue on your end.

Do you have the same problem with any other layers? eg, https://github.com/RafalWilinski/serverless-puppeteer-layers

from git-lambda-layer.

Aaaa, right, I feel silly I didn't check to see if it worked with another layer first. Same error. I'll keep digging and get back when I figured it out.

from git-lambda-layer.

Alrighty, figured it out: I copied and pasted the layer arn blindly and kept us-east-1 in there as the region. My lambda is deployed in eu-west-1 however. Everything started chooching just fine once I changed the region in the layer arn to match the one I was using.

from git-lambda-layer.

@silviulucian I am also deployed in EU region. Thanks for the possible fix idea!

from git-lambda-layer.

This is documented under the ARNs: https://github.com/lambci/git-lambda-layer#version-arns

I might add it to the getting started too

from git-lambda-layer.

Yes was confused because the same ARN worked the same.

from git-lambda-layer.