1. Versioned

  1. Versioned

  1. Versioned

What is Versioned config?

What is Versioned config?

The ability to track parameter, secret, and template changes over time for security, compliance, and reliability use cases.

The ability to track parameter, secret, and template changes over time for security, compliance, and reliability use cases.

Why Versioned config?

Why Versioned config?

  1. Compliance auditing and security aggregation need versioned configuration data.


  2. Roll-back configuration changes separate from code changes.


  3. Rapid outage triage requires a quick method to see recent config changes across all projects, teams, and environments.

  1. Compliance auditing and security aggregation need versioned configuration data.


  2. Roll-back configuration changes separate from code changes.


  3. Rapid outage triage requires a quick method to see recent config changes across all projects, teams, and environments.

Benefits

Benefits

  1. Tracking changes over time makes it easier to orchestrate updates in a consolidated fashion.


  2. Make a batch/checkpoint in a release vs. one at a time.

  1. Tracking changes over time makes it easier to orchestrate updates in a consolidated fashion.


  2. Make a batch/checkpoint in a release vs. one at a time.

Examples

Examples

  1. Provide proof of change management controls in place for a SOC2, ISO27001 or FedRAMP audit.


  2. Compare "current state" versus "desired state" for configuration drift detection.

  1. Provide proof of change management controls in place for a SOC2, ISO27001 or FedRAMP audit.


  2. Compare "current state" versus "desired state" for configuration drift detection.