Campaigns

Detailed description of Campaigns

Introduction

Making changes to cloud configuration can be daunting: from remediating a long list of CSPM vulnerability findings to migrations or upgrades, the process of changing configuration for existing infrastructure can be challenging.

• Identifying the impacted resources

• Tracking progress and measuring success

• Coordinating with developers to make the change

• Writing the actual infrastructure as code (IaC)

Campaigns empower your teams to manage infrastructure-as-code (IaC) changes across many resources, or changes that require collaboration across multiple teams. Examples include launching a campaign to migrate all teams from terraform module version v1.0 to v1.2, or starting a campaign to remediate all of your S3-related vulnerabilities as flagged by a CSPM.

Resourcely Campaigns simplify cloud configuration changes by:

• Clearly outlining changes and necessary actions.

• Enabling developers to understand and implement modifications easily.

• Helping managers track progress across the organization efficiently.

How do Campaigns work?

Define

• The campaign manager, often a service owner, defines a set of high-level goals for the required Infrastructure-as-Code (IaC) changes.

• These high-level goals are translated into Resourcely-specific Guardrails, providing concrete and actionable guidelines.

Identify

• Violations across the organization are quickly identified and can be inspected for further analysis.

Fix

• Developers view the required changes in the Remediation section of the product and take appropriate action.

• The campaign manager can track progress in real time from their dedicated campaign management view.