Timelines for your convenience: 00:00 // Intro 00:46 // Introduction to AWS Kinesis 07:22 // What is Streaming Data? 11:00 // AWS Kinesis Video Streams 14:41 // AWS Kinesis Data Streams 16:42 // AWS Kinesis Data Firehose 20:08 // AWS Kinesis Data Analytics 21:52 // What are Click Streaming and Click Path? 27:28 // Important points for Exam
Very nice presentation. The illustrative diagrams are clean and easy to follow - they are extraordinarily helpful. The closing summary is also well executed. Thanx !
Can someone explain the clickstream example at 26:00? I feel like the first component to capture the stream should be Kinesis Data Stream, not the Kinesis Firehose. Can explain the purpose of the Kinesis Firehose there?
Sir, If there is data firehose which can CAPTURE and load real time data into say S3, whats the purpose need of data streams.. KDS captures the real time data.. Data firehose captures and load the real time data. What is special need of KDS if we have firehose. Pls reply Thanks in advance
It depends na, if u need to send it to only s3 and redshift and u only need a managed service you will go for firehose rather than data stream which is manual.
Hi, How do I put data from Firehose to data analytics? Since data analytics has only S3, Redshift, Opensearch etc as Destinations. Can you please help me ?
Yeah in most cases its the same thing but Think of when u are working with a stream of data , where data flow is like a queue, generally we say we pushed the data to the queue Secondly, let suppose i am speaking about a website data being propagated when i open it, we say the data is getting loaded cause its progressive and we feel Its a stack of data and we are trying to load it on to the website. So its more of a representation. But used interchangeably when speaking
Why all the streams are having different output???video stream is having different set of consumer than data streams. Data stream is having different set of consumers than firehose. How to remebr them????
IT depends on what is the use case, you should not take the pain in recollecting all these things, just the use case should be sufficient to create a mapping between what is the out put and where it can be used.
Can you also let me know if the samples provided in aws side for kinesis can be used for production implementation ? or is there anything that i need to take care of
It always depends on what ur use case is, what are u using kinesis for. Is it data streams or firehose or video streams. If firehose you need to understand where you are pushing the data to like splunk or other tools. Mostly as kinesis is a standalone service security at transit play a important role. You can always create an endpoint and make use of it but check ensure data at transit is secure. That's what makes it close to a production deployment
We can surely use IAM roles to secure permissions and most importantly you need to have a monitor in place. Mostly with video streams you should be concerned about the end user who is trying to access it. So access tokens can be a good option to further enhance it. And I believe when we create it we also.secure the endpoint.
