This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
This should be evaluated because our goal was to provide alternative solution. Requires further analysis. Response shared to Support Team before
"Using the private ACL has strong justification here as it preserves full ownership and audit integrity of the license evidence within the workload account where the usage logger produces the files. So we keep the data ownership and S3 ownership on "writer" account of the workload (name it account A) should contain the logger and S3 bucket with private ACL
If the goal of customer is to have the proxy on another account B then they should setup:
In Account A (S3 Bucket): Add the bucket policy statement granting s3:GetObject and s3:ListBucket to arn:aws:iam::<ACCOUNT_B_ID>:role/<PROXY_TASK_ROLE_NAME>.
In Account B (Proxy Task Role): Attach an IAM policy granting s3:GetObject and s3:ListBucket on arn:aws:s3:::<ACCOUNT_A_BUCKET_NAME>/*.
In Account B (Proxy Environment): Set AWS_S3_BUCKET_NAME and AWS_S3_BUCKET_REGION to point to Account A's bucket.
The idea of "one bucket, many accounts" is rather not our target solution from architectural/security perspective since it would mean that various writers contribute to one bucket from various AWS accounts.
Rather other idea should be feasible to use one bucket on one account and ACL=private.
The alternative to consider would be to have single proxy instance on account B to handle S3 buckets from workloads (and loggers) located on various accounts; then it can read cross-account from other accounts where S3 buckets are created; and objects in the bucket via standard IAM permissions and Bucket Policies.