[AWS] Expose rabbit for private subnets #1032
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
consolesuffix)FYI: @sanderegg
What do these changes do?
Related issue/s
Related PR/s
Checklist