ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Access: Direct RabbitMQ for ECS
Open
@Ayush8923 is already working on this.
Since Sep 2, 2026.
enhancement
infrastructure
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
Currently, the RabbitMQ instance in ECS production can be accessed directly. This means the instance is reachable without going through the bastion host, which is not the desired security setup.
Describe the solution you'd like
- Restrict direct access to the RabbitMQ instance in ECS production and place it behind the bastion host.
- RabbitMQ should only be accessible when connected through the bastion. This will ensure that the RabbitMQ instance is not directly reachable via its IP address and that access is controlled through the bastion host.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.