Skip to content

Infrastructure: Separate RabbitMQ and Redis Intances #957

@Ayush8923

Description

@Ayush8923

Is your feature request related to a problem?
Currently, production and staging RabbitMQ and Redis are running on the same EC2 instance, causing potential conflicts and risks during deployment.

Describe the solution you'd like

  • Separate staging and production RabbitMQ and Redis into different EC2 instances.
  • Configure the credentials in the corresponding production and staging applications.
  • Set up the current staging and production instances on the Kaapi VPC.
Original issue

Describe the current behavior

  • Right now, the production and staging rabbit-mq and redis running on the same ec2 instance in the different VPC. Need to change this flow.

Describe the enhancement you'd like

  • Separate out the staging and production Rabbit-mq and redis in different EC2 instance.
  • Configured the credentials in corresponding prod and staging applications.
  • Create the current staging and production instance on Kaapi VPC.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

Status
In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions