big-data/hadoop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HADOOP-16758. Refine testing.md to tell user better how to use auth-keys.xml (#1753)

Browse Source 
Contributed by Mingliang Liu
This commit is contained in:
Mingliang Liu 2019-12-11 11:52:53 -08:00 committed by GitHub
parent c174d50b30
commit b56c08b2b7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/testing.md
View File

@ -151,8 +151,9 @@ Example:
For S3a encryption tests to run correctly, the
`fs.s3a.server-side-encryption.key` must be configured in the s3a contract xml
file with a AWS KMS encryption key arn as this value is different for each AWS
KMS.
file or `auth-keys.xml` file with a AWS KMS encryption key arn as this value is
different for each AWS KMS. Please note this KMS key should be created in the
same region as your S3 bucket. Otherwise, you may get `KMS.NotFoundException`.
Example:
@ -1078,7 +1079,7 @@ mvn -T 1C verify -Dtest=skip -Dit.test=ITestS3AMiscOperations -Ds3guard -Ddynamo
### Notes
1. If the `s3guard` profile is not set, then the S3Guard properties are those
of the test configuration set in `contract-test-options.xml` or `auth-keys.xml`
of the test configuration set in s3a contract xml file or `auth-keys.xml`
If the `s3guard` profile *is* set:
1. The S3Guard options from maven (the dynamo and authoritative flags)