diff --git a/README.md b/README.md
index 222e72e..0b7f54b 100644
--- a/README.md
+++ b/README.md
@@ -73,7 +73,7 @@ Secrets are fetched in batch via the `ENTRYPOINT`. This is done for you automati
 
 When building your own Lambda Containers, use both the `crypteia` binary and `libcrypteia.so` shared object files that match your platform. Target platform naming conventions include the following:
 
-- Amazon Linux 2: uses the `-amzn` suffix.
+- Amazon Linux: uses the `-amzn` suffix.
 - Debian, Ubuntu, etc.: uses the `-debian` suffix.
 
 > **Note**
@@ -84,8 +84,8 @@ When building your own Lambda Containers, use both the `crypteia` binary and `li
 There are two options for Lambda containers. The easiest is to use Docker's multi stage builds with our [Extension Containers]([https://github.com/orgs/rails-lambda/packages?ecosystem=container&tab=packages&ecosystem=container&q=extension](https://github.com/orgs/rails-lambda/packages?repo_name=crypteia&q=extension)) to copy the `/opt` directory matching your platform and Crypteia version number. example below. Remember to use `-debian` vs `-amzn` if you are using your own Linux containers. Or change the version number depending on your needs.
 
 ```dockerfile
-FROM ghcr.io/rails-lambda/crypteia-extension-amzn:1 AS crypteia
-FROM public.ecr.aws/lambda/nodejs:18
+FROM ghcr.io/rails-lambda/crypteia-extension-amzn:2 AS crypteia
+FROM public.ecr.aws/lambda/nodejs:24
 COPY --from=crypteia /opt /opt
 ENV LD_PRELOAD=/opt/lib/libcrypteia.so
 ```
@@ -136,7 +136,7 @@ S3_BUCKET_NAME=my-bucket ./package/deploy
 If you are using Crypteia on your own Docker containers without the Lambda Extension mechanics, you can simply set the `ENTRYPOINT` to the Crypteia binary which fetches your environment variables so the shared object preload can use them.
 
 ```dockerfile
-FROM ghcr.io/rails-lambda/crypteia-extension-amzn:1 AS crypteia
+FROM ghcr.io/rails-lambda/crypteia-extension-amzn:2 AS crypteia
 FROM ubuntu
 COPY --from=crypteia /opt /opt
 ENV LD_PRELOAD=/opt/lib/libcrypteia.so