Skip to content

Commit 8826999

Browse files
committed
add ARNs for Lambda layers of final 1.1.0 release
1 parent 43c9b27 commit 8826999

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

README.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ While GeoLambda was initially intended for AWS Lambda they are also useful as ba
1313
| geolambda | GDAL |
1414
| -------- | ---- |
1515
| 1.0.0 | 2.3.1 |
16-
| 1.1.0 | 2.4.0 |
16+
| 1.1.0 | 2.4.1 |
1717

1818
To get the version numbers of all installed packages see the [CHANGELOG](CHANGELOG.md) or the Dockerfile for the specific version.
1919

@@ -39,6 +39,14 @@ The GeoLambda image does not have an entrypoint defined, so a command must be pr
3939

4040
If you just wish to use the publicly available Lambda layer you will need the ARN for the layer in same region as your Lambda function. Currently, GeoLambda layers are available in `us-east-1`, `us-west-2`, and `eu-central-1`. If you want to use it in another region please file an issue or you can also create your own layer using this repository (see instructions below on 'Create a new version').
4141

42+
#### v1.1.0
43+
44+
| Region | ARN |
45+
| ------ | --- |
46+
| us-east-1 | arn:aws:lambda:us-east-1:552188055668:layer:geolambda:1 |
47+
| us-west-2 | arn:aws:lambda:us-west-2:552188055668:layer:geolambda:1 |
48+
| eu-central-1 | arn:aws:lambda:eu-central-1:552188055668:layer:geolambda:1 |
49+
4250
#### v1.1.0rc3
4351

4452
| Region | ARN |

0 commit comments

Comments
 (0)