- Newest
- Most votes
- Most comments
Step 1 looks to be concerned with Cfn that provisions the resources. Have you completed step 2? It looks like Step 2 discusses how to access, unlock, and customize the Jenkins server.
Hi! Good question.
A couple things to verify from step 1:
- Where are you connecting to the Jenkins server from when you try to SSH?
- When you say route all traffic 0.0.0.0/0 to the Internet Gateway, are you referring to ingress (inbound) or egress (outbound)?
- Does the Jenkins server have the proper Security Group allowing ingress for both Web Traffic (from where you are going to access the Jenkins server) and SSH traffic?
- Is the Jenkins server properly setup in a public subnet as per the values provided here: https://third-party-integration-codebuild-codedeploy-plugins.workshop.aws/en/create.html? 172.31.32.0/20 is part of a Private Address space (RFC 1918).
In Step 2, to configure the Jenkins server, you will need to do the following:
- Try looking in /var/jenkins_home/secrets/initialAdminPassword as well for the password.
How do I configure the subnets properly? How would I modify this template to create a completely new VPC and proper subnets? blog-for-codedeploy.s3.eu-central-1.amazonaws.com/CodeDeployTemplate.json I'll try it again from scratch because I think that the subnets are not properly setup.
Do you have port 80 for http or port 443 for https open for the user you are using to access the server in your browser?
I accidently noticed yesterday while doing something else that Chrome by default tried to open the URL by HTTPS and HTTPS was not enabled in the Security Group so that's probably why it didn't work. I'll give it a try one more time. Appreciate your help.
Relevant content
- asked 10 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
No, I haven't completed step 2. When I try to look what's inside the /var/log/jenkins/jenkins.log file it says that the file doesn't exist.