Skip to main content
NetApp Knowledge Base

Increase in AWS S3 billing due to increase in ONTAP API GET calls

  1. Last updated
  2. Save as PDF
Views:
119
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

Applies to

  • ONTAP 9
  • Cloud Volumes ONTAP
  • AWS
  • S3 bucket 

Issue

  • Increase in AWS S3 bucket billing due to increase in ONTAP API "GET" calls to the capacity tier.
  • High number of "GET" calls from ONTAP, specifically the cluster interconnect LIF IP address caused an increase in billing on the capacity tier as shown in the screen shot below:

 Increase in AWS S3 billing due to increase in ONTAP API GET calls

  • The increased costs occur after modifying the default value for -unreclaimed space threshold parameter for the object store. The –unreclaimed-space-threshold % was modified from the default value of 40% to 80:
    • xxxx.xxxx xxxxx Sat Jun 08 2024 13:33:33 -04:00 [kern_audit:info:xxx] xxxx :: xxxx :: xx.xx.xx.x:xxx :: xx:admin :: storage aggregate object-store modify -aggregate xxxx -object-store-name xxx -unreclaimed-space-threshold 80 :: Success
  • After this change was made, a gradual increase in "GET" calls from ONTAP to S3 started as well as well as an increase in billing on the the S3 as shown in the picture above.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.