Elastic Beanstalk not loading on other's computer.

Since the flask app deployed on Elastic Beanstalk is loading fine when accessed from your own computer but not loading on other computers, there are a few potential reasons for this issue:

1. Check the security group settings associated with your Elastic Beanstalk environment. Ensure that the security group allows inbound traffic on the port your Flask app is listening on (usually port 80 for HTTP or port 443 for HTTPS).
2. If you are using network ACLs in your VPC, make sure they are configured to allow inbound and outbound traffic to and from your Elastic Beanstalk environment.
3. Verify that your Elastic Beanstalk environment is deployed in a subnet with internet access (public subnet). If it's deployed in a private subnet, you'll need to configure a NAT gateway or NAT instance to allow outbound internet access.
4. Ensure that the DNS records for your domain name (if you're using a custom domain) are correctly configured to point to the Elastic Beanstalk environment's endpoint.
5. Check the health of the EC2 instances running your Elastic Beanstalk environment. If the instances are unhealthy or terminated, it could cause the application to be inaccessible.
6. If the users accessing the application from other computers are behind a proxy or firewall, it may be blocking access to the Elastic Beanstalk environment. Verify that the proxy or firewall settings allow access to the required ports and domains.
7. Load Balancer Configuration: If your Elastic Beanstalk environment is using a load balancer, ensure that the load balancer's listeners are correctly configured to route traffic to the instances.
8. Application Configuration: Review your Flask application's configuration to ensure that it's not restricting access based on IP addresses or other criteria.
9. By checking these potential issues, you should be able to diagnose and resolve the issue with your Flask app not loading on other computers when accessed from the Elastic Beanstalk environment.

Lastly consider reviewing the Elastic Beanstalk logs for any errors or contacting AWS support for further assistance with the detailed logs

Hope it clarifies and if does I would appreciate answer to be accepted so that community can benefit for clarity, thanks ;)