CloudWatch Log Group Standard Class, Use Infrequent Access
The Infrequent Access class prices ingestion lower in exchange for a reduced query feature set, which is the right trade for logs that are kept rather than queried.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Switch log group to Infrequent Access. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Log Groups on AWS
- The fix, by hand
- Note: log class cannot be changed on existing log groups.
- Create a new log group with Infrequent Access class.
- Update the log source to write to the new log group.
- Infrequent Access supports CloudWatch Logs Insights but not real-time subscriptions.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1518- Full reference
CloudWatch Log Group Standard Class -- Use Infrequent Access
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.