You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: msk-lambda-schema-avro-java-sam/README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,8 @@ This project contains source code and supporting files for a serverless applicat
16
16
-`template_original.yaml` - The original template with placeholders that get replaced during deployment.
17
17
-`MSKAndKafkaClientEC2.yaml` - A CloudFormation template file that can be used to deploy an MSK cluster and also deploy an EC2 machine with all pre-requisites already installed, so you can directly build and deploy the lambda functions and test them out.
18
18
19
-
> [!Important] This application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the [AWS Pricing page](https://aws.amazon.com/pricing/) for details. You are responsible for any AWS costs incurred.
19
+
> [!Important]
20
+
> This application uses various AWS services and there are costs associated with these services after the Free Tier usage - please see the [AWS Pricing page](https://aws.amazon.com/pricing/) for details. You are responsible for any AWS costs incurred.
20
21
21
22
## Requirements
22
23
@@ -35,7 +36,8 @@ There is a CloudFormation template to deploy an Amazon MSK Cluster. You can depl
35
36
36
37
* Once the CloudFormation stack is created, you can go to the EC2 console and log into the machine using either **Connect using EC2 Instance Connect** or **Connect using EC2 Instance Connect Endpoint** option under the *EC2 Instance Connect* tab.
37
38
38
-
> [!NOTE] You may need to wait for some time after the CloudFormation stack is created, as some UserData scripts continue running after the CloudFormation stack shows *Created*.
39
+
> [!NOTE]
40
+
> You may need to wait for some time after the CloudFormation stack is created, as some UserData scripts continue running after the CloudFormation stack shows *Created*.
39
41
40
42
### Check if Kafka Topic has been created
41
43
* Once you are connected to the EC2 machine, you should be in the `/home/ec2-user` folder. Check to see the contents of the file `kafka_topic_creator_output.txt` by running the command:
@@ -93,7 +95,8 @@ sam deploy --capabilities CAPABILITY_IAM --no-confirm-changeset --no-disable-rol
93
95
94
96
The `sam deploy` command packages and deploys your application to AWS, with a series of prompts.
95
97
96
-
> [!NOTE] The script retrieves the required parameters from the CloudFormation outputs in the AWS Console after deploying the `MSKAndKafkaClientEC2.yaml` template. These outputs contain all the necessary information for deploying the Lambda functions. If you connect to a different Kafka cluster, enter the values manually.
98
+
> [!NOTE]
99
+
> The script retrieves the required parameters from the CloudFormation outputs in the AWS Console after deploying the `MSKAndKafkaClientEC2.yaml` template. These outputs contain all the necessary information for deploying the Lambda functions. If you connect to a different Kafka cluster, enter the values manually.
97
100
98
101
***Stack Name**: The name of the stack to deploy to CloudFormation. This should be unique to your account and region, and a good starting point would be something matching your project name.
99
102
***AWS Region**: The AWS region you want to deploy your app to.
0 commit comments