Stack Automation for creating backend state resources (e.g. S3, DynamoDB)
When we want to self-mange the terraform backend state resources, we will have to create the S3 and DynamoDB table on our own. It’s increase our manual overhead.
It is good if Spacelift can provide one click automation of provisioning these resources upon stack creation.
- Workaround
Log in to comment and vote
Comments2
Natalia Gazda
Jul 16
Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Natalia Gazda
Aug 6, 2025
Thanks for sharing this.
To make sure we fully understand the job you’re trying to get done:
Spacelift already provides zero‑config state management out of the box — every stack has managed state without needing to set up S3 or DynamoDB. If you’d like to self‑manage backends, you can still do that, but we try to remove that overhead by default.
The idea of “one‑click provisioning of backend state infra” sounds like you’re leaning toward a hybrid: wanting to own the resources, but not the setup friction. That’s interesting — but we’d want to validate if this solves a real pain, or just reproduces something Spacelift already handles.
We’d also want to understand the local‑run angle. Spacelift supports private worker pools, drift detection, and CLI access via
spacectl—so you can already run plans/applies locally against the same state. The key difference is whether you want Spacelift to still “own” the backend.Before we jump to solutions, could we dig into the underlying need?
What’s the main reason you’d prefer to provision your own S3/DynamoDB backend instead of relying on Spacelift’s built‑in state management?
If this worked perfectly, what would you no longer need to worry about?
When you say “local run,” is that mainly for speed, compliance, or debugging?