CODEWITHSUNDEEP
node.jsamazon-web-servicesnginxamazon-ec2amazon-elastic-beanstalk
Huang
Huang

Reputation: 1355

AWS node.js migration

I am about to inherit on a Node.js project which is a number of node webservers running on a single EC2 instance. Routing is done using nginx instance running on the same EC2 instance, these node servers connect to RDS postgres dbs and elastiCache redis instance. I am to move this so each server has its own instance and the system can autoscale properly.

From what I can tell the webservers are mainly stateless. I am thinking of sticking with AWS products, like Elasticbeanstalk or Opsworks, I think chef can handle this change but wanted to know what would be best practices for this scenario.

Upvotes: 0

Views: 227

Answers (1)

robertomarin
robertomarin

Reputation: 1282

For the scenario you described looks very easy to build an Beanstalk Node application and environment.

You have the endpoints for the RDS Postgres database and Redis on Elasticache, so the only thing you need to do is to create the environment and test it.

If this two is your only dependencies, I would start by the AWS panel. There you can create your Beanstalk application, deploy it and test it.

Be careful when deploying the first environment and point your endpoints [rds, elasticache] to a QA environment, this way you avoid compromising production data. ;)

Upvotes: 1

Related Questions