Skip to content

Conversation

@YuryHrytsuk
Copy link
Collaborator

Since computational clusters run outside docker swarm cluster on AWS Deployments but still need to access RabbitMQ, we need to make it available on private subnets (within VPC). This does not mean public access since manager nodes are private on AWS Deployments.

Bonus:

  • Rename route to management console (add console suffix)

FYI: @sanderegg

What do these changes do?

Related issue/s

Related PR/s

Checklist

  • I tested and it works

Since computational clusters run outside docker swarm cluster on AWS
Deployments but still need to access RabbitMQ, we need to make it
available on private subnets (within VPC). This does not mean public
access since manager nodes are private on AWS Deployments.

Related Issue(s):
* ITISFoundation#1030
@YuryHrytsuk YuryHrytsuk added this to the Pauwel Kwak milestone Apr 24, 2025
@YuryHrytsuk YuryHrytsuk self-assigned this Apr 24, 2025
@YuryHrytsuk YuryHrytsuk changed the title [AWS] Expose rabbit on private subnets [AWS] Expose rabbit for private subnets Apr 24, 2025
Copy link
Member

@sanderegg sanderegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

Copy link
Member

@mrnicegyu11 mrnicegyu11 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, nice!

@YuryHrytsuk YuryHrytsuk enabled auto-merge (squash) April 25, 2025 08:34
@YuryHrytsuk YuryHrytsuk merged commit 9babd62 into ITISFoundation:main Apr 25, 2025
3 checks passed
@YuryHrytsuk YuryHrytsuk deleted the expose-self-hosted-rabbit-mq-on-aws branch April 25, 2025 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants