For the most recent update on ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1), refer to the AWS Health Dashboard. For information on AWS Service migration, see How do I migrate my services to another region?
how to create a slave node with username and password ?
Hai AWS team, my self Jeevan Kalyan. I am learning AWS DevOps. I doubt that i.e., I created two instances in AWS console 1. Jenkins and 2nd is a slave instance and I connected these two servers with SSH-keygen. After that, I opened the Jenkins dashboard with public key and then I created a node in the manage Jenkins option in that node, I gave some information like node name, root directory, Number of executors, Launch method --- In the launch method, I select launch agent with SSH. After that I saved the node Once I created that node it was not connecting due to some errors.
Can u please help me to solve my problem?
Thanks in advance
- Newest
- Most votes
- Most comments
You need to login to the worker node (slave) as the user that Jenkins will connect via SSH. Then cd ~/.ssh and edit or create the authorized_keys file. In this file, place the Public Key for the ssh key that Jenkins will be connecting with.
Once you have done this, you can test the connection for the primary node to the worker.
Background documentation on SSH based auth. https://www.digitalocean.com/community/tutorials/how-to-configure-ssh-key-based-authentication-on-a-linux-server
Hope this helps!
thanks in advance
hi
Verify SSH Credentials:
Double-check the username and private key associated with the "ubuntu" credential in Jenkins. Ensure the private key has the correct permissions (usually 600). You can check with ls -l ~/.ssh/id_rsa (replace id_rsa if your key filename is different) on the slave and adjust permissions with chmod 600 ~/.ssh/id_rsa if needed. Consider using a more secure authentication method like key pairs instead of username/password.
Enable SSH Key Verification:
Highly Recommended: Change the sshHostKeyVerificationStrategy to a more secure option like hudson.plugins.sshslaves.verifiers.KnownHostsFileVerificationStrategy. This verifies the slave's SSH fingerprint against a known_hosts file on the master, ensuring you're connecting to the intended server. If you must stick with non-verification for now (not recommended for production): Be very cautious about potential security risks. Manually verify the slave's SSH fingerprint on the master using ssh-keyscan <slave_ip> and add it to the ~jenkins/.ssh/known_hosts file on the master.
Check Firewall Rules:
Ensure both the master's and slave's security groups allow SSH traffic (port 22) between them.
Test SSH Manually:
Try connecting to the slave from the master using a basic SSH command (e.g., ssh -i ~/.ssh/id_rsa ubuntu@172.31.17.124) to isolate the issue. If this works, the problem likely lies in the Jenkins slave configuration.
Review Jenkins Logs:
Check the Jenkins logs for more detailed error messages that might provide further clues.
https://medium.com/@aika.nazhimidinova/configure-jenkins-agents-4d44d9c17a62
Relevant content
- asked a year ago
- asked 4 years ago
- AWS OFFICIALUpdated a year ago
I would not recommend using password based authentication for SSH.
However, I would start with logging into the worker, and set a password for the user that Jenkins will be connecting with.
Then edit
/etc/ssh/sshd_configand change the line forPasswordAuthentication notoPasswordAuthentication yes.Restart SSH
sudo systemctl restart sshd.serviceand then retry the connection from Jenkins.