This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-14
Channels
- # aleph (3)
- # announcements (16)
- # aws (6)
- # babashka (10)
- # beginners (28)
- # cider (1)
- # clj-kondo (14)
- # cljdoc (2)
- # cljs-dev (27)
- # cljsrn (7)
- # clojure (78)
- # clojure-europe (2)
- # clojurescript (14)
- # conjure (6)
- # core-async (2)
- # fulcro (5)
- # helix (7)
- # jobs (1)
- # lgbtq (1)
- # malli (12)
- # missionary (1)
- # nbb (10)
- # pathom (1)
- # portal (12)
- # protojure (1)
- # re-frame (41)
- # react (2)
- # reitit (1)
- # reveal (1)
- # shadow-cljs (72)
- # sql (11)
- # tools-deps (8)
- # vim (1)
- # xtdb (4)
I can use instance profiles so that, for example, the aws-api library wont need to be passed credentials because it uses this chain to check for credentials https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html Does anyone know if there's a way to use the aws CLI tools like this, avoiding explicitly passing credentials to the instance?
Seems possible https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-metadata.html
I thought that aws cli would automatically pick up the EC2 metadata server, if present, but seems there's credential_source = Ec2InstanceMetadata
option:
[profile profilename]
role_arn = arn:aws:iam::123456789012:role/rolename
credential_source = Ec2InstanceMetadata
region = region