Configure authentication against a System Manager

Edit online

The CSO API supports AWS Signature v2 and v4 Authentication on a System Manager.

The AWS Signature v4 signing specification describes how to add authentication information to S3 requests.

Requests that use AWS authentication must be signed by using the requesting user's the Access Key ID and Secret Access Key, collectively known as Access Credentials.

The AWS Credentials file and Boto SDK configuration file can contain one or more named set of Access Credentials, called named profiles. These files always have one set of Access Credentials, which are identified as the [default] profile.

The order of precedence for Access Credentials is:
  1. Credentials passed as Boto constructor parameters
  2. Credentials set as environment variables
  3. Credentials set in the shared credentials file
    1. Named profile
    2. Default profile
  4. Credentials set in the Boto SDK configuration file
    1. Named profile
    2. Default profile