Broken VPC Flow Logs Dynamic Partitioning

[StephenBedard]

Describe the bug
After upgrading to v1.8.1, VPC flow logs are sent to newly named CloudWatch log groups. This breaks the dynamic log partitioning feature of LZA.

To Reproduce

1. Make sure VPC flow logs are configured to send to CWL in your LZA config
2. Upgrade to LZA v1.8.1
3. VPC flow logs will no longer be dynamically partitioned by the ${ACCELERATOR_PREFIX}-FirehoseRecordsProcessor Lambda

Expected behavior
Ideally changes made to the logging stack don't change the name of resources (i.e. CW log group names) that customers refer to in their config for dynamic log partitioning. This can be fixed by modifying the log filters file to match the new log group name patterns (see below screenshot).

Please complete the following information about the solution:

• Version: v1.8.1

To get the version of the solution, you can look at the description of the created AWS CloudFormation stack used to install the LZA (AWSAccelerator-InstallerStack). For example, "(SO0199) Landing Zone Accelerator on AWS. Version 1.5.1.". If the description does not contain the version information, you can look at the Parameters of the stack for the RepositoryBranchName as that should contain the version number.

• Region: ca-central-1
• Was the solution modified from the version published on this repository?
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the services this solution uses?
• Were there any errors in the CloudWatch Logs?

Screenshots

Additional context
Add any other context about the problem here.