Skip to content

Commit c62566a

Browse files
Improve policy as code documentation formatting
- Restructure sentence for better flow and readability - Reformat benefits section as bulleted list for improved scannability - Maintain 'Pulumi Policies brings' as singular per product naming Co-authored-by: Cam Soper <CamSoper@users.noreply.github.com>
1 parent 446a847 commit c62566a

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/docs/insights/policy/_index.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,19 +25,19 @@ Pulumi Policies empowers you to set guardrails to enforce compliance across your
2525

2626
## What is policy as code?
2727

28-
Policy as code applies software engineering practices to infrastructure policies. Instead of manually configuring compliance rules through cloud provider consoles or maintaining policy documentation in wikis, you write policies in programming languages and manage them alongside your infrastructure code.
28+
Policy as code applies software engineering practices to infrastructure policies. You write policies in programming languages and manage them alongside your infrastructure code, instead of manually configuring compliance rules through cloud provider consoles or maintaining policy documentation in wikis.
2929

3030
This approach provides several key benefits:
3131

32-
**Cost control**: Define policies based on resource pricing to prevent expensive deployments before they happen. Set spending limits, identify unused resources, and enforce tagging for cost tracking and allocation across teams.
32+
- **Cost control**: Define policies based on resource pricing to prevent expensive deployments before they happen. Set spending limits, identify unused resources, and enforce tagging for cost tracking and allocation across teams.
3333

34-
**Compliance and security**: Enforce guardrails that prevent common misconfigurations like public S3 buckets, exposed databases, or overly permissive security groups. Apply consistent security standards across development, staging, and production environments.
34+
- **Compliance and security**: Enforce guardrails that prevent common misconfigurations like public S3 buckets, exposed databases, or overly permissive security groups. Apply consistent security standards across development, staging, and production environments.
3535

36-
**Early validation**: Catch policy violations during `pulumi preview` before resources are created, not after deployment. This prevents non-compliant infrastructure from reaching production and reduces the time and cost of remediation.
36+
- **Early validation**: Catch policy violations during `pulumi preview` before resources are created, not after deployment. This prevents non-compliant infrastructure from reaching production and reduces the time and cost of remediation.
3737

38-
**Best practices as code**: Encode organizational standards and cloud provider best practices as versioned, testable policies. Share policy packs across teams to ensure consistent infrastructure patterns throughout your organization.
38+
- **Best practices as code**: Encode organizational standards and cloud provider best practices as versioned, testable policies. Share policy packs across teams to ensure consistent infrastructure patterns throughout your organization.
3939

40-
**Integration with cloud-native tools**: Work alongside cloud provider features like AWS IAM Access Analyzer or AWS Organizations tag policies, combining Pulumi's policy enforcement with native cloud governance capabilities.
40+
- **Integration with cloud-native tools**: Work alongside cloud provider features like AWS IAM Access Analyzer or AWS Organizations tag policies, combining Pulumi's policy enforcement with native cloud governance capabilities.
4141

4242
Pulumi Policies brings these policy as code benefits to both Pulumi-managed infrastructure and resources discovered from other tools or created manually.
4343

0 commit comments

Comments
 (0)