Skip to content

Commit 6a15265

Browse files
committed
d - Add new section on cloud provider configuration
1 parent fd65ee7 commit 6a15265

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

docs/usage.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,15 @@ toc: true
66

77
# Command line usage
88

9-
Luminaut requires access to AWS. The commands in this documentation assumes that your shell is already configured with the necessary AWS credentials. You can confirm your credential configuration by running `aws sts get-caller-identity`. For additional information on configuring AWS credentials, see the [AWS CLI documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html).
9+
## Cloud provider configuration
10+
11+
Luminaut supports AWS and GCP cloud environments. The commands in this documentation assumes that your shell is already configured with the necessary AWS and GCP credentials.
12+
13+
You can confirm your AWS credential configuration by running `aws sts get-caller-identity`. For additional information on configuring AWS credentials, see the [AWS CLI documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html).
14+
15+
You can confirm your GCP credential configuration by running `gcloud auth list`. For additional information on configuring GCP credentials, see the [GCP SDK documentation](https://cloud.google.com/sdk/docs/install).
16+
17+
## Command line interface
1018

1119
No arguments are required to run luminaut. The default is to look for a `luminaut.toml` file in the same directory and run available tools to start detecting resources.
1220

0 commit comments

Comments
 (0)