Skip to main content

🛡️ Google GCE Commitment expired in the last 30 days🟢

Logic​

Description​

Open File

Description​

This policy identifies Google GCE Commitments that have expired within the last 30 days. It serves as a safeguard to confirm whether expirations were intentional and to alert teams of potential unplanned increases in cloud spending.

Rationale​

While proactively monitoring upcoming expirations is the recommended best practice, this policy provides a reactive safety net. By flagging recently expired commitments, FinOps and cloud management teams can validate whether the expiration was planned or accidental. This enables timely assessment of the financial impact of resources reverting to on-demand pricing and supports corrective action if required.

Audit​

This policy flags a Google GCE Commitment is INCOMPLIANT if its Status is EXPIRED and its End Timestamp falls within the last 30 days.

The Commitment is marked as INAPPLICABLE if its Status is not equal to EXPIRED.

Remediation​

Open File

Remediation​

Verify whether the commitment’s expiration was intentional. If it was not, take immediate corrective action to mitigate increased costs by purchasing a new commitment.

Using the Google Cloud Console​

  1. Acknowledge and Verify Intent

    Confirm with the resource owner or finance team whether the expiration of the identified commitment was deliberate.

  2. Assess Cost Impact

    Review the project and the resources previously covered by the commitment to understand the financial impact of running them at on-demand rates.

  3. Repurchase a Commitment (If Required)

  4. Implement Proactive Monitoring

    • Set alerts to notify teams of commitments approaching their expiration dates.
    • Regularly review the Committed Use Discounts page to monitor the status and expiration of all active commitments.

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 Cloudaware Framework → 💼 Waste Reduction25no data