> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Move CloudWatch Log Group to Infrequent Access Class

> Move CloudWatch log groups that nobody queries much to the Infrequent Access log class, which ingests for less.

The CloudWatch Logs Infrequent Access log class charges a lower price per GB ingested than the Standard class, in exchange for fewer features. nOps finds Standard log groups that ingest every day but are rarely queried with Logs Insights, and estimates the saving from ingesting the same data into an Infrequent Access log group.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Management and governance |
| **Service** | Amazon CloudWatch Logs |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Ingestion is usually the largest part of a CloudWatch Logs bill, and many log groups are kept only in case they are needed for an investigation.

## How nOps finds it

nOps reads your CloudWatch Logs billing for each log group. A group is flagged when it ingested Standard-class data on at least 7 of the last 14 days. Groups whose Logs Insights query cost in the last 30 days was more than 2% of their ingestion cost are left out, because they are queried often. The saving is the ingestion cost of the last 7 days, scaled to a month, times the difference between the public Standard and Infrequent Access prices per GB in the region, and must be at least \$20 a month.

## Before you start

Know which features the log group relies on, and who produces and reads its logs.

## How to implement

1. Check the log group does not need features Infrequent Access drops: metric filters, subscription filters, Live Tail, embedded metric format extraction, anomaly detection and data protection.
2. Create a new log group with the Infrequent Access class (`aws logs create-log-group --log-group-name NEW_NAME --log-group-class INFREQUENT_ACCESS`) and set its retention.
3. Point the producers (applications, Lambda functions, agents) at the new group.
4. Keep the old group until its data expires or is no longer needed, then delete it.

## Risks and considerations

* The log class is fixed when a log group is created, so this means a new log group and a change for every producer.
* Logs Insights queries still work on Infrequent Access, but alarms built on metric filters do not.
* To roll back, point producers back at a Standard log group.

## FAQs

> [accordion] Can I change the class of an existing log group?
>
> No. The class is set when the group is created, so you create a new group and move the producers.

## Related

* [Set CloudWatch Logs Retention](https://help.nops.io/inform/supported-recommendations/set-cloudwatch-logs-retention)
* [Enable CloudWatch Logs Intelligent Tiering](https://help.nops.io/inform/supported-recommendations/enable-cloudwatch-logs-intelligent-tiering)
* [Deliver VPC Flow Logs to S3 Instead of CloudWatch Logs](https://help.nops.io/inform/supported-recommendations/deliver-vpc-flow-logs-to-s3-instead-of-cloudwatch-logs)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.