node.jsamazon-elastic-beanstalk
"no data" health status while deploying node app via beanstalk
I tried to deploy a simple node application (code here via AWS Elastic BeanStalk by going with all default options except that I uploaded the sample application as default one didn't work.
In all my attempts, I eventually get "No data" error as health status. After 12-16 mins of wait, the last line in the logs say
Environment health has transitioned from Pending to No Data. Initialization in progress (running for 16 minutes). There are no instances.
Could someone please help me here?
Solution
For the benefit of others, I managed to resolve above issue by configuring VPC which wasn't configured by default.
- I want to install the "n" package and I get an error
- n <version> command does not activate specified version
- Change n install location
- How to install a specific version of Node on Ubuntu/Debian?
- Different node version for different projects, is there a way of telling node which version to use?
- Install Node.js to install n to install Node.js?
- How to select the latest node.js v6 version using n?
- n-install: ERROR: GNU Make not found, which is required for operation
- How to downgrade Node version with n
- how switch to previous version in n (Node version manager)?
- Automatically use the right version of Node for a package
- internal/modules/cjs/loader.js:905 -> throw err;
- Why doesn't "n" downgrade my node version on a Mac?
- Node version manager
- n failed to install/switch node in Linux?
- vue command not found on Mac
- How to uninstall n and all node versions installed by n
- Angular CLI on HTTPS - can't install CI as root
- n (node version manager): cannot create directory
- npm module n emits errors
- How to update npm permanently?
- Cannot change nodejs version using n
- upgrade nodejs to stable version
- How should I install and use multiple versions of Node on the same production machine?