Cost optimisation for Kinesis Firehose
A customer is using Kinesis Firehose and not happy with his bill.
I looked in their stats from CloudWatch, divide deliveryToS3.Bytes by deliveryToS3.Record and realised that average size of record is 0.5KB. As I know for billing we round size of a record to 5 KB, which means they are paying use almost 10 times more.
Am I right that the only way to optimise cost is to redesign an App to be able to combine several record into one?
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
One option is to make sure the Buffer Interval is cranked up to the max of 900 seconds. That gives firehose longer to buffer the records together into larger objects. If the source of the data is direct Puts, you definitely want to use PutRecordBatch to send in several records. If the source is machines with the kinesis log agent you can increase the maxBufferAgeMillis to increase how long the client buffers data before sending it to firehose, the trade off being the amount of data lost if something happens to the host.
Contenuto pertinente
AWS UFFICIALEAggiornata 6 mesi fa- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa