enable RabbitMQ web management console

[DaMandal0rian]

User description

Only accessible from inside the VPC for security.

---

PR Type

Enhancement

---

Description

• Added ingress rule for RabbitMQ console web management port

• Restricted access using internal VPC security group

---

Changes walkthrough 📝

	Relevant files
Enhancement	broker.tf Add ingress for RabbitMQ console web management                    resources/terraform/auto-drive/broker.tf Added ingress rule for port 15671 for web console Ensured access only from internal EC2 security group +8/-0

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Security Check Verify that the new ingress rule for the RabbitMQ web management console is fully restricted to internal VPC traffic and that the security group configuration prevents any unintended external access. # enable RabbitMQ web management console (only accessible from the VPC) ingress { from_port = 15671 to_port = 15671 protocol = "tcp" security_groups = [aws_security_group.auto_drive_sg.id] # Allow traffic from EC2 server's security group }

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct management console port Verify that the port used for the RabbitMQ management console is correct, as the default port is commonly 15672. resources/terraform/auto-drive/broker.tf [118-124] # enable RabbitMQ web management console (only accessible from the VPC) ingress { - from_port = 15671 - to_port = 15671 + from_port = 15672 + to_port = 15672 protocol = "tcp" security_groups = [aws_security_group.auto_drive_sg.id] # Allow traffic from EC2 server's security group } Suggestion importance[1-10]: 8 __ Why: The suggestion identifies a potential misconfiguration by using port 15671 instead of the common default 15672 for RabbitMQ management console, and the improved code correctly reflects this change in the relevant new hunk lines.	Medium