Cloud Platform
Adding a public key to an Acquia profile
With Copilot
Acquia Copilot is a conversational AI connected into our product documentation and knowledge base. Ask Copilot about product features, technical details, troubleshooting and how to get started with Acquia products.
To connect to Cloud Platform environments using SSH, you must have an SSH public key added to your Acquia profile. If you have the proper role and permissions as a member of a team, you can also use your public key to SSH to environments of applications to which your team is assigned. You can also use your public key to access your Cloud Platform environments using SFTP or rsync, or your Git repository.
If you do not already have an SSH key pair, you can create a new public key. Your SSH public key must be at least 4,096 bits in size.
Acquia supports only RSA user keys.
To add a public key to your account:
pbcopy < ~/.ssh/id_rsa.pubsudo apt-get install xclip xclip -sel clip < ~/.ssh/id_rsa.pubclip < ~/.ssh/id_rsa.pubUsing a text editor: In a text editor, open your SSH public key file, and then copy the contents of the file to the clipboard. Be sure not to add any extra lines or spaces to the copied key.
By default, the file name is ~/.ssh/id_rsa.pub.
Click SSH Keys.
Cloud Platform displays your account’s SSH Keys page.
In Public Key, paste the OpenSSH-formatted key. OpenSSH public keys start with ssh-rsa, and appear similar to the following example:
ssh-rsa AAAAG1bB0us3MAAACBALFF6+dpSkO6bwbJ6BCCwbGavQPqR3JSwGWW== user@hostnameClick Add Key.
You’ll receive an email informing that a key is added to your account. The email will have a subject line similar to the following:
Acquia: An SSH key labeled [labelname] was added to your Acquia account.If you get a 'Permission Denied (publickey)' error while cloning a repository, check that your user role in Cloud Platform has correct permissions for using SSH. Without appropriate permissions, you cannot utilize SSH. Verify your public key settings and ensure that they are correctly configured to resolve the issue.
After you add a key, there might be a delay of approximately one minute before you can use the key to connect to your environments or repository.
With your SSH public key added to your profile, you can use the key to access a Cloud Platform environment if you meet one of the following requirements:
Acquia provides the following permissions related to SSH keys:
If you have only the Add SSH key to git repository and Add SSH key to non-Production environments permissions, you can check code in and out of your application’s Git repository, and use SSH to connect to your application’s Development and Staging environments; however, you can’t connect to your application’s Production environment using SSH.
To learn more about teams and permissions in Cloud Platform see Managing users, teams, roles, and permissions.
Cloud Platform does not support the use of deployment keys (machine keys) that are not associated with an individual user account. All SSH keys must be associated with a user account.
Acquia recommends you create a new user account (in addition to the user accounts of your team members) to store the SSH keys that grant your third-party deployment systems (such as Travis or Jenkins) push access to Cloud Platform. Assign this user account a role that includes the Deploy code, files, or databases to the production environment permission, and then add the SSH public key to the new user account’s profile.
Creating a separate account for your deployment keys protects your subscription from unexpected deployment failures if an employee leaves your organization and is removed from your Cloud Platform subscription.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Sign in to use Acquia Copilot
Sign in and try Copilot
Acquia copilot is a chat AI connected to our knowledge base and product documentation.
Get answers to your questions complete with references to our product documentation.
To connect to Cloud Platform environments using SSH, you must have an SSH public key added to your Acquia profile. If you have the proper role and permissions as a member of a team, you can also use your public key to SSH to environments of applications to which your team is assigned. You can also use your public key to access your Cloud Platform environments using SFTP or rsync, or your Git repository.
If you do not already have an SSH key pair, you can create a new public key. Your SSH public key must be at least 4,096 bits in size.
Acquia supports only RSA user keys.
To add a public key to your account:
pbcopy < ~/.ssh/id_rsa.pubsudo apt-get install xclip xclip -sel clip < ~/.ssh/id_rsa.pubclip < ~/.ssh/id_rsa.pubUsing a text editor: In a text editor, open your SSH public key file, and then copy the contents of the file to the clipboard. Be sure not to add any extra lines or spaces to the copied key.
By default, the file name is ~/.ssh/id_rsa.pub.
Click SSH Keys.
Cloud Platform displays your account’s SSH Keys page.
In Public Key, paste the OpenSSH-formatted key. OpenSSH public keys start with ssh-rsa, and appear similar to the following example:
ssh-rsa AAAAG1bB0us3MAAACBALFF6+dpSkO6bwbJ6BCCwbGavQPqR3JSwGWW== user@hostnameClick Add Key.
You’ll receive an email informing that a key is added to your account. The email will have a subject line similar to the following:
Acquia: An SSH key labeled [labelname] was added to your Acquia account.If you get a 'Permission Denied (publickey)' error while cloning a repository, check that your user role in Cloud Platform has correct permissions for using SSH. Without appropriate permissions, you cannot utilize SSH. Verify your public key settings and ensure that they are correctly configured to resolve the issue.
After you add a key, there might be a delay of approximately one minute before you can use the key to connect to your environments or repository.
With your SSH public key added to your profile, you can use the key to access a Cloud Platform environment if you meet one of the following requirements:
Acquia provides the following permissions related to SSH keys:
If you have only the Add SSH key to git repository and Add SSH key to non-Production environments permissions, you can check code in and out of your application’s Git repository, and use SSH to connect to your application’s Development and Staging environments; however, you can’t connect to your application’s Production environment using SSH.
To learn more about teams and permissions in Cloud Platform see Managing users, teams, roles, and permissions.
Cloud Platform does not support the use of deployment keys (machine keys) that are not associated with an individual user account. All SSH keys must be associated with a user account.
Acquia recommends you create a new user account (in addition to the user accounts of your team members) to store the SSH keys that grant your third-party deployment systems (such as Travis or Jenkins) push access to Cloud Platform. Assign this user account a role that includes the Deploy code, files, or databases to the production environment permission, and then add the SSH public key to the new user account’s profile.
Creating a separate account for your deployment keys protects your subscription from unexpected deployment failures if an employee leaves your organization and is removed from your Cloud Platform subscription.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Cloud Platform