**Describe the bug** If I want to create an S3 bucket with lifecycle policy and do not define any filter within the given rule, not even an empty array, I get the following error message: **Steps to reproduce** Using lifecycle policy without filter defined. ``` lifecycle: rules: - id: RemoveNonCurrentVersionsAfter7Days status: Enabled noncurrentVersionExpiration: noncurrentDays: 7 # filter: {} ``` **Expected outcome** In my opinion, it would be worth using a default empty array in such cases if the user does not define one. **Environment** * ACK S3 controller version: `1.0.35` * Kubernetes version: 1.29 * Using EKS: yes, version 1.29 * AWS service targeted: S3 **Additional context** It would be better if ack can threw more useful error message, as the associated S3 controller did not write any errors in the log. I get this message on the created resource manifest itself, but it would be better if we could also see an error message about the resource spec that is causing the error. This way we don't need to figure it out from scratch which resource spec is causing the problem. Thank you very much!