From Jesus in AWSFNDN-25

Commit merged in master

Hello jlegendre, I think we need to update our documentation. This ticket allows using the aws-s3-connector without using the credentials of our Password app. To do so, it is needed to add the following properties into the magnolia.properties file:

magnolia.aws.validateCredentials=false
magnolia.aws.useCredentials=false

Then, for setting the credentials, we have to follow the instructions of https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html

1. Environment variables–AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. The AWS SDK for Java uses the EnvironmentVariableCredentialsProvider class to load these credentials.

1. Java system properties–aws.accessKeyId and aws.secretKey. The AWS SDK for Java uses the SystemPropertiesCredentialsProvider to load these credentials.

1. Web Identity Token credentials from the environment or container.

1. The default credential profiles file– typically located at ~/.aws/credentials (location can vary per platform), and shared by many of the AWS SDKs and by the AWS CLI. The AWS SDK for Java uses the ProfileCredentialsProvider to load these credentials.

You can create a credentials file by using the aws configure command provided by the AWS CLI, or you can create it by editing the file with a text editor. For information about the credentials file format, see AWS Credentials File Format.

1. Amazon ECS container credentials– loaded from the Amazon ECS if the environment variable AWS_CONTAINER_CREDENTIALS_RELATIVE_URI is set. The AWS SDK for Java uses theContainerCredentialsProvider to load these credentials. You can specify the IP address for this value.

1. Instance profile credentials– used on EC2 instances, and delivered through the Amazon EC2 metadata service. The AWS SDK for Java uses the InstanceProfileCredentialsProvider to load these credentials. You can specify the IP address for this value.