Description:

Requests are available to view, but there is no differentiation between a read request and a write request. This can determine what instance is causing a performance bottleneck. The CUR may already have such a field.

Service: Amazon Simple Storage Service

Usage Type: USW2-Requests-SIA-Tier1

Unit: Requests

Line Item Description: $0.01 per 1,000 PUT, COPY, POST or LIST requests to Standard-Infrequent Access

However, there's no direct field that clearly indicates whether a request is a read or write operation.

Feature Request:

It would be helpful to have an additional field or tag that explicitly categorizes each request type as either a read or write. This would enhance visibility and improve the accuracy of usage analytics and cost attribution across services.

Use Case:

This would help teams more easily break down and monitor storage interactions based on operation type (e.g., PUT vs. GET), which is critical for optimizing costs and understanding usage patterns.