S3 bucket with loggingConfiguration never becomes READY

[kubevalet]

What happened?

Seems like this https://github.com/crossplane-contrib/provider-aws/issues/1382

{
  "atProvider": {
    "arn": "arn:aws:s3:::test-s3-log44-jl5lq-2x787"
  },
  "conditions": [
    {
      "lastTransitionTime": "2024-07-18T15:07:57Z",
      "reason": "Creating",
      "status": "False",
      "type": "Ready"
    },
    {
      "lastTransitionTime": "2024-07-18T15:07:57Z",
      "reason": "ReconcileSuccess",
      "status": "True",
      "type": "Synced"
    }
  ]
}

Makes this tech completely unusable in environments where security compliance is required e.g. SOC2

How can we reproduce it?

Define a bucket with loggingConfiguration set ... here's my describe output (I already had to revert the change):

Spec:
  Deletion Policy:  Orphan
  For Provider:
    Location Constraint:  us-west-2
    Logging Configuration:
      Target Bucket:   log-bucket-dev-usw220240712151134571000000001
      Target Prefix:   test-s3-log44/
    Object Ownership:  BucketOwnerEnforced
    Payment Configuration:
      Payer:  BucketOwner
    Public Access Block Configuration:
      Block Public Acls:        true
      Block Public Policy:      true
      Ignore Public Acls:       true
      Restrict Public Buckets:  true
    Server Side Encryption Configuration:
      Rules:
        Apply Server Side Encryption By Default:
          Sse Algorithm:  AES256
    Versioning Configuration:
      Status:  Suspended
  Management Policies:
    *
  Provider Config Ref:
    Name:  provider-config-aws

What environment did it happen in?

Crossplane version: 1.15.1 AWS provider 0.48.1