core(runner) - Add S3 remote state backend for Terraform and technique state#834
Merged
christophetd merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
Minosity-VR
changed the title
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Minosity-VR
force-pushed
the
simon.marechal/s3-remote-state
branch
from
575ac8e to
fd9d02b
Compare
christophetd
approved these changes
Apr 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Enhancement: Allow the runner to be instantiated with a remote state in an AWS S3 bucket.
Note
Remote state only supports AWS S3 for now
Motivation
Soon™️ we are going to open source a wrapper for stratus to run it as a service. It requires some modifications in the core:
Having a remote state allows to share the stratus state between teammates (or services), and even host the state bucket in a different account than the detonation one:
Example when detonating an attack in account
1550********, but storing the state in account0693********:bucket:
cloudtrail before attack:
