Someone has already added that SSH key.
Asked by Niklas Brunberg:

I think it was an old account which I deleted this summer. Why is it still blocking me from adding my SSH key?


Answers:
author: Patrik S
body: Hello [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559) and welcome to the Community!

After an account is deleted, it might take up to 30 days for the data to be fully removed from all Atlassian services, as per stated in [our documentation](https://support.atlassian.com/bitbucket-cloud/docs/delete-an-account/) :
> After you delete your account, personal and billing data associated with the account will be also deleted from all Atlassian services accessed by your account within 30 days, unless we're required to keep it for legitimate business or legal purposes.

Hence, the SSH keys that were added to the deleted account may take up to 30 days to be removed.

In this case, it's recommended to create a new unique SSH key following the instructions outlined in the article [Configure SSH \| Bitbucket Cloud](https://support.atlassian.com/bitbucket-cloud/docs/configure-ssh-and-two-step-verification/) and use it in replacement of the old key.

Thank you, [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559) !

Patrik S

comments: author: Niklas Brunberg
body: Thank you.

What I don't understand is why the information/data is still \*active\*. I understand a certain delay is needed for various technical and organisational reasons. But why would you still treat the SSH keys as active during this period?


author: Patrik S
body: Hey [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559) ,

The removal of the SSH key can take up to 30 days to be completed, just like all the other data associated with your account. This is the standard time frame for the complete removal of data related to deleted accounts. The deletion process is designed to ensure all your data is securely erased, and this includes your SSH key.

However, I understand that waiting for this process can be inconvenient, so for an immediate solution you have the option to create a new unique SSH key and start using the new one. I comprehend that setting up a new SSH key might be an extra step, but it could be a suitable solution if you need to keep your work moving forward.

In future deletions, if you prefer not to create a new key and wish to re-use your existing key before the 30-day period, you will first need to manually remove the SSH key before deleting the account/workspace or repository where the key was originally added.

Thank you, [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559) .

Patrik S


author: Niklas Brunberg
body: I don't think I was clear enough in my question sorry. The delay in deletion I understand. The fact that it is still active I don't. Why is it still in use?


author: Patrik S
body: Hey [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559) ,

The key is not actually in use, but it still exists in the resource you have deleted that is still in a "deleting state". When adding an SSH key, Bitbucket validates if the key is not already being used in another resource to not cause conflicts in the system, and the resources in the "deleting" state are also counted against that validation.

Thank you, [@Niklas Brunberg](/t5/user/viewprofilepage/user-id/5294559)   
Patrik S


Tags: bitbucket-cloud

cloud