How to deploy RabbitMQ in a container with AWS ECS and persistent messages?

cathy_holmes

I am trying to deploy rabbitmq in a container with aws ecs with persistent messages. I have tried the following:1) I have created an ECS task definition with the container name as "rabbitmq"2) I have created an ECS service with the task definition3) I have created an ECS cluster4) I have created an IAM role for the ECS service5) I have created an IAM policy for the ECS service6) I have created an IAM role for the ECS task7) I have created an IAM policy for the ECS task8) I have created an ECS task execution role9) I have created an ECS task execution policy10) I have created an ECS container instance11) I have registered the ECS container instance with the ECS cluster12) I have created an S3 bucket13) I have created an SQS queue14) I have created an SNS topic15) I have subscribed the SQS queue to the SNS topic16) I have created a CloudWatch Logs group17) I have created a CloudWatch Logs stream18) I have added the CloudWatch Logs group to the ECS container instanceI can see that the ECS container instance is running and the ECS task is running. But when I check the CloudWatch Logs, I don't see any messages being written to the log stream. Also, when I check the rabbitmq management console, I don't see any queues or messages. Can someone please help me with this? Thanks in advance.

jean_patterson

There are a few different ways to deploy RabbitMQ in a container with AWS ECS. The most common way is to use the AWS ECS-optimized AMI, which has a built-in container agent that makes it easy to launch and manage containers on AWS ECS.

If you want to use a different container agent, you can either launch your own EC2 instance with the desired container agent or use a managed service like AWS Elastic Beanstalk.

Once you have your container agent set up, you'll need to create a task definition for your RabbitMQ container. The task definition specifies the container image to use, the CPU and memory requirements, and other settings.

Next, you'll create a service using the task definition. The service will launch and maintain a specified number of RabbitMQ containers.

Finally, you can create an Elastic Load Balancer (ELB) to route traffic to your RabbitMQ containers.

For more detailed instructions, see the following guide:

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-rabbitmq.html

Caleb433

You can use AWS ECS and deploy a RabbitMQ container with persistent messages. Here are the steps:

Create an ECS task definition for your RabbitMQ container. Be sure to include these parameters in your task definition:

-A "name" for your container
-The "image" you will use for your container. You can use the official RabbitMQ Docker image: rabbitmq:3
-The "command" you will use to start your container. For example, you can use the following command to start a RabbitMQ container with persistent messages:

"docker run -d --name rabbitmq -p 5672:5672 -p 15672:15672 -e RABBITMQ_DEFAULT_USER=user -e RABBITMQ_DEFAULT_PASS=password rabbitmq:3"

Create an ECS service for your RabbitMQ container. When creating your service, be sure to select your task definition and choose the number of instances you want to run (1 is usually sufficient).
Test your setup by sending a message to your RabbitMQ container. You can use the following command to do this:

"rabbitmqadmin publish exchange=amq.default routing_key=test_queue payload='Hello, World!'"

You should see the message "Hello, World!" appear in the queues tab of the RabbitMQ Management UI.