-
Task
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
Not Selected
-
NEW
-
NEW
-
If Release Note Needed, Set a Value
-
-
We've got the notification from AWS that Amazon S3 will stop returning DisplayName: https://docs.aws.amazon.com/AmazonS3/latest/API/API_Owner.html.
The Installer and Storage team are analyzing the potential impact, considering both Logging and Registry also support S3, so heads up to ensure it's going to be analyzed by your teams too. Ignore it if you are already aware of it.
Here is the recommendation from AWS:
1. Review the following APIs that return Owner.DisplayName attribute as part of the response and ensure users completely remove any references:
REST.GET.ACL - GetBucketAcl, GetObjectAcl
REST.GET.BUCKET - ListObjects, ListObjectsV2
REST.GET.BUCKETVERSIONS - ListObjectVersions
REST.GET.LOGGING_STATUS - GetBucketLogging
REST.GET.SERVICE - ListBuckets
REST.GET.UPLOAD - ListParts
REST.GET.UPLOADS - ListMultipartUploads
2. Update applications to use canonical IDs instead of Owner.DisplayName attribute.
3. Implement proper error handling for missing Owner.DisplayName attribute [2]
4. Test applications with Owner.DisplayName attribute removed from responses.
5. Validate owner identification using canonical IDs.
6. Review and update your runbooks and applications that reference Owner.DisplayName attribute
Can you please assess the impact to Logging?