Skip to content

update repo-level README with infra section #92

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
eglucas merged 1 commit into from
Jul 31, 2026
Merged

update repo-level README with infra section #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 18 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,24 @@ uv run python -m asf_mission_data.run example --stage all
## Infrastructure

Infrastructure is managed with [AWS CDK](https://aws.amazon.com/cdk/) (Python).
See [infrastructure/README.md](infrastructure/README.md) for full documentation.

**How this works, in three steps:**

1. **Build**: our code (all pipelines) gets packaged into a single Docker
container image and pushed to ECR (a private store for container images).

2. **Run**: to run a specific pipeline, someone manually triggers a task on
ECS Fargate (AWS's "run a container without managing a server" service),
telling it which pipeline to run from that shared image.

3. **Land**: the pipeline writes its output data to an S3 bucket where it's picked up by downstream tools for analysis.

> Note: there's no automatic scheduling yet (as of 31 July 2026), every run is triggered
> manually at the moment.

See [infrastructure/README.md](infrastructure/README.md) for full CDK
documentation, or [docs/running-pipelines.md](docs/running-pipelines.md)
for how to actually trigger a run.

---

Expand Down
Loading