You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/modules/post/multi/escalate/aws_create_iam_user.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,8 +65,8 @@ aws_create_iam_user can be used to take over an AWS account given access to
65
65
a host having 1). overly permissive instance profile/role, 2). API Access keys.
66
66
Once a foothold is established, you can run the module to pull temporary
67
67
access keys from the metadata service. If this fails, search the instance for
68
-
API access keys, e.g., see ~/aws/credentals, and set `AccessKeyId`,
69
-
`SecretAccessKey`, & `Token` (optional).
68
+
API access keys, e.g., see ~/.aws/credentials, and set `AccessKeyId`,
69
+
`SecretAccessKey`, & `Token` (optional).
70
70
71
71
## Options
72
72
@@ -75,6 +75,8 @@ API access keys, e.g., see ~/aws/credentals, and set `AccessKeyId`,
75
75
*`SecretAccessKey`: set this if you find access keys on the host and instance has no profile/privileges
76
76
*`Token`: set this if you find access keys on the host and instance has no profile/privileges. This is optional as this signifies temporary keys, if you find these, these are most likely expired.
77
77
*`Proxies`: depending on your environment, you may wan to proxy your calls to AWS.
78
+
*`CREATE_API`: when true, creates API keys for this user
79
+
*`CREATE_CONSOLE`: when true, creates a password for this user so that they can access the AWS console
78
80
79
81
80
82
### Establish a foothold
@@ -212,4 +214,4 @@ You can see the API keys stored in loot:
0 commit comments