Skip to main content
NetApp Knowledge Base

Impact for Fabric Pool while Amazon S3 stop returning Owner.DisplayName for all request responses

  1. Last updated
  2. Save as PDF
Views:
78
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP 9
  • Fabric Pool
  • Amazon Simple Storage Service (Amazon S3)

Answer

There is no impact to Fabric Pool as it is not sending S3 API request / receiving response that including Owner.DisplayName.

Additional Information

Beginning September 15, 2025, emails about AWS Health events will be delivered via AWS User Notifications. 

---

Hello,

On November 21, 2025, Amazon Simple Storage Service (Amazon S3) will stop returning Owner.DisplayName for all request responses. Owner.DisplayName is a legacy field that most modern applications do not rely on as it has been superseded by AWS Account IDs and IAM ARNs. Until November 21, 2025, S3 will progressively remove this field from request responses. After this date, Owner.DisplayName will not be returned for any requests made to Amazon S3.

The Owner.DisplayName parameter is supported only in eight AWS Regions on eight Amazon S3 APIs. If you have applications that rely on this behavior to validate ownership of objects, we recommend using canonical IDs (unique identifier for AWS accounts), AWS account ID (12 digit identifier) or IAM ARNs (full resource naming) as a direct replacement of Owner.DisplayName.

This change affects the following AWS Regions: US-EAST-1 Region, US-WEST-1 Region, US-WEST-2 Region, AP-SOUTHEAST-1 Region, AP-SOUTHEAST-2 Region, AP-NORTHEAST-1 Region, EU-WEST-1 Region, and SA-EAST-1 Region.

This is also communicated in S3 documentation [1].

Important Dates:

* From now until November 21, 2025: S3 will gradually stop returning the Owner.DisplayName.
* Beginning November 21, 2025: Owner.DisplayName will not be returned across all requests to Amazon S3 in any AWS region.

Recommended Actions:

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 REST.GET.BUCKETVERSIONS - ListObjectVersions REST.GET.LOGGING_STATUS - GetBucketLogging REST.GET.SERVICE - ListBuckets REST.GET.UPLOAD - ListParts REST.GET.UPLOADS - ListMultipartUploads REST.PUT.BUCKET - CreateBucket

2. Update applications to use canonical IDs instead of Owner.DisplayName attribute.
3. Implement proper error handling for missing Owner.DisplayName attribute [2][3].
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.

If you have any questions or concerns, please reach out to AWS Support [4].

[1] https://docs.aws.amazon.com/AmazonS3/latest/API/API_Owner.html
[2] https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
[3] https://docs.aws.amazon.com/AmazonS3/latest/userguide/troubleshoot-403-errors.html
[4] https://aws.amazon.com/support

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210

---

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.