prakhar1989/docker-curriculum

AWS deployment for a single container shows Severe Health Status

Open

#311 opened on Oct 23, 2021

View on GitHub
 (1 comment) (3 reactions) (0 assignees)CSS (4,274 stars) (1,686 forks)batch import
aws-ecshelp wantedquestion

Description

Hi, I have an issue with AWS deployment for a single container that shows Severe Health Status. I followed one to one the instruction, but once I uploaded the aws.json file, the AWS server didn't start. I am new to AWS deployment and couldn't find any log file to understand the error exactly. All GUI messages are not descriptive enough. I need to install EB CLI to retrieve the log files. Could you navigate me what exactly I need to do and to look for to understand the issue? The flask app is so simple, and it runs locally. The aws.json file is correct and the same as in the instruction. I have no idea what is wrong with AWS. It is frustrating to get errors on such a simple example. Thanks

Contributor guide

Tech stack
pythonflaskdockeraws
Domain
clouddevops
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Docker basicsAWS accountElastic Beanstalk
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The user is experiencing a severe health status on AWS Elastic Beanstalk. They need to retrieve the EB CLI logs to diagnose the issue. Review the repository's deployment documentation for any troubleshooting steps. Check if any maintainer comments or linked fixes exist for similar issues. The aws.json file should be examined for correct configuration.