, 3 tweets, 1 min read Read on Twitter
One of the best, but not well documented or appreciated, things about CloudMapper is the ability to easily collect data. It has pagination and (recently) solid error reporting, but the jq syntax in collect_commands.yaml is something novel and powerful. 1/3
Ex. to get the Access Advisor info, you need to iterate through every user and role and call iam:GenerateServiceLastAccessedDetails which returns a jobid, which you then need to use with a call to iam:GetServiceLastAccessedDetails. That ends up being about a dozen lines. 2/3
First, it calls iam:GetAccountAuthorizationDetails, then it uses jq to extract out the parameters needed to call the generate calls. Then it extracts the jobid for the `get` call, checking the result and retrying as needed. github.com/duo-labs/cloud… 3/3
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Scott Piper
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!