                                                 ┃┠──────────────────┼─────────────────────────────────────────────────────────────────────┨

┃ SHARED           │ ➖                                                                  ┃

┠──────────────────┼─────────────────────────────────────────────────────────────────────┨

┃ CREATED_AT       │ 2023-06-19 18:12:42.066053                                          ┃

┠──────────────────┼─────────────────────────────────────────────────────────────────────┨

┃ UPDATED_AT       │ 2023-06-19 18:12:42.066055                                          ┃

┗━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

Configuration

┏━━━━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━┓

┃ PROPERTY              │ VALUE     ┃

┠───────────────────────┼───────────┨

┃ region                │ us-east-1 ┃

┠───────────────────────┼───────────┨

┃ aws_access_key_id     │ [HIDDEN]  ┃

┠───────────────────────┼───────────┨

┃ aws_secret_access_key │ [HIDDEN]  ┃

┗━━━━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━┛

AWS Secret Key

Long-lived AWS credentials consisting of an AWS access key ID and secret access key associated with an AWS IAM user or AWS account root user (not recommended).

This method is preferred during development and testing due to its simplicity and ease of use. It is not recommended as a direct authentication method for production use cases because the clients have direct access to long-lived credentials and are granted the full set of permissions of the IAM user or AWS account root user associated with the credentials. For production, it is recommended to use the AWS IAM Role, AWS Session Token, or AWS Federation Token authentication method instead.

An AWS region is required and the connector may only be used to access AWS resources in the specified region.

If you already have the local AWS CLI set up with these credentials, they will be automatically picked up when auto-configuration is used (see the example below).