Light, fluffy, and always free - The AWS Local Emulator alternative
docs: fix initialization hooks Docker image names and AWS CLI instructions (#169)
冰水泡枸杞93f122e8f873
diff --git a/docs/configuration/initialization-hooks.md b/docs/configuration/initialization-hooks.mdindex eebe1a820d..31130aebd7 100644--- a/docs/configuration/initialization-hooks.md+++ b/docs/configuration/initialization-hooks.md@@ -23,13 +23,36 @@ Hooks run:- With the same environment variables as FlociHooks can call Floci service endpoints directly from inside the container (e.g. `http://localhost:4566`).-The published Docker image does not include the AWS CLI. If your hooks require it, extend the image:++The published Docker images are available on Docker Hub:++- `hectorvent/floci:latest` — native image (minimal, no apk)+- `hectorvent/floci:latest-jvm` — JVM image (Alpine-based, has apk)+- `hectorvent/floci:latest-aws` — JVM image with AWS CLI pre-installed++If your hooks require the AWS CLI, use one of these options:++**Option 1: Use the pre-built AWS CLI image**++```dockerfile+FROM hectorvent/floci:latest-aws+# AWS CLI is already installed+```++**Option 2: Extend the JVM image (Alpine-based)**```dockerfile-FROM ghcr.io/hectorvent/floci:latest+FROM hectorvent/floci:latest-jvmRUN apk add --no-cache aws-cli```+**Option 3: Extend the JVM image with additional tools**++```dockerfile+FROM hectorvent/floci:latest-jvm+RUN apk add --no-cache aws-cli jq curl+```+If a hook depends on additional CLI tools, make sure those tools are available in the runtime image.### Execution Behavior