2.1.0 geolambda shared layer update

[furick1]

In the readme the ARNs for the shared public lambda layer are the same for 2.0.0 and 2.1.0 which is arn:aws:lambda:us-east-1:552188055668:layer:geolambda:4 and arn:aws:lambda:us-east-1:552188055668:layer:geolambda-python:3 . Did the shared image get updated from 2.0.0 to 2.1.0 or am I misunderstanding? Perhaps I should use :5 and :6?

[matthewhanson]

@furick1 The new layers will be available through a different AWS account, but they haven't been added yet. Gotta figure out an authentication/permissions issue. I'll be updating the README and making a Release when they have been deployed.

[furick1]

@matthewhanson any luck? I compiled my own latest python lambda layer and published to AWS but got errors on use. I can share more detail but would like to utilize the public shared layers as in past. I'm happy to offer assistance on the auth/perms issues on AWS but realize that is easier said then done.

[four43]

@matthewhanson any update on this? Just curious if I should continue trying to build my own version here...

[matthewhanson]

Hi @four43 , apologies, every time I get back to this I keep on hitting some issue then just run out of time.

Another alternative is to take a look at https://github.com/lambgeo/docker-lambda that @vincentsarago created which has more version and region options and he also got working on Amazon Linux 2.

[four43]

Hey no worries. You don't owe us anything, it's free :D

I was just curious if I could help in some way. I'll check out that alternative. Thanks a lot!

[giovanniborella]

Any news on this issue?

[tov-bk-pavuk]

It would be great to update the documentation to say that version 2.1.0 is not available because it's confusing and kills a lot of time investigating the issue.

[vincentsarago]

@tov-bk-pavuk I'll be happy to review any PR on the documentation 🙏