https://github.com/tsmx/beanstalktest
Test-project for AWS Beanstalk using NodeJS.
https://github.com/tsmx/beanstalktest
Last synced: over 1 year ago
JSON representation
Test-project for AWS Beanstalk using NodeJS.
- Host: GitHub
- URL: https://github.com/tsmx/beanstalktest
- Owner: tsmx
- License: mit
- Created: 2019-08-08T18:09:34.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2022-12-19T11:54:27.000Z (over 3 years ago)
- Last Synced: 2025-01-11T19:24:03.132Z (over 1 year ago)
- Language: JavaScript
- Size: 555 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# AWS Beanstalk Test with NodeJS and Express
This is a (very simple) test project to demonstrate and test the AWS Elastic Beanstalk stack with NodeJS.
Setting up Beanstalk at AWS:
- in the app main folder run the following command
```
eb init (IAM credentials with rights to Beantsalk needed)
eb create 'environment-name'
eb create 'environment-name' --vpc --vpc.elbpublic (create inside a VPC with public available Loadbalancer --> VPC-ID and Subnets needed!)
eb deploy
eb terminate 'environment-name' (will delete the entire environment)
```
Useful commands / hints:
- for IAM: create a group and user with sufficient rights for Beanstalk
- create a role with 'AWSElasticBeanstalkFullAccess'
- create a user and assign the role
- eb list (lists all available environments of the app)
- create ssl cert:
```
openssl req -x509 -newkey rsa:2048 -keyout test.key -out test.crt -days 365 -nodes
```
Note: Only keys up to 2048bits are supported by the AWS Cert Manager!!! (as of 2019) 4096bit keys are only working through direct IAM upload.
- save complex configurations and recall them at
```
eb create --cfg 'config-name' 'environment-name'
```
- a running environment cannot be stopped, only terminated!
- a running environment causes costs for EC2 even without requests / in idle mode! (take into account when just playing around...)