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.
Note
Acquia supports only RSA user keys.
To add a public key to your account:
On your local computer, use one of the following methods to copy your SSH public key file to the clipboard:
Using a command: Open a command prompt, and then run one of the following commands (based on your operating system):
Using 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.
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.
Note
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.
Using your public key
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:
You are a member of a team assigned to the infrastructure’s application, and you have a role that includes the appropriate SSH permissions.
You are either the Owner or Administrator for the application.
Acquia provides the following permissions related to SSH keys:
Add SSH key to Git repository
Add SSH key to non-Production environments
Add SSH key to the Production environment
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.
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.
Note
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.
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.
Note
Acquia supports only RSA user keys.
To add a public key to your account:
On your local computer, use one of the following methods to copy your SSH public key file to the clipboard:
Using a command: Open a command prompt, and then run one of the following commands (based on your operating system):
Using 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.
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.
Note
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.
Using your public key
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:
You are a member of a team assigned to the infrastructure’s application, and you have a role that includes the appropriate SSH permissions.
You are either the Owner or Administrator for the application.
Acquia provides the following permissions related to SSH keys:
Add SSH key to Git repository
Add SSH key to non-Production environments
Add SSH key to the Production environment
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.
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.
Note
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.
Cloud Platform