Article by Nick Frichette.
Create a Console Session from IAM Credentials
When performing an AWS assessment you will likely encounter IAM credentials. These credentials can be used with the AWS CLI or other tooling to query the AWS API.
While this can be useful, sometimes you just can't beat clicking around the console. If you have IAM credentials, there is a way that you can spawn an AWS Console session using a tool such as aws-vault. This can make certain actions much easier rather than trying to remember the specific flag name for the AWS CLI.
If you are using temporary IAM credentials (ASIA...), for example, from an EC2 instance, you do not need to have any special IAM permissions to do this. If you are using long-term credentials (AKIA...), you need to have either sts:GetFederationToken or sts:AssumeRole permissions. This is to generate the temporary credentials you will need.
If you are attempting to avoid detection, this technique is not recommended. Aside from the suspicious
ConsoleLogin CloudTrail log, and the odd user-agent (Why is the IAM role associated with the CI/CD server using a Firefox user-agent string?), you will also generate a ton of CloudTrail logs.
From here, perform the following commands depending on the type of credentials you have.
For long-term credentials (Those starting with AKIA), there is an extra step that must be completed first. You will need to generate temporary credentials to retrieve the sign in token. To do this, we will make use of sts:GetFederationToken. As an alternative, sts:AssumeRole can also be used.
aws sts get-federation-token --name blah
This will return temporary IAM credentials that you can use with the next step.
For short-term credentials (Those starting with ASIA), you can run the following command:
If you'd like to generate a link without it automatically opening a new tab in your browser you can use the
-s flag and it will be printed to stdout.
To learn more about custom identity broker access to the AWS Console please see the official documentation.