KITE-938 added experimental support for the s3n and s3a S3 protocols. However, the registered URI patterns for the protocols are substantially different; the patterns for s3a are missing a "/*path" part that is included for the s3n patterns. This part seems to be necessary because a bucket name is a required component of the URI, in the host position. Without it, an "Unknown repository URI pattern" IllegalArgumentException is thrown. After adding in this missing pattern part to the kite-data-s3 Loader I was successfully able to create a dataset with s3a.