Skip to content

feat: Add LogGroupClass support by upgrading AWS SDK to v1.48.4 #369

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: mainline
Choose a base branch
from

Conversation

fonsecas72
Copy link

Issue #, if available:
N/A

Description of changes:
This PR adds support for the LogGroupClass feature, which allows users to specify the storage class (STANDARD or INFREQUENT_ACCESS) for their CloudWatch log groups, enabling cost optimization through the INFREQUENT_ACCESS tier.

Key changes:

  • Upgrade AWS SDK for Go to v1.48.4 which provides the LogGroupClass API
  • Add log_group_class configuration option to the plugin
  • Implement validation to ensure only valid storage classes (STANDARD, INFREQUENT_ACCESS) are accepted
  • Add unit tests for LogGroupClass functionality and validation
  • Update documentation with clear instructions for using the LogGroupClass feature

The feature is opt-in and only applies when creating new log groups with auto_create_group enabled.

The LogGroupClass feature can be used by setting the log_group_class parameter in the Fluent Bit configuration:

[OUTPUT]
    Name cloudwatch
    Match *
    region us-west-2
    log_group_name my-logs
    log_group_class INFREQUENT_ACCESS

- Update AWS SDK to v1.48.4 for LogGroupClass support
- Add LogGroupClass configuration option with STANDARD and INFREQUENT_ACCESS support
- Add validation and tests for LogGroupClass feature
- Add clear documentation for the LogGroupClass option
@fonsecas72 fonsecas72 requested a review from a team as a code owner February 11, 2025 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant