Prerequisites
Last updated
Was this helpful?
Last updated
Was this helpful?
Hopscotch CLI is written for on MacOS. Usage with different shells or UNIX-like OSs might result in misbehavior. This software relies on non-standard commandline tools (e.g. jq
, httpie
) that are automatically installed if missing using the brew
package manager.
Hopscotch CLI does not require root privileges; this software comes as-is and should not be run as superuser.
Before the installation, you will need a working installation of the AWS CLI with a valid access key. Install the AWS CLI by running
Log in to the with the user that has been set up for you; the account alias is hopscotch-labs
.
Use the drop-down menu next to you user name and select Security Credentials.
If this is your first login, you will need to replace your temporary password.
You must set up MFA. All your user privileges are dependent on MFA being enabled. Without MFA enabled, the only action your user is allowed to perform is enabling MFA. Before you proceed to the next step, if you did not use MFA for your current login session (because you just set it up), you will have to log out of the AWS console and back in.
You can now create programmatic access keys for AWS CLI. In the Security Credentials page, select Create access keys. Select the CLI and accept the warning to create a new access key.
Hopscotch AWS user passwords expire every 30 days!
If you already use the AWS CLI and have already configured an access key, Hopscotch CLI support setting a profile for AWS commands issued by the CLI. Toggle the tab below to view next steps based on your situation.
With the created Access Key and Secret Key, open your terminal again and type
then paste in the Access Key ID and Secret Key that you just created. Use eu-west-1
as the region and json
as the output format.
You can check your setup by running
Hopscotch AWS access keys are rotated monthly! Repeat this process when your access key is deactivated.