Hello, I'm trying to use the ec2-plugin to launch ec2 slaves, but am failing when it comes to adding EC2 Key Pair's Private Key.I add the private key, and when I press the "Test Connection" button, I get the error "The EC2 key pair private key isn't registered to this EC2 region (fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:ff:9c:1b)". AFAICT, I've set everything up correctly.
Can someone help me figure out what's going wrong? I'm fairly new to Jenkins. Is there perhaps a way to turn up debug logging so I can see more of what's happening? Perhaps what API calls it's making to EC2? Thanks in advance. Details are below. kallen I created a keypair in ec2 called "build-automation" in my us-east-1 ec2 account. I created the ssh key like so: ssh-keygen -N "" -C build-automation -f .ssh/build-automation I then imported the public portion of the key via the AWS console in my account. In jenkins, I create an ec2 cloud, I add the access key ID and secret access key. Then I add the private key of the ssh keypair, as mentioned above. After testing connection (which tests the ssh keypair, right?) I get an error saying the key isn't registered to this EC2 region, fingerprint xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:ff:9c:1b. I don't even recognize that fingerprint. But maybe I don't understand what the fingerprints are telling me. The fingerprints as I see them: $ ssh-keygen -l -f sysadmin 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:3c:24 sysadmin.pub (RSA) $ ssh-keygen -l -f build-automation 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:bd:45:fb build-automation.pub (RSA) $ ec2-describe-keypairs -K $AWS_x509_KEY -C $AWS_x509_CERT KEYPAIR build-automation xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:33:e3:a0 KEYPAIR sysadmin xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:8d:bc:32 The fingerprint as shown by the error message matches none of the fingerprints as seen by ec2-describe-keypairs or ssh-keygen -l. I don't get it... However, if instead of the build-automation private key, I add the sysadmin private key, "Test Connection" succeeds. And yet, both keypairs are indeed present in my ec2 account.
