Nightly batch ETL architecture
Scheduled extract and load from source systems into a lake, then modelled into a warehouse.
AWSetls3redshiftschedule
What is in it
Every resource, and what it costs.
Projections from August 2026 list prices for always-on resources. Connect an account and these become the figures your provider actually bills.
| Node | Type | What it is | Projected |
|---|---|---|---|
| Nightly schedule | Messaging | 2M events | $2.00/mo |
| Extract jobs | Compute | 5M invocations · 512 MB · ~150 ms | from $8.00/mo |
| Raw zone | Storage | 1 TB standard | $24/mo |
| Transform ×2 | Compute | 2 × 0.25 vCPU · 0.5 GB | $18/mo |
| Redshift Serverless | Database | 8 RPU · ~25 h/month | from $75/mo |
| CloudWatch logs | External | 30 GB ingested | $18/mo |
Every figure is a projection from AWS list prices, before anything is built. 2 rows show from because those services bill by usage, so the total is a scenario at the stated volumes, not a quote.
Related
Similar templates.
Streaming ingest
Events land on a stream, are enriched in flight, and are written to both a lake and a search index.
API GatewayKinesis Data StreamLambdaS3 data lake+2
from $92/mo projected6 nodes
Analytics warehouse
Lake, warehouse and BI, with archival storage for anything older than the retention window.
S3 data lakeECS Fargate task ×2Redshift ServerlessCRM+1
from $118/mo projected5 nodes
Open Nightly batch ETL on the canvas.
It loads as an editable graph. Ask Archie to change it, then approve the plan and it is built in your own AWS account.