matiasvallejosdev
commented
7 months ago Introduction
There are multiple errors in my project that I solved:
Issue 1: Set 'Enhanced Health' Active for Your Environment
To address the issue you've encountered with the environment health remaining at "Yellow" status even after an update has finished, it's important to enable and utilize the Enhanced Health Monitoring feature in your AWS Elastic Beanstalk environment. This feature provides detailed health insights, making it easier to diagnose and solve problems.
Issue 2: Service Role for Elastic Beanstalk doesn't have sufficient permissions or it is not created.
When you launch an environment in the Elastic Beanstalk console or CLI, it creates a default service role named aws-elasticbeanstalk-service-role and attaches managed policies with default permissions to this service role. Take a look at the following stack overflow solution:
Issue 3: Instance Role for EC2 doesn't have sufficient permissions or it is not created.
You can then assign the EC2 instance profile to the new environments that you create. Take a look at the following stack overflow solution:
If your AWS account doesn’t have an EC2 instance profile, you must create one using the IAM service
Issue 4: VPC and Security Groups Rules
Ensuring your VPC's Internet Gateway and Route Tables are properly configured is crucial for connectivity issues. Here’s a simplified guide on how to set up and verify these components within your VPC for your Elastic Beanstalk environment:
- Step 1: Verify or Attach an Internet Gateway
- Step 2: Configure Route Tables
- Step 3: Associate Route Tables
- Step 4: Review Security Groups and Network ACLs
Following these steps ensures that your AWS Elastic Beanstalk environment's underlying network infrastructure is configured to support external connectivity, which is crucial for applications that need to communicate with the internet or be accessible from it.
No existing bucket name given, creating/requesting storage location Uploading file to bucket elasticbeanstalk-us-east-2-680662318279 New build successfully uploaded to S3, bucket=elasticbeanstalk-us-east-2-680662318279, key=/cicddotnetawsbeanstalk/8768762217.zip Created new application version 8768762217 in Beanstalk. Starting deployment of version 8768762217 to environment cicddotnetawsbeanstalk-dev Deployment started, "wait_for_deployment" was true...
00:26:54 INFO: Environment update is starting. 00:26:58 INFO: Deploying new version to instance(s). 00:27:03 INFO: New application version was deployed to running EC2 instances. 00:27:03 INFO: Environment update completed successfully. Deployment finished. Version updated to 8768762217 Status for cicddotnetawsbeanstalk-cicddotnetawsbeanstalk-dev is Ready, Health: Yellow, HealthStatus: Warning Warning: Environment update finished, but health is Yellow and health status is Warning. Giving it 120 seconds to recover... Warning: Environment still has health: Yellow and health status Warning. Waiting 109 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 99 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 88 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 78 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 68 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 57 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 47 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 36 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 26 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 16 more seconds before failing... Warning: Environment still has health: Yellow and health status Warning. Waiting 5 more seconds before failing... Error: Deployment failed: Error: Environment still has health Yellow 120 seconds after update finished!