anchor.diff:  3. Create a named profile in the AWS credentials file and set the environment variable `AWS_PROFILE` with its name.
   4. Amazon ECS container and instance profile credentials should also work, but have not been tested.
   
  -For more information, most of the advice in http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html[this AWS document] describes how credentials are located. Note however that the Java system properties options will NOT work with the clojure scripts (but would work if using the tools.deps.alpha library directly).
  +For more information, most of the advice in http://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html[this AWS document] describes how credentials are located. Note however that the Java system properties options will NOT work with the command line tools (but would work if using the tools.deps.alpha library directly).
   
   === Usage
   
  
positive.code: * `clojure [dep-opt*] [init-opt*] [main-opt] [arg*]`
  * `clj     [dep-opt*] [init-opt*] [main-opt] [arg*]`
  
  The clojure script is a runner for Clojure. clj is a wrapper for interactive repl use. These scripts ultimately construct and invoke a command-line of the form:
  
  `java [java-opt*] -cp classpath clojure.main [init-opt*] [main-opt] [arg*]`
  
  
negative.code: }
  ----
  
  The tools also provide support for connecting to private S3 Maven repositories (thanks to the https://github.com/s3-wagon-private/s3-wagon-private[s3-wagon-private] and https://github.com/spring-projects/aws-maven[aws-wagon] projects).
  
  Add a `:mvn/repos` that includes the s3 repository root:
  
  