Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Commit

Permalink
updating tutorial material
Browse files Browse the repository at this point in the history
  • Loading branch information
taylor-curran committed Jul 31, 2023
1 parent 0eb5db3 commit 17b2837
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions docs/ecs_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,9 @@ ECS (Elastic Container Service) tasks are a good option for executing Prefect 2

## ECS Flow Run Execution

To set up Prefect flow execution in your cloud infrastructure, you need to understand two key Prefect concepts:

- a [worker](https://docs.prefect.io/latest/concepts/work-pools/#worker-overview) to poll Prefect's API (specifically that worker's [work queue](https://docs.prefect.io/latest/concepts/work-pools/#work-queues))
- and the ephemeral [infrastructure](https://docs.prefect.io/2.10.11/concepts/infrastructure/) that this worker will spin up for each scheduled [flow run](https://docs.prefect.io/2.10.11/concepts/flows/#flow-runs).
To set up Prefect flow execution in your cloud infrastructure, you need to understand two key Prefect concepts a [worker](https://docs.prefect.io/2.11.1/concepts/work-pools/#worker-overview) and [work pool](https://docs.prefect.io/2.11.1/concepts/work-pools/#work-pool-overview). To learn more about these concepts please see our [deployment tutorial](https://docs.prefect.io/2.11.1/tutorial/deployments/).

For details on how workers and work pools are implemented in ECS, see the diagram below:
#### Architecture Diagram
```mermaid
graph TB
Expand Down

0 comments on commit 17b2837

Please sign in to comment.