Is the current NO_PROXY situation permanent?

[jgard]

CC: @tim-finnigan as he's been active on the subject (1, 2), thanks Tim. We understand that boto, now based on urllib, doesn't support any proxy bypass list. Thus, there's currently no way to configure a single Config object (or use environment variables) with proxy configuration and a bypass/exception list to work in an environment with mixed requirements.

We are an enterprise with required outbound web proxies and many VPC endpoints deployed. So if a boto3 script needs to use, say, EC2 in the same region it can bypass proxy and use the VPC endpoint. If it also has to use IAM (for which we have no endpoint in our region), it must go out the proxy.

Thus, an example script needs to be aware of what services we do and don't have endpoints for, and use a proxy-aware configuration sometimes, like:

import boto3
from botocore.config import Config

proxy_config = Config(
    region_name='us-east-2',
    signature_version='v4',
    proxies={'https': 'http://proxy.company.com'}
)

no_proxy_config = proxy_config = Config(
    region_name='us-east-2',
    signature_version='v4',
    proxies={}
)

ec2client = boto3.client('ec2', config=proxy_config)
iamclient = boto3.client('iam', config=no_proxy_config)

Is there any hope for an enhancement here?