Capturing AWS Traffic with Fiddler Everywhere
|Product Version||1.0.0 and above|
|3rd-party tool||AWS CLI|
|Supported OS||macOS, Linux, Windows|
Amazon Web Services (a.k.a. AWS) is a popular tool that provides multiple options to configure and manage computing power, database storage, content delivery, and others through the AWS CLI. This article covers the setup needed for Fiddler Everywhere to track requests made from the AWS CLI.
To capture traffic generated from AWS CLI commands, you need to configure the Fiddler Proxy for the preferred terminal application (where AWS CLI will be executed) and configure the
AWS_CA_BUNDLE environment variable for the certificate bundle that will be used for HTTPS certificate validation.
Open the terminal app where the AWS CLI commands will run. Set the terminal app to use the Fiddler Everywhere proxy, as described in this KB article.
Open Fiddler Everywhere and export the FiddlerRootCertificate.crt file via Settings > HTTPS > Advanced Settings > Export root certificate to Desktop.
Use OpenSSL toolkit to generate FiddlerRootCertificate.pem from the exported FiddlerRootCertificate.crt.
openssl x509 -inform DER -in ~/Desktop/FiddlerRootCertificate.crt -out ~/Desktop/FiddlerRootCertificate.pem
The sample path ~/Desktop/FiddlerRootCertificate.crt might differ on your side, depending on the used operating system.
Use the generated PEM file to set the
AWS_CA_BUNDLEspecifies the path to a certificate bundle to use for HTTPS certificate validation. If defined, this environment variable overrides the value for the profile setting
Start capturing traffic generated from AWS CLI commands.
aws sts get-caller-identity
After the debugging of the request made through are over, you could reset the
AWS_CA_BUNDLE environment variable while using the unset command.
Additionally, you might also reset the Fiddler Proxy in your terminal application.