Answers: <p>If you want to make it private either you need to setup a vpn so that you can access jenkins gui using <a href="http://private-subnet-ip:jenkins_port" rel="nofollow noreferrer">http://private-subnet-ip:jenkins_port</a> or you can move jenkins behind a load balancer and use load-balancer-dns to access jenkins gui. If it is in public subnet then use NACL/Security Groups to restrict access only to trusted sources. For more security, do not assign public ip to jenkins machine, assign dns hostname(even to load balancer you should do that) and implement ssl over http so that it can be accessed over https only. </p>
  
Answers: CC BY-SA 4.0
Answers: 2019-02-07T04:14:56.233Z
Answers: 2019-02-07T05:51:58.423Z
Answers: 2019-02-07T05:51:58.423Z
Answers: deosha
Answers: <p>If in the same VPC the can talk to each other. If you are doing that from a public host "outside" the VPC then you need either allow the IP or connect from bastion host. </p>
  
  <ul>
  <li>You may need to explain more about your issue.</li>
  </ul>
  
Answers: CC BY-SA 4.0
Answers: 2019-01-04T12:04:57.070Z
Answers: 2019-01-04T12:04:57.070Z
Answers: lORD
Answers: <p>You can also install docker and configure jenkins in that. so you can create and configure multi-nodes on that and it will consume time.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-02-07T08:53:19.127Z
Answers: 2019-02-07T08:53:19.127Z
Answers: Jenish Patel
Body: <p>For development environment, to be used by multiple developers, we have a pipeline to be created with Git-Jenkins-Tomcat(dev)
  Do I need to place jenkins in private subnet and access thru bastion host?</p>
  
Tags: <jenkins><jenkins-pipeline><build-pipeline><aws-vpc>
Title: Jenkins in private subnet
UserDisplayName: overexchange
ThreadText: # Jenkins in private subnet
  
  (Asked by: username_0 on 2019-01-04)
  
  For development environment, to be used by multiple developers, we have a pipeline to be created with Git-Jenkins-Tomcat(dev)
  Do I need to place jenkins in private subnet and access thru bastion host?
  
  **Tags:** jenkins, jenkins-pipeline, build-pipeline, aws-vpc
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_1 on 2019-02-07. Score: 1
  
  If you want to make it private either you need to setup a vpn so that you can access jenkins gui using <http://private-subnet-ip:jenkins_port> or you can move jenkins behind a load balancer and use load-balancer-dns to access jenkins gui. If it is in public subnet then use NACL/Security Groups to restrict access only to trusted sources. For more security, do not assign public ip to jenkins machine, assign dns hostname(even to load balancer you should do that) and implement ssl over http so that it can be accessed over https only.
  
  
  ---
  
  ### Answer by username_2 on 2019-01-04. Score: 0
  
  If in the same VPC the can talk to each other. If you are doing that from a public host "outside" the VPC then you need either allow the IP or connect from bastion host.
  
  * You may need to explain more about your issue.
  
  
  ---
  
  ### Answer by username_3 on 2019-02-07. Score: 0
  
  You can also install docker and configure jenkins in that. so you can create and configure multi-nodes on that and it will consume time.
  
  
  ---
  
  