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

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?

1 answer

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

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,762 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you