Describe the solution you'd like

In our environment, the AWS S3 bucket where S3 access logs should be stored is pre-created by the "central" team, and we don't have permissions to make any changes to it. Therefore, we don't need to:

• Create it: The current code creates the logging bucket only if it doesn't exist, which is already appropriate.
• Change configuration of the logging bucket, such as ACL, public access, encryption, or TLS enforcement.

Currently, we cannot configure server access logging because we have to use the pre-created bucket. Additionally, it would be beneficial to have the option to configure PartitionDateSource in the logging configuration.
Example:

{
  "LoggingEnabled": {
    "TargetBucket": "<bucket_name> ",
    "TargetPrefix": "",
    "TargetObjectKeyFormat": {
      "PartitionedPrefix": {
        "PartitionDateSource": "EventTime"
      }
    }
  }
}

There is also a small bug because the current code silently fails on the permission error when attempting to configure the logging bucket.

Describe alternatives you've considered

The only alternative is to configure access logging outside of Terragrunt.