Possible to pass https.Agent options about proxy-agents

[TooTallNate]

Try doing:

var opts = url.parse(process.env.HTTPS_PROXY);
opts.rejectUnauthorized = true;
opts.keepAlive = true;                // workaround part i.
opts.secureProtocol = 'TLSv1_method'; // workaround part ii.
opts.ciphers = 'ALL';                  // workaround part ii.

awsConfig.httpOptions.agent = new HttpsProxyAgent(opts);

[dvonlehman]

Thanks Nate for the quick response. That appears to be doing the trick. I've incorporated it into my little helper module: https://www.npmjs.com/package/aws-config

[unni1]

Sorry for this newbie question. I googled a lot, but couldn't find an answer, may be I was not using the right keywords.

I was also facing the same issue and AWS support advised us to use https.agent. But I ran into some trouble with the company proxy. Finally, with pac-proxy-agent, it worked with the below code sample:

const pacProxyAgent = require('pac-proxy-agent'); 

const pacProxyUri = 'pac+http://proxy.com/proxy.pac'

var ec2Agent = new pacProxyAgent({
    uri: pacProxyUri,
    ciphers: "ALL",
    secureProtocol: "TLSv1_method"
});

var ec2 = new AWS.EC2({
    httpOptions: {
        agent: ec2Agent,
    },
    region: 'us-east-1'
}); 

I don't see any errors in the node.js log any more, but I am not sure if it is actually obeying the
secureProtocol: "TLSv1_method"
part.

I have this confusion because I randomly changed it to some other string, say "ABCv1", and it still didn't give me any errors. In Wireshark, I saw all the ClientHello messages to AWS where TLSv1.2, but I don't know if I was looking at the right place.

If I want to force TLSv1, is the above code sample correct?