Java property aws.secretAccessKey vs aws.secretKey

## Driver version

2.1.0.17

## Redshift version

8.0.2

## Client Operating System

MacOS

## JAVA/JVM version

openjdk 11.0.18

## Problem description

1. Expected behaviour:

Documentation states that the Java Property names are **aws.accessKeyId aws.secretAccessKey** & **aws.sessionToken**

https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

4. Actual behaviour:

Fails to connect.

5. Error message/stack trace:

> com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: You must specify a value for roleArn and roleSessionName, com.amazonaws.auth.profile.ProfileCredentialsProvider@41f464f6: profile file cannot be null, com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@7239a287: Failed to connect to service endpoint:

6. Any other details that can be helpful:

Changing to aws.secretyKey (as stated in the error) is successful.

Start by reproducing the credential lookup with driver version 2.1.0.17 and compare the documented aws.secretAccessKey property with the error's aws.secretKey name. Check whether the driver accepts either spelling and update the relevant behavior or documentation so the documented property connects successfully.

Written by the indexing model from the issue text.