Update video links

Author: jeastham1993

docs/patterns/api-patterns/web-framework-on-lambda.md renamed to docs/patterns/api-patterns/web-framework-on-lambda.mdx

@@ -5,6 +5,8 @@ description: Web Framework on Lambda
 keywords: [rust,lambda,api gateway, lambda web adapter]
 ---
 
+import ReactPlayer from 'react-player'
+
 Adopting the [single Lambda per verb](./cdk-cargo-lambda-lambda-per-verb-ddb.md) way of building serverless API's with Lambda can be a paradigm shift. If you're a developer familiar with starting up your API on localhost, testing and debugging locally before pushing out to production this shift can be a challenge.
 
 If this feels like you, then this article walks you through how you can use the [Lambda Web Adapter](https://github.com/awslabs/aws-lambda-web-adapter) alongside the Rocket web framework for Rust to deploy an entire web application to AWS Lambda.
@@ -13,6 +15,8 @@ Even though this article uses Rocket, this same process would apply for Actix, A
 
 ## Why Might You Want To Do This?
 
+<ReactPlayer controls url='https://youtu.be/DUhRpaux4eE' />
+
 This article isn't going to dive into the nuanced (and potentially controversial) topic of monolithic Lambda's vs having a separate Lambda function per HTTP endpoint and verb. What it will tell you, is why you might want to choose this approach:
 
 1. A more familiar developer experience

docs/patterns/messaging-patterns/eventbridge-event-handler.md renamed to docs/patterns/messaging-patterns/eventbridge-event-handler.mdx

@@ -5,6 +5,8 @@ description: Lambda function for handling an event from Amazon EventBridge
 keywords: [rust,lambda,eventbridge,messaging,putevent]
 ---
 
+import ReactPlayer from 'react-player'
+
 As mentioned in several of the other messaging quick starts, the publisher/subscriber (pub/sub) pattern is extremely common in a serverless architecture. Severless encourages micro and someties even nano-sized components that are assembled together by way of contracts as opposed to building everything into a single binary.
 
 AWS' EventBridge is a service that describes itself like this:
@@ -13,6 +15,12 @@ AWS' EventBridge is a service that describes itself like this:
 
 It provides a Default Bus or you are able to add Custom Event Buses to fit your need.  This article will look to showcase how to create a Lambda function that handles an event from an EventBridge custom bus. It also takes the publishing component from the article on [Event Bridge Put Events](./eventbridge-putevent.md) to give a cohesive pub/sub experience.
 
+## Video Walkthrough
+
+If video is more your thing, then check out this walkthrough on YouTube. Otherwise, keep reading for the written documentation.
+
+<ReactPlayer controls url='https://youtu.be/DUm2rHbiFTs' />
+
 ## How It Works
 
 The sample in this tutorial builds upon a Lambda that listens on a Function URL and then generates an EventBridge PutEvent with a custom domain model. A Rule is defined by the subscriber on the custom event bus that sends any matching messages to a Lambda function. The subscriber Lambda function will deserialize and process the message.

docs/patterns/messaging-patterns/sam-lambda-kinesis-message-processor.md renamed to docs/patterns/messaging-patterns/sam-lambda-kinesis-message-processor.mdx

@@ -5,10 +5,18 @@ description: Lambda function for processing messages from a Kinesis stream
 keywords: [rust,lambda,kinesis,messaging,streaming data]
 ---
 
+import ReactPlayer from 'react-player'
+
 With the explosion of data streaming, whether that be readings from IoT sensors or events in an event driven architectures, the amount of data moving around in your organisation is probably increasing. As this volume continues to grow, your ability to process records from the stream quickly and efficiently is going to have a direct impact on the cost and scalability of your system.
 
 Amazon Kinesis is a serverless streaming service provided by AWS. It allows producers to put messages onto the stream and services like AWS Lambda and Amazon Event Bridge Pipes can be added as consumers of records on the stream.
 
+## Video Walkthrough
+
+If video is more your thing, then check out this walkthrough on YouTube. Otherwise, keep reading for the written documentation.
+
+<ReactPlayer controls url='https://youtu.be/yd0iUPMG-DM' />
+
 ## How It Works
 
 The Kinesis to Lambda integration is an example of a [poll based invoke](../../fundamentals/invocation-modes.md#poll-based-invokes). Internally, the Lambda service polls the Kinesis stream on your behalf and invokes your Lambda function with a batch of messages. As a developer, that means you need to write your Lambda functions to handle a batch of messages.

docs/patterns/messaging-patterns/sam-lambda-sqs-message-processor.mdx

@@ -15,7 +15,7 @@ Amazon Simple Queue Service (SQS) was the first AWS service ever released (it's
 
 If video is more your thing, then check out this walkthrough on YouTube. Otherwise, keep reading for the written documentation.
 
-<ReactPlayer playing controls url='https://youtu.be/OwLa42lssc0' />
+<ReactPlayer controls url='https://youtu.be/OwLa42lssc0' />
 
 ## How It Works