1. 문제 상황

2023-06-06 02:19:41 INFO createEnvironment is starting.
2023-06-06 02:19:43 INFO Using elasticbeanstalk-ap-northeast-2-792226969596 as Amazon S3 storage bucket for environment data.
2023-06-06 02:20:03 INFO Created security group named: sg-0e67381bc96082f55
2023-06-06 02:20:19 INFO Created security group named: awseb-e-ipwwgtkp2r-stack-AWSEBSecurityGroup-14ZXYWV09H72A
2023-06-06 02:20:19 INFO Created target group named: arn:aws:elasticloadbalancing:ap-northeast-2:792226969596:targetgroup/awseb-AWSEB-RTYBCOUNX26M/b6bce50926ca836c
2023-06-06 02:20:19 INFO Created Auto Scaling launch configuration named: awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingLaunchConfiguration-h5HHlxU3EHY3
2023-06-06 02:20:34 INFO Created Auto Scaling group named: awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingGroup-1OW62TIN2SLL2
2023-06-06 02:20:34 INFO Waiting for EC2 instances to launch. This may take a few minutes.
2023-06-06 02:20:50 INFO Created Auto Scaling group policy named: arn:aws:autoscaling:ap-northeast-2:792226969596:scalingPolicy:6be112bf-b728-4eeb-a04d-55b1b3e2aaab:autoScalingGroupName/awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingGroup-1OW62TIN2SLL2:policyName/awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingScaleUpPolicy-AZhNIWDMJCzg
2023-06-06 02:20:50 INFO Created Auto Scaling group policy named: arn:aws:autoscaling:ap-northeast-2:792226969596:scalingPolicy:6cfc3be4-fa9e-41fe-9709-9a585ff292c2:autoScalingGroupName/awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingGroup-1OW62TIN2SLL2:policyName/awseb-e-ipwwgtkp2r-stack-AWSEBAutoScalingScaleDownPolicy-7AI7X5ONdL1e
2023-06-06 02:20:50 INFO Created CloudWatch alarm named: awseb-e-ipwwgtkp2r-stack-AWSEBCloudwatchAlarmHigh-1S70LXFYGN7X8
2023-06-06 02:20:50 INFO Created CloudWatch alarm named: awseb-e-ipwwgtkp2r-stack-AWSEBCloudwatchAlarmLow-12U2U9WLSRX8Q
2023-06-06 02:21:36 INFO Created load balancer named: arn:aws:elasticloadbalancing:ap-northeast-2:792226969596:loadbalancer/app/awseb-AWSEB-1CU8XH4HAW159/728f096d4c5c5f8d
2023-06-06 02:21:38 INFO Created Load Balancer listener named: arn:aws:elasticloadbalancing:ap-northeast-2:792226969596:listener/app/awseb-AWSEB-1CU8XH4HAW159/728f096d4c5c5f8d/2df0406389297c15
2023-06-06 02:21:49 ERROR Instance deployment failed to install application dependencies. The deployment failed.
2023-06-06 02:21:49 ERROR Instance deployment failed. For details, see 'eb-engine.log'.
2023-06-06 02:21:50 ERROR [Instance: i-0f23e4a47102fe87e] Command failed on instance. Return code: 1 Output: Engine execution has encountered an error..
2023-06-06 02:21:51 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2023-06-06 02:22:53 ERROR Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.

이 중에서 에러 메시지가 뜬 부분만 번역해보자면,

Instance deployment failed to install application dependencies. The deployment failed.
인스턴스 배포가 애플리케이션 종속성을 설치하지 못했습니다. 배포에 실패했습니다.

Instance deployment failed. For details, see 'eb-engine.log'.
인스턴스 배포에 실패했습니다. 자세한 내용은 'eb-engine.log'를 참조하십시오.

Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.
환경 만들기 작업이 완료되었지만 오류가 있습니다. 자세한 내용은 문제 해결 설명서를 참조하십시오.

2. 시도한 방법

애플리케이션과 환경 이름이 왜 '9'나 되냐면...
거의 10번 정도를 애플리케이션과 환경을 지우고 생성하고를 반복했기 때문이다.

3. 해결법

정말 어이없게도 폴더 위치의 문제였다.

배포를 하려는 파일의 위치는 원래 바탕화면 > sparta > projects > 04.bucket

그러나 정리병 때문에 해당 폴더를 다른 폴더 안으로 옮겨서 보기 좋게 분류해뒀었다.
이게 문제였다.

결국 해당 폴더를 바탕화면으로 다시 이동시켰더니 정상 배포되었다.

4. 느낀점

구글링을 해보고, 매니저님들께도 여쭤보고.
그렇게 10번 정도를 시도했었다.

계속 실패할 때마다 오기가 생겨서 2시 전에 해결하고만다는 생각으로 계속 도전했다.
그리고 결국엔 이렇게 해결책을 찾을 수 있었다.

무슨 에러가 뜨든 내가 할 수 있는 모든 방법을 시도해 볼 때까지 포기하지만 말자.