ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pulumi
Wrap an S3 bucket and CloudFront distribution into a Pulumi component resource so you can deploy static blogs repeatedly without copying infrastructure code.
Use a single ESC environment per stage, keep secrets out of Pulumi state, and validate ESC schema and access logs to ensure deterministic, auditable deployments.
Learn how Pulumi’s Policy‑as‑Code lets teams enforce infrastructure rules with OPA, see a step‑by‑step example, weigh trade‑offs, and decide when to adopt it.
Stop copying VPC and subnet boilerplate across stacks. Build, publish, and consume a Pulumi ComponentResource in TypeScript.
Learn how to architect a minimal Pulumi deployment that uses stack outputs for shared data and config secrets for sensitive values, ensuring clear data boundaries and secure remote state management.
Compare Pulumi Service managed state and self‑hosted S3‑based state backends for regulated multi‑team IaC, then validate each with concrete CLI steps.
Pulumi ComponentResources let you bundle cloud resources into reusable, version‑controlled modules. Learn how to define, export, and publish a component, link it to downstream resources, and avoid common pitfalls.
Learn how to architect Pulumi for security, focusing on encrypted state backends, KMS integration, and operational guardrails to prevent secret leakage in CI/CD pipelines.
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.