ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Compare Pulumi Service managed state and self‑hosted S3‑based state backends for regulated multi‑team IaC, then validate each with concrete CLI steps.
Choosing where Pulumi stores state and encrypts secrets is a production security decision. Compare Pulumi Cloud, self-managed object storage with KMS, and passphrase options.
Compare Terraform state backends — local, S3, Azure Blob, GCS, Consul, Terraform Cloud — with a decision matrix and a ready‑to‑use S3 + DynamoDB configuration.
Goal Select a Pulumi state backend for a team that updates the same stack concurrently, prioritizing predictable locking behavior and access control. Assumes the current stable Pulumi CLI release. Constraint Pulumi Cloud provides server-side state locking, version history, and organization-level access control by default. Self-managed backends using cloud ob
Pulumi Cloud vs Self-Managed Object Storage for Data-Residency and Access-Control Constraints Our team must choose a Pulumi state backend that satisfies strict data-residency and access-control requirements while preserving operational visibility. Pulumi Cloud offers managed encryption, organization-level RBAC, and audit logs, but stores state in a third-par
pulumi
terraform
dynamodb