IBM License Usage Logger for Fargate- Support cross-account bucket configurations

Background: Through IBM Support case TS023136250, we identified that the IBM License Usage Logger for Fargate (v1.20.17/v1.20.19) hardcodes the S3 upload ACL to private, which forces object ownership to remain with the writing (member) account. IBM development confirmed this behavior and advised that a code change would be required to support cross-account bucket configurations, directing us to submit a formal enhancement request via IBM Ideas (ideas.ibm.com) for further analysis and roadmap consideration.

Business Need: Our organization operates a central-account architecture in which a single centralized S3 bucket, KMS key, and License Reporter Proxy are intended to aggregate license usage data from multiple AWS member accounts running ECS Fargate workloads. Because the Logger signs uploads with acl=private, objects remain owned by the member account, causing the central Reporter Proxy to receive 403 errors when attempting to read consolidated usage data. This prevents the documented "one bucket, many accounts" consolidation model from functioning as intended and limits our ability to centralize license usage reporting across accounts, which is critical to our governance and audit requirements.

Requested Enhancement: We are requesting that IBM evaluate modifying the Logger to either send bucket-owner-full-control instead of private on S3 object upload, or omit the ACL entirely to support S3 "Bucket Owner Enforced" settings. This change would allow the centralized Reporter Proxy to read usage objects written by Loggers in other AWS accounts without compromising security, while still preserving auditability of license evidence. We ask that this enhancement be logged for formal development review and prioritization, with visibility into target release timelines once scoped.