- 최신
- 최다 투표
- 가장 많은 댓글
The issue here was that I had created a custom AMI by deploying a Beanstalk instance. Apparently that leads to unexpected behavior and the correct way of creating a custom for Beanstalk is by deploying a Beanstalk AMI to EC2, editing it, and then saving it and deploying to Beanstalk.
I had to sign up for Amazon premium support and do "live chat". They were very helpful.
One other thing - I ran into a separate issue that I hadn't seen before during setup. I was using ts-node
(for a Typescript / Node.JS) project and it wasn't finding tsconfig-paths
(I use this so I can have paths global to my code's src
dir). I am installing these globally via .ebextensions. Apparently Elasticbeanstalk won't load env variables during
.ebextensions` setup so you need to include a script first:
.ebextensions/0_set_env_variables.config
commands:
setvars:
command: /opt/elasticbeanstalk/bin/get-config environment | jq -r 'to_entries | .[] | "export \(.key)=\"\(.value)\""' > /etc/profile.d/sh.local
packages:
yum:
jq: []
관련 콘텐츠
- AWS 공식업데이트됨 10달 전
- AWS 공식업데이트됨 일 년 전