Expand description
Amazon Redshift control-plane implementation for FakeCloud.
Redshift’s control plane is pure state CRUD: clusters, snapshots,
parameter/subnet/security groups, HSM objects, event subscriptions,
scheduled actions, usage limits, endpoint access, datashares, and so on.
Unlike RDS/ElastiCache there is no data plane to run (SQL access is a
separate service, redshift-data), so nothing here spawns containers —
every resource is modelled as real persisted state with real CRUD,
validation, pagination, and AWS-faithful error codes.
Structs§
- Redshift
Accounts - Redshift
Service - Amazon Redshift control-plane service. Holds per-account state and, in
persistent mode, a
SnapshotStorethat every mutating action flushes to. - Redshift
Snapshot - On-disk snapshot envelope for Redshift state. Versioned so format changes fail loudly on upgrade rather than silently mis-parsing.
- Redshift
State - All Redshift control-plane resources for a single AWS account.