๋ฐ์ํ
Intro
์๋ ํ์ธ์. ๋น์คํก ๋ฐฐํฌ ํ๊ฒฝ ๊ตฌ์ฑ ์ค ๋ค์๊ณผ ๊ฐ์ ์๋ฌ๊ฐ ๋ฐ์ํ์์ต๋๋ค.
The EC2 instances failed to communicate with AWS Elastic Beanstalk,
either because of configuration problems with the VPC or a failed EC2 instance.
Check your VPC configuration and try launching the environment again.
Why?
๊ตฌ๊ธ๋ง์ ํด๋ณด๋ ์ธ์คํด์ค ์ค์ ์ค ํผ๋ธ๋ฆญ IP ์ฃผ์ ํ ๋น์ ์ฒดํฌํ์ง ์์ผ๋ฉด ๋ค์ ์๋ฌ๊ฐ ๋ฐ์ํ ์ ์๋ค๊ณ ํฉ๋๋ค.
How to solve the problem
์ ํ๋ฉด๊ณผ ๊ฐ์ด ํผ๋ธ๋ฆญ IP ์ฃผ์ > ํ์ฑํ๋จ์ ์ฒดํฌ๋ฅผ ํ๋ฉด ํด๋น ์๋ฌ๊ฐ ์ฌ๋ผ์ง๊ฒ ๋ฉ๋๋ค.
https://wiki.yowu.dev/ko/dev/AWS/Things-to-know-when-using-Elastic-Beanstalk-in-a-VPC-environment
๋ฐ์ํ
'Devops > AWS' ์นดํ ๊ณ ๋ฆฌ์ ๋ค๋ฅธ ๊ธ
[AWS] AWS ๊ธฐ๋ณธ ์ฌ์ฉ๋ฒ, S3๋ก ํ๋ ํ์ผ ๊ด๋ฆฌ (0) | 2024.07.22 |
---|---|
[AWS] beanstalk healthd.conf not foud ์๋ฌ ๋ฐ์ ์์ธ ๋ฐ ํด๊ฒฐ ๋ฐฉ๋ฒ (1) | 2023.12.11 |
[AWS] EC2 ์ธ์คํด์ค ์คํ ๋ฆฌ์ง๋? (0) | 2023.05.27 |
[AWS SAA] EC2 ์๋ฃจ์ ์ค ์ํคํ ํธ ์ด์์์์ดํธ ๋ ๋ฒจ (0) | 2023.05.23 |
[AWS] EC2๊ธฐ์ด, EC2๋? (0) | 2023.05.21 |