You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to do cross-account S3 object transfer with the following constraints:
the bucket-level ownership of the destination bucket is fixed to object writer,
the ACLs of objects from source bucket must be retained when these objects are copied to the destination bucket, and
the copied S3 objects in the destination bucket needs to have object ownership set to the destination AWS account, not the source account.
Problem
If I use this package to do the cross-account S3 transfer via DataSync, the current behavior is that the DataSync task is created and initiated from the source AWS account. This means that when the DataSync transfer task is initiated, the source AWS account effectively becomes the object writer of the copied objects in the destination bucket, violating constraint no. 3.
If I set the bucket-level ownership of the destination bucket to bucket owner enforced (already violating constraint no. 1), this will resolve the issue about objects being owned by the source bucket, at the cost of disabling ACLs and violating constraint no. 2.
Solution
Provide an option for the destination AWS account to be the one that copies S3 objects from source to destination buckets, contrary to the current behavior that the source AWS account is the initiating party. In this case, DataSync-related resources will be created from the destination AWS account.
The text was updated successfully, but these errors were encountered:
C-Collamar
changed the title
Support DataSync transfer initiated from destination AWS account
Allow destination AWS account to initiate the DataSync transfer
Dec 13, 2023
My use case
I need to do cross-account S3 object transfer with the following constraints:
Problem
If I use this package to do the cross-account S3 transfer via DataSync, the current behavior is that the DataSync task is created and initiated from the source AWS account. This means that when the DataSync transfer task is initiated, the source AWS account effectively becomes the object writer of the copied objects in the destination bucket, violating constraint no. 3.
If I set the bucket-level ownership of the destination bucket to bucket owner enforced (already violating constraint no. 1), this will resolve the issue about objects being owned by the source bucket, at the cost of disabling ACLs and violating constraint no. 2.
Solution
Provide an option for the destination AWS account to be the one that copies S3 objects from source to destination buckets, contrary to the current behavior that the source AWS account is the initiating party. In this case, DataSync-related resources will be created from the destination AWS account.
The text was updated successfully, but these errors were encountered: