2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
Hi, the tiering is applied on all vended logs volume ingested to CloudWatch and not tiered per service.
respondido hace 8 meses
Contenido relevante
- ¿Cómo puedo vender una instancia reservada de Amazon EC2 en el Marketplace de instancias reservadas?OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
- ¿Cómo puedo analizar los registros de flujo de VPC personalizados mediante CloudWatch Logs Insights?OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 2 años
You could reverse the question: if it were tiered per service, that would be documented. As CloudWatch mentions a price for vended logs without mentioning that tiering would be split per service, it is implicit that the tiering applies on all vended logs received by CloudWatch.
You can see that by querying the price list API (https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-ppslong.html): if you download the offer for CloudWatch, you'll see that vended logs pricing entries do not have any dimension on operation or any other available input field than the usage type, so the tiering is applied across the (vended log) usage types of a same region without varying per operation or service or another input dimension.
By contrast, you can check from that same price list file that the log delivery varies by a "destination" dimension, for example logs delivered to S3 in Parquet format have a different pricing from logs delivered to S3 in Json format, as per the line "Format Converted to Apache Parquet" in CloudWatch pricing page.