Succesful deployment on Windows server but still can't access app

0

After creating a pipeline with CodePipeline with all the attendant resources (CodeCommit, CodeDeploy, EC2, IAM Roles, etc.), my pipeline has run successfully but I still can't access my EC2 instance online ("This site can't be reached error").

My code is very simple, I just want to run a starter app to learn how to use the pipeline; in fact, I'm using the SampleApp_Windows structure downloaded from this Github repo https://github.com/quangit/aws-codedeploy-samples-master/tree/master/applications. I didn't change anything in the code and my pipeline is showing success in all of the stages. But when I try to access the EC2 instance via the public DNS address provided, nothing happens.

I've already gone through the process of successfully deploying the SampleApp_Linux from the same Github repository and was able to access the app there (and since I'm using the same security group on my new Windows instance I don't think it's a firewall issue), so I really don't know what the issue could be other than there's something about how a Windows server works with CodePipeline that I don't know.

Any ideas would be appreciated!

asked a year ago231 views
1 Answer
0

When everything looks like it's working there's always an easy answer: launching the instance from the console using the public DNS address seems to always adds an https:// out front (even when you can't see it), but forcing that to be http:// let everything work! So, the moral of the story is to always check the protocol.

answered a year ago

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