[ARVADOS] updated: 2.1.0-2368-gbc4b186ae
Git user
git at public.arvados.org
Mon Apr 25 20:33:04 UTC 2022
Summary of changes:
doc/install/crunch2-cloud/install-dispatch-cloud.html.textile.liquid | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
via bc4b186aed4185fa84d65cf04745c80ee183c7f7 (commit)
from 7cb44353aa44c07cd8c6d87149b61f42aaf2bf17 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
commit bc4b186aed4185fa84d65cf04745c80ee183c7f7
Author: Ward Vandewege <ward at curii.com>
Date: Mon Apr 25 16:32:52 2022 -0400
19054: more doc changes.
Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>
diff --git a/doc/install/crunch2-cloud/install-dispatch-cloud.html.textile.liquid b/doc/install/crunch2-cloud/install-dispatch-cloud.html.textile.liquid
index 3efd49fd1..008779d97 100644
--- a/doc/install/crunch2-cloud/install-dispatch-cloud.html.textile.liquid
+++ b/doc/install/crunch2-cloud/install-dispatch-cloud.html.textile.liquid
@@ -101,7 +101,9 @@ When @Containers/LocalKeepBlobBuffersPerVCPU@ is non-zero, the compute node will
If the AWS credentials for S3 access are configured in @config.yml@ (i.e. @Volumes/DriverParameters/AccessKeyID@ and @Volumes/DriverParameters/SecretAccessKey@), these credentials will be made available to the local Keepstore on the compute node to access S3 directly and no further configuration is necessary.
-Alternatively, if an IAM role is configured in @config.yml@ (i.e. @Volumes/DriverParameters/IAMRole@), this role (or an equivalent role) needs be configured in the @CloudVMs/DriverParameters/IAMInstanceProfile@ parameter. That way, @arvados-dispatch-cloud@ can attach the appropriate instance profile to the compute node as it starts up and make the role available to the compute node.
+Alternatively, if an IAM role is configured in @config.yml@ (i.e. @Volumes/DriverParameters/IAMRole@), the name of the instance profile that corresponds to this role ("usually identical to the name of the IAM role":https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html#ec2-instance-profile) must be configured in the @CloudVMs/DriverParameters/IAMInstanceProfile@ parameter.
+
+Finally, if an IAM role is used by Keepstore but not configured in @Volumes/DriverParameters/IAMRole@, Keepstore will use the role attached to the node, whatever it may be called. The @CloudVMs/DriverParameters/IAMInstanceProfile@ parameter must then still be configured with the name of the appropriate role. That way, @arvados-dispatch-cloud@ can attach the appropriate instance profile to the compute node as it starts up and make the role available to the compute node.
h3. Minimal configuration example for Amazon EC2
-----------------------------------------------------------------------
hooks/post-receive
--
More information about the arvados-commits
mailing list