CloudWatch Logs Class Configuration as a parameter for lambda function logs

[uditsidana]

Sometimes the cost of vended lambda logs can be huge, we want a way in which customers could choose the log class for their vended logs.

We would like to have a way so that customers have the option to reduce the vended logs cost which they account for.

I would like to see that the logs for lambda can be chosen by the customer instead of it always being defaulted to standard

Additional context

• The Infrequent Access class offers 50% lower ingestion costs and is suitable for debug logs, verbose application logs, and logs used primarily for forensic analysis
• This feature would help optimize costs for development environments, non-production workloads, and high-volume applications with infrequent log access patterns
• AWS already supports log class selection when manually creating log groups via the CreateLogGroup API
• Current workaround requires pre-creating log groups with desired settings before deploying Lambda functions

[CrypticCabub]

Thanks for creating this feature request!

We'll add this to backog for consideration and prioritization.

The proposal sounds simple enough, but I would be curious as to if you know whether enabling infrequent access has any implications on the performance of Log Insights Queries and Log Subscription Filters.

[uditsidana]

Hi @CrypticCabub thanks.
Log Insights Queries (Most commands) are supported and Log Subscription Filters are not supported for Infrequent Access class logs. The diff. table is here https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch_Logs_Log_Classes.html#Log_Class_Features