Cloudwatch日志存储成本核算与S3成本核算 [英] Cloudwatch log store costing vs S3 costing
问题描述
我有一个正在运行apache应用程序的ec2实例。
I have an ec2 instance which is running apache application.
我必须将我的Apache日志存储在某个地方。为此，我使用了两种方法：
I have to store my apache log somewhere. For this, I have used two approaches:
- Cloudwatch Agent将日志推送到cloudwatch
- CronJob将日志文件推送到s3
我已经使用了两种方法。两种方法都适合我。但是，在这里我不担心成本计算。
I have used both of the methods. Both methods suit fine for me. But, here I am little worried about the costing.
其中哪些将具有最低成本？
Which of these will have minimum cost?
推荐答案
S3定价基本上基于三个因素：
S3 Pricing is basically is based upon three factors:
- 存储量。
- 每个月传输的数据量。
- 每月发出的请求数。
同一区域内S3和AWS资源之间的数据传输成本为零。
The cost for data transfer between S3 and AWS resources within the same region is zero.
根据日志的Cloudwatch定价：
所有日志类型。 CloudWatch Logs的任何数据传输都不收费。CloudWatchLogs的Data Transfer OUT已定价。
All log types. There is no Data Transfer IN charge for any of CloudWatch.Data Transfer OUT from CloudWatch Logs is priced.
Cloudwatch日志的定价详细信息：
Pricing details for Cloudwatch logs:
- 收集（数据提取）：$ 0.50 / GB
- 存储（存档）：$ 0.03 / GB
- 分析（Log Insights查询）：$ 0.005 / GB扫描的数据
引用 CloudWatch定价了解更多详情。
类似地，根据AWS，S3定价
Similarly, according to AWS, S3 pricing differs region wise.
例如对于弗吉尼亚州：
S3标准存储
- 前50 TB /月：$ 0.023 / GB
- 后450 TB /月：$ 0.022 / GB
- 每月超过500 TB：每GB $ 0.021
请参阅 S3定价以获取更多详细信息。
Refer S3 pricing for more details.
因此，我们可以得出结论，将日志发送到S3比将它们发送到CloudWatch更具成本效益。
Hence, we can conclude that sending logs to S3 will be more cost effective than sending them to CloudWatch.
这篇关于Cloudwatch日志存储成本核算与S3成本核算的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
