Feedback request: external NEXUS-Q key provider integration for OpenTofu state and plan encryption #4801
Replies: 2 comments
|
Update: an experimental pre-release is now available to make evaluation easier. Download: https://github.com/lecodev-26/nexusq-keyprovider/releases/tag/v0.1.0-rc.1 The release includes direct binaries for Linux AMD64/ARM64, macOS ARM64, and Windows AMD64, plus the complete release bundle, SHA-256 checksums, SPDX 2.3 SBOMs, SLSA/Sigstore provenance and SBOM attestation bundles, build metadata, and the separate GitHub-runner rebuild report. The exact tagged source commit is 95aef9ee28891d077ab76995397744fe6d70b269. CI passed (16 jobs), including Go tests/vet/fuzzing, OpenTofu E2E on the documented Linux matrix, native macOS/Windows runtime E2E, real NEXUS-Q E2E, S3Mock E2E, and the separate-runner attestation/rebuild comparison. Important boundaries: this is an experimental release candidate, not a stable or production-certified release; no independent security audit has been performed; the separate-runner comparison is still within GitHub Actions and is not third-party reproduction; and real AWS S3/IAM validation remains pending. The release notes and verification instructions spell out the exact coverage and limitations. Feedback on the protocol integration, compatibility edge cases, context-binding model, saved-plan handling, rotation, and recovery is very welcome. |
|
External operator testing is now open — looking for 2–3 evaluators\n\nI have added a practical External operator testing guide to help people evaluate the experimental NEXUS-Q External Key Provider.\n\nThe guide includes two paths: (1) a local integration test using the repository test-only NEXUS-Q API fixture, with no real NEXUS-Q credentials; and (2) an optional real NEXUS-Q smoke test using a dedicated disposable vault, test token, local-only OpenTofu resources, and non-production data.\n\nI am looking for 2–3 operators to independently try installation/configuration and report on state encryption, saved-plan handling, recovery, key rotation, compatibility, and documentation clarity. Please include only the exact OpenTofu version, OS/architecture, tested commit/release, steps, and sanitized results. The guide includes a feedback checklist.\n\nSafety: this is an experimental pre-release, not for production infrastructure or valuable state. Do not share credentials, vault files, state files, saved plans, plaintext keys, or raw provider metadata. No independent security audit has been performed. Real AWS S3/IAM validation and outside-CI independent build reproduction remain pending.\n\nIf interested, please reply with the test path you can run and your OS/architecture. Thanks for helping pressure-test this before a stable release. |
Uh oh!
There was an error while loading. Please reload this page.
Hi OpenTofu community,
I have built an experimental external key-provider companion that connects OpenTofu state and saved-plan encryption to NEXUS-Q. It runs as a separate executable and implements External Key Provider protocol v1; it does not modify or fork OpenTofu.
The provider generates 256-bit DEKs for OpenTofu's native AES-GCM encryption and uses NEXUS-Q's envelope API to wrap and recover them. Its v2 metadata includes an operator-configured context assertion inside the NEXUS-Q-encrypted payload. Legacy v1 metadata is rejected by default, with an explicit migration opt-in.
Validation currently documented:
Latest successful CI evidence for the implementation: https://github.com/lecodev-26/nexusq-keyprovider/actions/runs/41440512209
Repository and technical documentation: https://github.com/lecodev-26/nexusq-keyprovider
External-review notes and the explicit validation boundaries: https://github.com/lecodev-26/nexusq-keyprovider/blob/main/docs/EXTERNAL-REVIEW.md
I would appreciate feedback on:
A few important boundaries: S3Mock is not AWS S3 validation; AWS IAM, bucket policies, versioning, Object Lock, SSE-KMS, and S3 lock contention have not been validated. GitHub's second-runner rebuild is not an independent-operator reproduction. The project has not received an independent security audit and remains an experimental prototype.
I am not requesting an OpenTofu core change, and this post should not be read as an endorsement request or a claim of upstream support. I would value technical feedback before considering any broader release.
All reactions