Description

Add support for CloudFront Standard Logging using CloudWatch Log Delivery resources. This replaces the legacy logging_config and allows logging to S3, CloudWatch Logs, or Firehose as destinations.

Standard logging is automatically enabled when std_logging_destination or std_logging_destination_arn is provided (no separate enable flag needed).

New variables:

• std_logging_region - Region for logging resources (default: us-east-1)
• std_logging_source_name - Optional custom name for delivery source
• std_logging_destination_arn - Use existing destination (skip creation)
• std_logging_destination - Destination configuration (name, output_format, destination_arn)
• std_logging_delivery - Delivery configuration (field_delimiter, record_fields, s3_delivery_configuration)

New outputs:

• cloudfront_std_logging_source_arn
• cloudfront_std_logging_source_name
• cloudfront_std_logging_destination_arn
• cloudfront_std_logging_delivery_id
• cloudfront_std_logging_delivery_arn

Motivation and Context

AWS announced CloudFront Standard Logging in November 2024, providing significant improvements over legacy logging:

• Support for multiple destinations: S3, CloudWatch Logs, Firehose
• Multiple output formats: JSON, Parquet, Plain, W3C, Raw
• Hive-compatible S3 paths for better integration with analytics tools
• Customizable record fields
• Ability to send logs to opt-in AWS regions

Related:

• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logging.html
• [Enhancement]: CloudFront V2 Logging to S3 hashicorp/terraform-provider-aws#40925

Breaking Changes

No breaking changes. This is an additive feature. Existing logging_config (legacy logging) continues to work unchanged.

How Has This Been Tested?

• I have updated at least one of theexamples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the providedexamples/* projects
• I have executedpre-commit run -a on my pull request