Setting up different credentials ( Profiles ) This should start an SSM session ( as long as you are able to access the same from the AWS Session manager without any issues ). If the instance is in the same region as the default, you may skip the -region section. Note that you can override the region here. We can access an instance using the instance-id of the instance from AWS. aws ssm start-session -target -region ap-southeast-1 Once the SSM plugin setup is done, we could access an instance using the below command format. The last step should give a response as below: Accessing an instance Run the below commands one by one for downloading and installing the session-manager plugin. Now that AWS CLI is set up, let’s install the plugin required for SSM access. Provide the default region ( where you have the servers.

Provide the access key and secret received in the previous step.

This will ask you for some details about the account for setting up the access. Once the installation is done, we need to do some basic configuration for the AWS CLI to connect to an account.ĪWS Access Key ID : AKIAIOSFODNN7EXAMPLEĪWS Secret Access Key : wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

This will provide you with an accessKey and access secret that you need to note down and provide during the AWS CLI configuration. You can go to your AWS account -> IAM -> Users -> Add User ( Choose programmatic access ) and enable the relevant access rights and create the user. This will provide you with the access key and access secret that are required for connecting the AWS CLI with your AWS account. AWS account with programmatic accessįor using the AWS CLI, you need to have a user account with programmatic access enabled in the AWS account. Once the installation is complete, you can run the below command from the terminal and it should give the details of the AWS CLI version. Go to the below link and follow the instruction for your respective platform. Load AWS CLI credentials and config file from a custom locationīefore we start the setup, it is necessary to have the AWS CLI installed and configured in the system where you are trying to access it.Define configuration for profile ( region, output etc ).Define multiple credentials ( profiles ).Setting up different credentials ( Profiles ).

Terminal session manager