From 4a1ede2e5526f1a6bbf404207f0f5f1dcc81f0e0 Mon Sep 17 00:00:00 2001 From: Juniper Hovey Date: Thu, 7 Dec 2023 10:43:33 -0600 Subject: [PATCH] Add documentation for IAM env var --- docs/site/pages/docs/authentication.mdx | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/site/pages/docs/authentication.mdx b/docs/site/pages/docs/authentication.mdx index d51e46b..ffabf6c 100644 --- a/docs/site/pages/docs/authentication.mdx +++ b/docs/site/pages/docs/authentication.mdx @@ -1,11 +1,10 @@ -import { Callout, Tabs, Tab } from 'nextra-theme-docs'; +import { Callout, Tabs, Tab } from "nextra-theme-docs"; # Authentication - Remember to never save your secrets in source control or any insecure - environment. Anybody who gets access to them could use them to steal your - accounts. + Remember to never save your secrets in source control or any insecure environment. Anybody who + gets access to them could use them to steal your accounts. ## Resource management @@ -112,6 +111,10 @@ The simplest method is to set the `MANTLE_AWS_ACCESS_KEY_ID` and `MANTLE_AWS_SEC variables. Mantle also supports the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` variables but recommends you scope your variables to Mantle to avoid conflicts with other tools. +If you're using Mantle within an AWS EC2 instance or AWS Elastic Container Service, you can set the +`MANTLE_AWS_INHERIT_IAM_ROLE` environment variable to `true` to inherit the permission set granted to the host +runner via either the EC2 instance's IAM role or the Elastic Container Service task execution IAM role. + You can set your environment variables in various ways, like the following: