Can't redeploy EKS bulk import optional stack

[patchwork01]

Description

We can't remove and then redeploy the EKS bulk import optional stack. The EKS cluster is deployed with a custom resource provider (see cluster-resource-provider.ts). This includes lambdas and a waiter state machine, that each have a log group. When the optional stack is added and then removed, those log groups are retained but are no longer managed by the CDK. When we add the optional stack back into the Sleeper instance, it fails to deploy because those log groups already exist.

Steps to reproduce

1. Deploy an instance of Sleeper
2. Enable optional stack EksBulkImportStack, wait for CDK deployment
3. Disable optional stack EksBulkImportStack, wait for CDK deployment
4. Enable optional stack EksBulkImportStack
5. See CDK deployment fails because a log group already exists

Expected behaviour

We should be able to disable and re-enable the optional stack as many times as we like.

We need a way to configure the log groups on the custom resource provider lambdas and waiter state machine. We've raised an issue for this on the CDK GitHub repository:

• aws-eks: Configure logging for cluster resource provider aws/aws-cdk#31745

Background

Split from:

• Can't redeploy persistent EMR cluster or other optional stacks #3202

Related to:

• Logs retention policy is not applied to all EKS cluster resources #3451