Lack of necessary permissions in worker instance to set Object ACL in Destination settings

[hahahadebuger]

Describe the bug
Lack of necessary permissions in worker instance to set Object ACL in Destination settings, the policy which name like "EC2WorkerStackWorkerAsgRoleDefaultPolicy" of the role of the worker instance which name like "DTH-S3EC2-28ace-EC2WorkerStackWorkerAsgRole" lack of s3:PutObjectAcl.

		{
			"Action": [
				"s3:GetObject*",
				"s3:GetBucket*",
				"s3:List*",
				"s3:DeleteObject*",
				"s3:PutObject",
				"s3:PutObjectLegalHold",
				"s3:PutObjectRetention",
				"s3:PutObjectTagging",
				"s3:PutObjectVersionTagging",
				"s3:Abort*"
			],
			"Resource": [
				"arn:aws:s3:::Destination_BUCKET",
				"arn:aws:s3:::Destination_BUCKET/*"
			],
			"Effect": "Allow"
		},

To Reproduce
set Object ACL in Destination settings, such as public read

Expected behavior
there is no error and no need to modify the policy to transfer file to Destination with right acl

Please complete the following information about the solution:

• Version: v2.6.0

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO8001) - Data Transfer Hub with aws-solutions-constructs: This template deploys an one-stop toolset for transferring data from different sources into AWS. Template version v2.6.0".

• Region: ap-southeast-1
• Was the solution modified from the version published on this repository? NO
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the sevices this solution uses? YES
• Were there any errors in the CloudWatch Logs?

2024/05/21 09:00:58 S3> Got an error uploading file - operation error S3: PutObject, https response error StatusCode: 403, RequestID: HAHW5J4AN152NKH5, HostID: gT/oQFRKZU3jShTvUzUHCXlgbJRYcoAi0s/uKSL3fqLEAx49YBhixOJJ8SAUs0G0nPne08ZxKw7oqtBrVoSP9w==, api error AccessDenied: Access Denied

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

[YikaiHu]

Hi @hahahadebuger , thanks for calling out!
We will fix this issue in next release.