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
@iann0036 I'm curious about this suggestion, and whether it's a may or a must.
As described over in this issue, I couldn't get any of my inter-container proxying working without making HTTPS_PROXY == HTTP_PROXY == http://:. I hadn't properly read the proxy mode docs which suggest to use http for both variables, so I had https for the HTTPS variable. I ran the AWS CLI with --debug which gave me an error indicating that the proxy was only listening on http. I think the code corroborate this, but I wonder if this should be made more clear in the README.
I'm working with iamlive in proxy mode issued the following command
iamlive --profile iam_AdministratorAccess --mode proxy
then I'm trying to run boto3 scripts heres a snippet:
I receive an error:
My question is should I try and recreate the cert bundle to be used with boto3?
-- the profile does contain ca_bundle = ~/.iamlive/ca.pem
Also proxy mode will work for general awscli commands. Not sure what needs to be added to a python script.
Main goal is to get the resources enumerated when running python commands.
The text was updated successfully, but these errors were encountered: