How to configure Elastic Beanstalk to handle HTTPS requests from Amplify app?

Hello, If you are trying to deploy your application through Elastic Beanstalk and facing the above issues then it might be the issue with the instance health issue. I think your are getting warning issue in Elastic beanstalk is with instance. so once check all following steps which can resolve your issue:

1. Check SSL Certificate Configuration: Ensure that you've configured the SSL certificate correctly in the Elastic Beanstalk environment settings. Double-check that you've selected the correct SSL certificate and that it's properly configured for your domain.

2. Health Check Configuration: Review the health check configuration for your Elastic Load Balancer (ELB). Ensure that the health check settings are appropriate for your backend Node.js application. You may need to adjust the health check URL, timeout, or other parameters to ensure accurate health checks.

3. Security Group Configuration: Verify that the security group associated with your Elastic Beanstalk environment allows inbound traffic on port 443. If the security group is not configured correctly, it may block HTTPS traffic.

4. Check Elastic Beanstalk Logs: Review the logs for your Elastic Beanstalk environment to identify any errors or issues. Look for any messages related to SSL configuration, health checks, or instances failing to send data. The logs can provide valuable insights into the root cause of the problem.

5. Inspect Instance Health: Check the health status of your Elastic Beanstalk instances. If instances are failing health checks, investigate the reasons for the failures. Look for any errors or issues that may be preventing the instances from handling HTTPS traffic correctly.

6. Review Elastic Beanstalk Configuration: Double-check your Elastic Beanstalk configuration to ensure that all settings related to HTTPS and SSL are correct. Pay attention to any warnings or error messages that may indicate misconfigurations or issues.

7. Monitor ELB Metrics: Monitor the metrics for your Elastic Load Balancer in the AWS Management Console. Look for any anomalies or patterns that may indicate problems with HTTPS traffic handling or instance health.

**But your are telling that your are following AWS Documentation, So once make sure you have double-checked everything and nothing is missed. **

1. Provision an SSL Certificate: Use AWS Certificate Manager (ACM) or import a certificate into ACM to obtain an SSL certificate for your domain.

2. Configure the Load Balancer: In the Elastic Beanstalk console, navigate to your environment and select "Configuration." Under "Load Balancer," click "Edit" and enable HTTPS. Select the SSL certificate you obtained in step 1. Optionally, you can configure a security policy, cipher preference, and SSL redirection behavior.

3. Update Security Group Rules: Ensure that the security group associated with your Elastic Beanstalk environment allows inbound traffic on port 443 (HTTPS).

4. Update Route 53 DNS Settings: If you're using a custom domain, update your Route 53 DNS settings to point to the Elastic Load Balancer's DNS name.

5. Test Your Configuration: Access your application using the custom domain over HTTPS to ensure that the SSL certificate is valid and the connection is secure.