Non-standard API Requests for S3 Exceed Threshold
Details about Automated Insights showing savings opportunities for S3.
Non-standard API Requests for S3 Exceed Threshold
This insight identifies when spend on non-standard API requests to S3 is high. This high spend may indicate excess overhead operations on your objects in S3.
Non-standard API requests for S3 include operations like LIST and HEAD. The LIST operation is used for retrieving various configuration information for S3 buckets and the HEAD operation is used for retrieving metadata about an object without retrieving the object itself.
High spend on these operations in comparison to GET and PUT operations may indicate these operations are creating costly overhead. This may be normal if you are serving private objects since HEAD requests for private objects can’t be cached due to the need to generate a signed URL. Public objects can be cached because they don’t require a signed URL. For publicly served objects, consider caching these requests with CloudFront to reduce costs.
Some Items to Note:
- If object metadata changes frequently, you might need to set shorter cache expiration times to ensure your application is receiving the latest information.
Source: CloudZero
The information for this insight is based on spend data in the CloudZero platform.
Frequency
This insight is checked once per day. If the insight is marked as Ignored, it will still get updated, but notifications will no longer be sent for any updates.
Threshold
This insight is created if reducing non-standard S3 API calls will save at least $500 based on a 95% savings rate. When reducing non-standard S3 API calls results in savings less than $500, the insight will automatically be closed.
Updated 2 days ago