Skip to content

Commit 8117869

Browse files
committed
Add README for Other Containers
1 parent 742abf3 commit 8117869

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,18 @@ aws configure
7373
S3_BUCKET_NAME=my-bucket ./package/deploy
7474
```
7575

76+
#### Other Containers
77+
78+
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.
79+
80+
```dockerfile
81+
FROM ghcr.io/customink/crypteia-extension-amzn:latest AS crypteia
82+
FROM ubuntu
83+
COPY --from=crypteia /opt /opt
84+
ENV LD_PRELOAD=/opt/lib/libcrypteia.so
85+
ENTRYPOINT /opt/extensions/crypteia
86+
```
87+
7688
## Usage
7789

7890
First, you will need your secret environment variables setup in [AWS Systems Manager Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html). These can be whatever [hierarchy](https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-hierarchies.html) you choose. Parameters can be any string type. However, we recommend using `SecureString` to ensure your secrets are encrypted within AWS. For example, let's assume the following paramter paths and values exists.

0 commit comments

Comments
 (0)