From 84de16028dc786cfa133a8b64e4be8fa14c03398 Mon Sep 17 00:00:00 2001 From: Joey Krabacher Date: Wed, 9 Feb 2022 04:35:11 -0600 Subject: [PATCH] HADOOP-18114. Documentation correction in assumed_roles.md (#3949) Fixes typo in hadoop-aws/assumed_roles.md Contributed by Joey Krabacher Change-Id: I2b77bd7793ae0433196b77042d5f400d0bcbe745 --- .../src/site/markdown/tools/hadoop-aws/assumed_roles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/assumed_roles.md b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/assumed_roles.md index 45170fc339e..094ea5668c0 100644 --- a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/assumed_roles.md +++ b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/assumed_roles.md @@ -80,7 +80,7 @@ and for background refreshes, a different credential provider must be created, one which uses long-lived credentials (secret keys, environment variables). Short lived credentials (e.g other session tokens, EC2 instance credentials) cannot be used. -A list of providers can be set in `s.s3a.assumed.role.credentials.provider`; +A list of providers can be set in `fs.s3a.assumed.role.credentials.provider`; if unset the standard `BasicAWSCredentialsProvider` credential provider is used, which uses `fs.s3a.access.key` and `fs.s3a.secret.key`.