Policy Violations

Overview

Policy violations occur when your cloud resources deviate from predefined OneLens cost-saving policies. These breaches are automatically detected based on daily checks across your environment.

The Policy Violations page provides a centralized view of all such breaches, showing the violated policy, affected services, involved resources, and the potential savings associated with each violation.

Exploring the Violation Dashboard

To begin with:

• Log in to the OneLens UI using your credentials.

• From the left sidebar, go to the Policy Violation section.

Here is how the main page looks:

Number References

1. View Option
2. Filters
3. Potential Savings

4. Achieved Savings

5. Violations Detected

6. Unique Resources

7. Search Bar

8. Policy Table

View Option

You can start with pre-saved views or customize your own using filters.

• Recent Tickets: Shows tickets created in the last 7 days.

• Quick Wins: Filters for low-risk, easy-effort opportunities.

• Waste: Focuses on unused resources.

• Graviton: Surfaces opportunities to switch to Graviton instances.

• Savings Achieved: Status marked as Acted & Closed.

Tip

To learn how to save a customized view, click here.

Filter

Refine your view using filters:

• Account ID: Focus on a specific AWS account.

• Region: Limit results to a particular AWS region.

• Service: Select an individual AWS service.

• Cost Center: Filter by your organizational cost centers.

• Created Date: Choose a time window for ticket creation.

• Change Type:

  • Application Changes: Updates to app components.

  • Config Changes: Infrastructure-level adjustments.

  • Decommissioning: Terminating unused resources.

  • Scheduling: Time-based cost-saving actions.

• Cost Saving Category: Filter by the nature of the savings opportunity.

• Risk:

  • Low: Low-risk, generally safe changes.

  • High: Higher risk may need review.

• Effort:

  • Easy: Quick wins with minimal effort.

  • Medium: Requires moderate effort or coordination.

  • Hard: Higher-effort tasks with broader impact.

Key Metrics

• Potential Savings – Combined estimated savings across all detected violations.

• Achieved Savings – Total savings already realized per month from resolved tickets.

• Violations Detected – Number of unique policies currently violated.

• Unique Resources – Total distinct resources involved in these violations.

Violated Policies Table

Each violated policy is displayed as a row in the table, capturing key impact metrics:

• Policy Name – The name of the cost-saving policy that has been violated.

• Service – The cloud service associated with the policy (e.g., EC2, S3).

• Potential Savings – Estimated savings if the violation is addressed.

• Achieved Savings – Actual savings realized if actions have already been taken.

• Resources Affected – Number of unique resources that have triggered the violation.

Click on any Policy Name to open its detailed violation view.

Next Step

To explore the tickets created under a specific violated policy, see Viewing Specific Policy Violations