Introduction to Amazon Kinesis Firehose recensioni

Matt C. · Recensione inserita quasi 8 anni fa

Peter M. · Recensione inserita quasi 8 anni fa

Dustin S. · Recensione inserita quasi 8 anni fa

Archana S. · Recensione inserita quasi 8 anni fa

sai krishna r. · Recensione inserita quasi 8 anni fa

yuppppppppppppp

omar s. · Recensione inserita quasi 8 anni fa

Junho L. · Recensione inserita quasi 8 anni fa

Ian M. · Recensione inserita quasi 8 anni fa

Had problems with instructions - EC2 was unable to see mystream when only firehose created: 2016-12-17 20:48:32.849+0000 ip-10-0-0-112 (sender-11) com.amazon.kinesis.streaming.agent.tailing.AsyncPublisher [ERROR] AsyncPublisher[kinesis:mystream:/tmp/app.log*]:RecordBuffer(id=2,records=6,bytes=367) Retriable send error (com.amazonaws.services.kinesis.model.ResourceNotFoundException: Stream mystream under account 126546796233 not found. (Service: AmazonKinesis; Status Code: 400; Error Code: ResourceNotFoundException; Request ID: de17e898-9705-a6da-8ed8-4e78e5cc7318)). Will retry. [ec2-user@ip-10-0-0-112 ~]$ aws firehose list-delivery-streams { "DeliveryStreamNames": [ "mystream" ], "HasMoreDeliveryStreams": false } [ec2-user@ip-10-0-0-112 ~]$ aws kinesis list-streams { "StreamNames": [] } Once I created a kinesis stream (not firehose) called mystream, it was able to send data but then the lab ended as I presume there is some plumbing between the two. [ec2-user@ip-10-0-0-112 ~]$ aws kinesis list-streams { "StreamNames": [ "mystream" ] } 2016-12-17 20:50:29.804+0000 ip-10-0-0-112 (FileTailer[fh:mystream:/tmp/app.log*].MetricsEmitter RUNNING) com.amazon.kinesis.streaming.agent.tailing.FileTailer [INFO] FileTailer[fh:mystream:/tmp/app.log*]: Tailer Progress: Tailer has parsed 6 records (264 bytes), transformed 0 records, skipped 0 records, and has successfully sent 6 records to destination. 2016-12-17 20:50:29.812+0000 ip-10-0-0-112 (Agent.MetricsEmitter RUNNING) com.amazon.kinesis.streaming.agent.Agent [INFO] Agent: Progress: 12 records parsed (968 bytes), and 6 records sent successfully to destinations. Uptime: 270059ms

Brian S. · Recensione inserita quasi 8 anni fa

Steve B. · Recensione inserita quasi 8 anni fa

Foday C. · Recensione inserita quasi 8 anni fa

Hong L. · Recensione inserita quasi 8 anni fa

PPK file is not working. WHiel connecting from Putty getting error "Server refused key"

Ramu V. · Recensione inserita quasi 8 anni fa

3 stars

ASHWINI C. · Recensione inserita quasi 8 anni fa

Sajitha P. · Recensione inserita quasi 8 anni fa

I couldn't find the Quries tab in the final step so couldn't complete the lab and see the stream coming through to Redshift.

mike c. · Recensione inserita quasi 8 anni fa

Jon A. · Recensione inserita quasi 8 anni fa

Josh B. · Recensione inserita quasi 8 anni fa

Ramon R. · Recensione inserita quasi 8 anni fa

Pedro N. · Recensione inserita quasi 8 anni fa

Liang F. · Recensione inserita quasi 8 anni fa

could use an update (interface has changed some since this was written)

Greg M. · Recensione inserita quasi 8 anni fa

The tutorial skipped few important steps. Unable to select a Redshift cluster from drop down when creating a delivery stream.

Vinaya Kumar B. · Recensione inserita quasi 8 anni fa

Antonio I. · Recensione inserita quasi 8 anni fa

Patrick G. · Recensione inserita quasi 8 anni fa