Opinie (Introduction to Amazon Kinesis Firehose)

amy l. · Sprawdzono ponad 7 lat temu

3

Rajnish G. · Sprawdzono ponad 7 lat temu

Candi H. · Sprawdzono ponad 7 lat temu

1) The /etc/aws-kinesis/agent.json has configurations for both Kinesis Stream and Firehose. It is causing the Stream's part to fail because this lab didn't setup Stream; it only set up Firehose. Therefore, when "tail -f /var/log/aws-kinesis-agent/aws-kinesis-agent.log", all I see is a constant parade of (Stream) errors which is very misleading -- the Firehose part is actually working. 2) It would be beneficial to have some instructions to let the students browse the "cities" table in RedShift to see that the data actually reached RedShift. 3) The CloudWatch screen (step 59) doesn't match the instruction -- maybe the UI has changed?

Vincent Y. · Sprawdzono ponad 7 lat temu

Emre Y. · Sprawdzono ponad 7 lat temu

Would have been nice to have included data transformation with Kinesis

Scott F. · Sprawdzono ponad 7 lat temu

Aoyagi M. · Sprawdzono ponad 7 lat temu

Bryan F. · Sprawdzono ponad 7 lat temu

Agustin F. · Sprawdzono ponad 7 lat temu

Gavin B. · Sprawdzono ponad 7 lat temu

It was good, but I couldn't make Kinesis Agent to push data to Kinesis Firehose. I double check the region during the lab, but I could only see this error in the agent log: AAAA-MM-DD HH:33:13.004+0000 ip-xx-xx-xx-xx (sender-34) com.amazon.kinesis.streaming.agent.tailing.AsyncPublisher [ERROR] AsyncPublisher[kinesis:mystream:/tmp/app.log*]:RecordBuffer(id=2,records=67,bytes=4099) Retriable send error (com.amazonaws.services.kinesis.model.ResourceNotFoundException: Stream mystream under account xxxx not found. (Service: AmazonKinesis; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: xxx)). Will retry.

Develop D. · Sprawdzono ponad 7 lat temu

Martin T. · Sprawdzono ponad 7 lat temu

Agustin F. · Sprawdzono ponad 7 lat temu

William X. · Sprawdzono ponad 7 lat temu

This is very good.

Jinjun S. · Sprawdzono ponad 7 lat temu

Roberto C. · Sprawdzono ponad 7 lat temu

Bit of a stretch to finish in 45 minutes if the data takes 15 minutes to propagate

James O. · Sprawdzono ponad 7 lat temu

Thomas S. · Sprawdzono ponad 7 lat temu

Lilian H. · Sprawdzono ponad 7 lat temu

Claudio O. · Sprawdzono ponad 7 lat temu

This lab is well-explained and proportionate a great approach to the AWS tools.

Daniel S. · Sprawdzono ponad 7 lat temu

Priscila S. · Sprawdzono ponad 7 lat temu

obrigado

Paulo R. · Sprawdzono ponad 7 lat temu

Lilian H. · Sprawdzono ponad 7 lat temu

Glen T. · Sprawdzono ponad 7 lat temu