By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Environment deployed on Beanstalk not accessible

0

I created a browser game and deployed through Beanstalk. It was working fine in the beginning. I had to integrate it in my website that i created on Wix. For that i needed the https 'version' because I cannot embed a http website in Wix. I registered a domain for my wix website. Created a subdomain for my game and got certificate from AWS only for this subdomain so that i can get the https version.

For my environment now, i have two security groups and one of them has the other one as source in its inboud settings. I have made changes from http to https in the security groups but its not possible to change the source in one of them to 0.0.0.0/0. Its always the other security group. I have made the required modifications in listeners by adding https protocol, 443 port, the certificate from ACM. And now, i cannot access my environment. Neither through the subdomain of my website nor through EBL domain. Before i made these changes from http to https, i was able to access this from both the links. I have no idea what i am doing wrong.

PS: This might be irritating for the programmers here, but i have no programming knowledge per se. I installed and deployed everything with the help of chatgpt. So if you decide to help me with my problem, please treat me as programming virgin who doesn't know even the 'P' of programming.

Thank you in advance.

Topics
ComputeNetworking & Content Delivery
Tags
Website ProvisioningAWS Elastic BeanstalkElastic Load BalancingAmazon CloudFrontSecurity Group
Language
English
Zeus
asked 10 days ago294 views
1 Answer
0

The security group is just the firewall settings. You need to make sure your application (or its load balancer) is setup to handle https requests. AWS' documentation is pretty good for explaining it and how to set it up:

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html

JPurdy
answered 10 days ago
  • Zeus
    8 days ago

    Hey @JPurdy, thank you for your reply. Couldn't check it out earlier. Wife got sick and admitted in the hospital. Got time today so I tried figuring it out

    1. According to the document, im supposed to go to ‘Load Balancer’ from ‘configuration’ and then edit it. It also states that if I cannot edit my load balancer settings, it means that I don’t have a load balancer. So here are the problems: There is no category named ‘Load Balancer’ separately. There is a subcategory named ‘Load balancer type’ (it is greyed out. Cannot edit it) and ‘Listeners’ (that have one listener with port 80. Both these are found in ‘Configure instance traffic and scaling’ category.

    Does this mean I do not have a load balancer?

    Under this category only, the subcategory ‘Capacity’ has an option of selecting ‘environment type’ in which ‘load balanced’ is already selected.

    1. Under ‘listener’ subcategory, I can edit the already present listener, that has port 80 and HTTP protocol. But, the port section is grade out and cannot change it from 80 to 443 for HTTPS. If I try to add a new listener, it gets added but the system says that I already have a listener for the said environment. And I cannot delete it either. If I try to remove it or disable it i get an error saying that my environment is in an invalid state and it must be ready for this operation.

    So, any further help would be appreciated. Or would it be actually better if I terminate this environment and deploy it after rebuilding it from 0.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content