fixup! feat: Add a changelog for the v5

Signed-off-by: Vincent Boutour <vincent.boutour@datadoghq.com>

Author: ViBiOh

aws/logs_monitoring/CHANGELOG.md

@@ -4,48 +4,36 @@
 
 ### Overview
 
-Version 5.0.0 of the Datadog Lambda Forwarder introduces several breaking changes that remove deprecated features and improve log filtering behavior. This release simplifies the forwarder configuration and aligns with modern AWS integration patterns.
+Version 5.0.0 of the Datadog Lambda Forwarder introduces several breaking changes that remove deprecated features and improve log filtering behavior. This release introduce a new way to enrich your logs with tags that would reduce AWS Lambda related cost (S3, KMS and Lambda).
 
-### Breaking Changes
-
-#### 1. Removed TCP Transport Support
-
-**What Changed:**
-
-- Removed the `DD_USE_TCP` / `DdUseTcp` environment variable and parameter
-- Deleted the TCP client implementation
-- All logs now **must** be sent via HTTP/HTTPS
-
-**Migration Required:**
-
-- Remove any configuration setting `DD_USE_TCP=true` or `DdUseTcp=true`
-- The forwarder will now exclusively use HTTP transport
-- If you were using TCP with custom ports (10516), these configurations will be ignored
-- The default HTTP endpoint is now `http-intake.logs.<DD_SITE>` on port 443
-
----
+### New Features
 
-#### 2. Removed Deprecated PrivateLink Environment Variable
+#### 1. Backend Storage Tag Enrichment
 
-**What Changed:**
+**Added:**
 
-- Removed the `DD_USE_PRIVATE_LINK` / `DdUsePrivateLink` environment variable and parameter
+- New `DD_ENRICH_S3_TAGS` / `DdEnrichS3Tags` parameter (default: `true`)
+- New `DD_ENRICH_CLOUDWATCH_TAGS` / `DdEnrichCloudwatchTags` parameter (default: `true`)
+- These instruct the Datadog backend to automatically enrich logs with resource tags **after ingestion**
+- New cloudwatch tags can appear on logs, check your Datadog log index configuration to ensure smooth transition.
 
-**Migration Required:**
+**Benefits:**
 
-- Remove any configuration setting `DD_USE_PRIVATE_LINK=true`
-- **AWS PrivateLink is still fully supported**, but you must follow [PrivateLink documentation](https://docs.datadoghq.com/agent/guide/private-link/):
-    1. Set up VPC endpoints for `api`, `http-logs.intake`, and `trace.agent` as documented
-    2. Configure the forwarder with `DdUseVPC=true`
-    3. Set `VPCSecurityGroupIds` and `VPCSubnetIds`
+- **Reduces forwarder cost** and execution time
+- Provides the same tag enrichment as `DdFetchS3Tags` and `DdFetchLogGroupTags`
+- Requires [Resource Collection](https://docs.datadoghq.com/integrations/amazon-web-services/#resource-collection) enabled in your AWS integration
 
-**Why This Changed:**
+**Deprecation Notice:**
 
-- The variable was deprecated since 4 years, we use the major release opportunity to cleanup with a breaking change.
+- `DdFetchS3Tags` is now marked as **DEPRECATED** in favor of `DdEnrichS3Tags`
+- `DdFetchLogGroupTags` is now marked as **DEPRECATED** in favor of `DdEnrichCloudwatchTags`
+- `DD_FETCH_S3_TAGS` now defaults to `false` (previously `true`)
 
 ---
 
-#### 3. Changed Regex Matching Behavior for Log Filtering
+### Breaking Changes
+
+#### 1. Changed Regex Matching Behavior for Log Filtering
 
 **What Changed:**
 
@@ -63,28 +51,40 @@ Version 5.0.0 of the Datadog Lambda Forwarder introduces several breaking change
 
 ---
 
-### New Features
+#### 2. Removed TCP Transport Support
 
-#### 4. Backend Storage Tag Enrichment
+**What Changed:**
 
-**Added:**
+- Removed the `DD_USE_TCP` / `DdUseTcp` environment variable and parameter
+- Deleted the TCP client implementation
+- All logs now **must** be sent via HTTP/HTTPS
 
-- New `DD_ENRICH_S3_TAGS` / `DdEnrichS3Tags` parameter (default: `true`)
-- New `DD_ENRICH_CLOUDWATCH_TAGS` / `DdEnrichCloudwatchTags` parameter (default: `true`)
-- These instruct the Datadog backend to automatically enrich logs with resource tags **after ingestion**
-- New cloudwatch tags can appear on logs, check your Datadog log index configuration to ensure smooth transition.
+**Migration Required:**
 
-**Benefits:**
+- Remove any configuration setting `DD_USE_TCP=true` or `DdUseTcp=true`
+- The forwarder will now exclusively use HTTP transport
+- If you were using TCP with custom ports (10516), these configurations will be ignored
+- The default HTTP endpoint is now `http-intake.logs.<DD_SITE>` on port 443
 
-- **Reduces forwarder cost** and execution time
-- Provides the same tag enrichment as `DdFetchS3Tags` and `DdFetchLogGroupTags`
-- Requires [Resource Collection](https://docs.datadoghq.com/integrations/amazon-web-services/#resource-collection) enabled in your AWS integration
+---
 
-**Deprecation Notice:**
+#### 3. Removed Deprecated PrivateLink Environment Variable
 
-- `DdFetchS3Tags` is now marked as **DEPRECATED** in favor of `DdEnrichS3Tags`
-- `DdFetchLogGroupTags` is now marked as **DEPRECATED** in favor of `DdEnrichCloudwatchTags`
-- `DD_FETCH_S3_TAGS` now defaults to `false` (previously `true`)
+**What Changed:**
+
+- Removed the `DD_USE_PRIVATE_LINK` / `DdUsePrivateLink` environment variable and parameter
+
+**Migration Required:**
+
+- Remove any configuration setting `DD_USE_PRIVATE_LINK=true`
+- **AWS PrivateLink is still fully supported**, but you must follow [PrivateLink documentation](https://docs.datadoghq.com/agent/guide/private-link/):
+    1. Set up VPC endpoints for `api`, `http-logs.intake`, and `trace.agent` as documented
+    2. Configure the forwarder with `DdUseVPC=true`
+    3. Set `VPCSecurityGroupIds` and `VPCSubnetIds`
+
+**Why This Changed:**
+
+- The variable was deprecated since 4 years, we use the major release opportunity to cleanup with a breaking change.
 
 ---