Connecting EC2 with Bitbucket works, but ssh-agent identity doesn't "stick"

Sergiu Poenaru

Steps taken so far:

Login EC2
Sudo su -
ssh-keygen -t rsa
eval ssh-agent -s
ssh-add mybitbucket.pub
copy the key in BitBucket's web interface.

Works fine, however if I close the terminal and log again into my EC2 instance, the ssh-agent is dead:

[ec2-user@ip-10-0-1-112 .ssh]$ ssh-add -l
Could not open a connection to your authentication agent.

Therefore I have to do eval ssh-agent -s and ssh-add mybitbucket.pub every single time I want to do git operations with the remote bitbucket.

Anybody had a similar issue?

Sergiu Poenaru

Leaving this solution from SO for anyone that scratched its head with the same issue:

http://stackoverflow.com/questions/43968867/ec2-ssh-add-identity-doesnt-stick