Add CloudWatch Contributor Insights Support to ACK Managed DynamoDB Tables #2408
Description
Is your feature request related to a problem?
Currently, while ACK (AWS Controllers for Kubernetes) provides a declarative, Kubernetes-native way to manage DynamoDB tables, it does not support enabling CloudWatch Contributor Insights directly via the CRD. For teams leveraging ACK in multi-cluster environments, this limitation means that Contributor Insights would have to be managed via separate automation (using the AWS CLI, scripts, or other external tooling). This fragmented approach increases operational overhead and risks introducing inconsistencies where the live configuration drifts from the desired state.
Describe the solution you'd like
I would like the ability to configure CloudWatch Contributor Insights directly through ACK when managing DynamoDB tables. Specifically, I propose adding an optional field in the DynamoDB Table CRD—perhaps something like:
spec:
contributorInsights:
enabled: true
This field (and potentially additional configuration options for fine-tuning) would allow users to declaratively enable, disable, or manage Contributor Insights as part of the ACK-managed resource. The controller would then align the desired state for Contributor Insights along with other table configurations. This approach is similar to the read-only mode seen in other Kubernetes operators and would eliminate the need for external post-deployment automation.
Describe alternatives you've considered
The only alternative available at this time is to manually enable and configure Contributor Insights using the AWS CLI or external automation tools after the DynamoDB table has been created via ACK. However, this approach means you have to manage two parts separately, which can cause them to get out of sync if not carefully managed. I have not identified any other alternatives that provide a fully integrated, declarative solution within the ACK framework.