localstack/localstack-docs

[📑 Docs]: Expand page: CDK ECS Fargate Hot Reloading & Debugging

Open

#232 opened on Sep 25, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)MDX (37 forks)github user discovery
awsdocumentationgood first issuehacktoberfest

Repository metrics

Stars
 (13 stars)
PR merge metrics
 (Avg merge 8d 13h) (87 merged PRs in 30d)

Description

What docs changes are you proposing?

Source: https://github.com/localstack-samples/sample-cdk-ecs-fargate-hot-reloading-debugging

Problem

Repo is link-only in docs.

Proposal

  • Doc page with:
    • Introduction (how to hot reload and debug ECS containers locally)
    • Prerequisites (LocalStack Pro, Docker, AWS CDK, Node.js/Python)
    • Architecture diagram (Client → ALB → ECS Service → Task)
    • Steps (clone, deploy, edit code, reload container)
    • Testing the application (curl to service before and after hot reload, verify updated output)
    • Conclusion (benefits of local ECS debugging)

Acceptance Criteria

  • Doc has Intro, Architecture diagram, and explicit Testing the application section.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Clone the sample repository at https://github.com/localstack samples/sample cdk ecs fargate hot reloading debugging and inspect its structure. Create a documentation page following the proposed outline: Introduction, Prerequisites, Architecture diagram, Steps (clone, deploy, edit code, reload container), Testing the application (curl before and after hot reload), and Conclusion. Ensure to include an architecture diagram and a testing section with explicit curl commands.
Tech stack
awsdockernodejspython
Domain
backenddevops
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitDocker
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85