1 個回答
- 最新
- 最多得票
- 最多評論
0
Yes, proposed workflow makes lot of sense. Migrating this workload on Kinesis Firehose would provide lot of benefits over current architecture like auto scaling, high availability, no administration, ease of use etc.
Firehose pricing is based on volume of data you ingest into Firehose plus charges for data format conversion to Parquet or ORC which is not the requirement here.
Refer to link https://aws.amazon.com/kinesis/data-firehose/pricing/
Pricing example#4 explains how to calculate pricing if Firehose loads data into Elasticsearch cluster. You need to collect volumetric in terms of size of record, count of records/second to be able to calculate monthly pricing of Firehose delivery stream and compare the same with existing solution.
已回答 4 年前
相關內容
- 已提問 6 個月前
- 已提問 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前