add scheduled Lambda images

Author: nideveloper

the-scalable-webhook/csharp/README.md

@@ -19,7 +19,7 @@ sure that your serverless resource doesn't scale up to an amount that it DO
 This is done by putting a queue between them and having a lambda with a throttled concurrency policy pull items off the queue and communicate with your 
 serverless resource at a rate it can handle.
 
-![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/architecture.png)
+![Architecture](img/architecture.png)
 
 <strong>NOTE:</strong> For this pattern in the cdk deployable construct I have swapped RDS for DynamoDB. <br /><br />Why? Because it is significantly cheaper/faster for developers to deploy and maintain, I also don't think we lose the essence of the pattern with this swap given we still do the pub/sub deduplication via SQS/Lambda and throttle the subscription lambda. RDS also introduces extra complexity in that it needs to be deployed in a VPC. I am slightly worried developers would get distracted by the extra RDS logic when the main point is the pattern. A real life implementation of this pattern could use RDS MySQL or it could be a call to an on-prem mainframe, the main purpose of the pattern is the throttling to not overload the scale-limited resource.
 

the-scalable-webhook/java/README.md

@@ -19,7 +19,7 @@ sure that your serverless resource doesn't scale up to an amount that it DO
 This is done by putting a queue between them and having a lambda with a throttled concurrency policy pull items off the queue and communicate with your 
 serverless resource at a rate it can handle.
 
-![Architecture](https://raw.githubusercontent.com/cdk-patterns/serverless/master/the-scalable-webhook/img/architecture.png)
+![Architecture](img/architecture.png)
 
 <strong>NOTE:</strong> For this pattern in the cdk deployable construct I have swapped RDS for DynamoDB. <br /><br />Why? Because it is significantly cheaper/faster for developers to deploy and maintain, I also don't think we lose the essence of the pattern with this swap given we still do the pub/sub deduplication via SQS/Lambda and throttle the subscription lambda. RDS also introduces extra complexity in that it needs to be deployed in a VPC. I am slightly worried developers would get distracted by the extra RDS logic when the main point is the pattern. A real life implementation of this pattern could use RDS MySQL or it could be a call to an on-prem mainframe, the main purpose of the pattern is the throttling to not overload the scale-limited resource.
 

the-scheduled-lambda/csharp/README.md

@@ -2,7 +2,7 @@
 
 This is an example CDK stack demonstrating how to use AWS EventBridge to invoke a Lambda function on a schedule or using a cron expression. The Lambda function will then write the request ID to a DynamoDB table.
 
-![The Scheduled Lambda Architecture Diagram](../img/the-scheduled-lambda.png)
+![The Scheduled Lambda Architecture Diagram](img/the-scheduled-lambda.png)
 
 **WARNING**: By default the EventBridge rule has been configured with a rate of 2 minutes, so you are able to quickly see the result of this example. I would strongly recommend destroying the stack using `cdk destroy TheScheduledLambdaStack` so that the scheduled run does not lead to AWS billing you for function invocations.
 

the-scheduled-lambda/csharp/img/the-scheduled-lambda.png

@@ -2,7 +2,7 @@
 
 This is an example CDK stack demonstrating how to use AWS EventBridge to invoke a Lambda function on a schedule or using a cron expression. The Lambda function will then write the request ID to a DynamoDB table.
 
-![The Scheduled Lambda Architecture Diagram](../img/the-scheduled-lambda.png)
+![The Scheduled Lambda Architecture Diagram](img/the-scheduled-lambda.png)
 
 **WARNING**: By default the EventBridge rule has been configured with a rate of 2 minutes, so you are able to quickly see the result of this example. I would strongly recommend destroying the stack using `cdk destroy TheScheduledLambdaStack` so that the scheduled run does not lead to AWS billing you for function invocations.
 

the-scheduled-lambda/java/README.md

@@ -2,7 +2,7 @@
 
 This is an example CDK stack demonstrating how to use AWS EventBridge to invoke a Lambda function on a schedule or using a cron expression. The Lambda function will then write the request ID to a DynamoDB table.
 
-![The Scheduled Lambda Architecture Diagram](../img/the-scheduled-lambda.png)
+![The Scheduled Lambda Architecture Diagram](img/the-scheduled-lambda.png)
 
 Once deployed, this stack will product a Lambda function, DynamoDB table, and an EventBridge rule.
 

the-scheduled-lambda/java/img/the-scheduled-lambda.png

@@ -2,7 +2,7 @@
 
 This is an example CDK stack demonstrating how to use AWS EventBridge to invoke a Lambda function on a schedule or using a cron expression. The Lambda function will then write the request ID to a DynamoDB table.
 
-![The Scheduled Lambda Architecture Diagram](../img/the-scheduled-lambda.png)
+![The Scheduled Lambda Architecture Diagram](img/the-scheduled-lambda.png)
 
 **WARNING**: By default the EventBridge rule has been configured with a rate of 2 minutes, so you are able to quickly see the result of this example. I would strongly recommend destroying the stack using `cdk destroy TheScheduledLambdaStack` so that the scheduled run does not lead to AWS billing you for function invocations.