README.md

Event driven Amazon MQ ActiveMQ message processing using AWS Lambda (Java)

This sample project demonstrates event driven message processing from an Amazon MQ ActiveMQ queue using an AWS Lambda function written in Java.

Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/patterns/activemq-lambda-sam-java

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 for details. You are responsible for any AWS costs incurred. No warranty is implied in this example.

Requirements

• Create an AWS account if you do not already have one and log in. The IAM user that you use must have sufficient permissions to make necessary AWS service calls and manage AWS resources.
• AWS CLI installed and configured
• Git Installed
• AWS Serverless Application Model (AWS SAM) installed
• Java 21 or above installed
• Maven 3.9.6 or above installed

Deployment Instructions

1. Create a new directory, navigate to that directory in a terminal and clone the GitHub repository:

   git clone https://github.com/aws-samples/serverless-patterns

2. Change directory to the pattern directory:

   cd serverless-patterns/activemq-lambda-sam-java

3. From the command line, execute the below command to build the Java based AWS Lambda function.

   sam build

4. From the command line, use AWS SAM to deploy the AWS resources for the pattern as specified in the template.yml file:

   sam deploy --guided

5. During the prompts:

   • Enter a stack name
   • Enter the desired AWS Region (e.g. us-east-1).
   • Enter a username. User Name can't contain commas (,), colons (:), equals signs (=), or spaces.
   • Enter a password. Password must be minimum 12 characters, at least 4 unique characters. Can't contain commas (,), colons (:), equals signs (=), spaces or non-printable ASCII characters.
   • Allow SAM CLI to create IAM roles with the required permissions.
   • Keep default values to the rest of the parameters.

   Once you have run sam deploy --guided mode once and saved arguments to a configuration file (samconfig.toml), you can use sam deploy in future to use these defaults.

6. Note the outputs from the SAM deployment process. These contain the resource names and/or ARNs which are used for next step as well as testing.

How it works

Please refer to the architecture diagram below:

Here's a breakdown of the steps:

1. Amazon MQ: An ActiveMQ single-instance broker is provisioned. A test queue with name MyTestQueue is created. A message is pushed to the queue.

2. AWS Lambda: AWS Lambda has an event source mapping (ESM) configured for MyTestQueue queue. The Lambda function is triggered by the new message on the Amazon MQ queue. The Lambda function processes the message and logs the decoded the message content.

Testing

1. Log into the ActiveMQ Web Console using the username and password provided at the time of deployment. The console URL is available in theActiveMQWebConsole key of sam deploy output.

2. Click on the Queues tab to open the list of queues.

3. Click on the Send To link under Operations tab next to the MyTestQueue queue.

4. Enter a Message Body and click Send button.

5. Execute the below command to tail logs of the AWS Lambda function. Please replace MyMQMessageHandlerFunction from the sam deploy -g output and also your region.

   aws logs tail --follow /aws/lambda/{MyMQMessageHandlerFunction} --region {your-region}

6. Check the AWS Lambda console log. It should print the message from the Amazon MQ queue.

7. Press Ctrl + c to stop tailing the logs.

Cleanup

1. To delete the resources deployed to your AWS account via AWS SAM, run the following command:

sam delete

---

Copyright 2024 Amazon.com, Inc. or its affiliates. All Rights Reserved.

SPDX-License-Identifier: MIT-0