Skip to content

guides/localstack: update init directory to /etc/localstack/init/ready.d #24816

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
craig-osterhout merged 2 commits into from
Jun 10, 2026
Merged

guides/localstack: update init directory to /etc/localstack/init/ready.d #24816

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5ccd5c7
guides/localstack: update init directory to /etc/localstack/init/ready.d
lacatoire Apr 17, 2026
0ee14ba
review: split executable script tip for clarity
lacatoire Apr 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion content/guides/localstack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,7 @@ Now that you have learnt how to connect a non-containerized Node.js application
- SERVICES=s3
- GATEWAY_LISTEN=0.0.0.0:4566
volumes:
- ./localstack:/docker-entrypoint-initaws.d"
- ./localstack:/etc/localstack/init/ready.d

volumes:
mongodbdata:
Expand Down Expand Up @@ -308,6 +308,15 @@ Now that you have learnt how to connect a non-containerized Node.js application

The command creates an S3 bucket named `mysamplebucket`.

> [!TIP]
>
> You can automate this step by placing a shell script (for example,
> `init.sh`) under the local `./localstack` directory. Make sure the
> script is executable (`chmod +x ./localstack/init.sh`). LocalStack
> runs files mounted in `/etc/localstack/init/ready.d` once it is ready.
> See [LocalStack init hooks](https://docs.localstack.cloud/references/init-hooks/)
> for more details.

@docker-agent docker-agent Jun 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[LOW] Weak link phrasing: "for more details" is generic

The sentence "See LocalStack init hooks for more details." ends with a generic call-to-action phrase. Per the Docker style guide, link text should be descriptive and specific, and trailing filler like "for more details" adds no value. Consider rewriting as: "For the full list of hook types and execution order, see the LocalStack init hooks reference."


Open [http://localhost:5173](http://localhost:5173) to access the complete to-do list application and start uploading images to the Amazon S3 bucket.

> [!TIP]
Expand Down