I-Boto3 yamukela inqubomgomo ye-proxy ecacile ngokusebenzisa into ye-Config ye-botocore:

import boto3
from botocore.config import Config

network = Config(proxies={
    'http': 'http://proxy.example:8080',
    'https': 'http://proxy.example:8080',
})
s3 = boto3.client('s3', config=network)

Okhiye bemephu bakhetha iphrothokholi yendawo eya kuyo. Amanani achaza indawo yokugcina ye-proxy. Lesi sibonelo sithumela kokubili izicelo zesevisi ze-HTTP ne-HTTPS nge-proxy eyodwa ye-HTTP ehamba phambili. Ukuze kuhlolwe indawo yokugcina ye-AWS yomphakathi evunyelwe ngaphandle kwe-akhawunti ye-proxy, ingeno ye-HTTP evela kuhlu lwe-proxy ye-HTTP inganikeza lawo ma-URL amabili.

Inani le-https:// lizodinga esikhundleni salokho isilaleli se-proxy esamukela ukuxhumana kwe-TLS okuvela kuklayenti. Ungashintshi uhlelo lwenani ukuze nje luhambisane nokhiye we-HTTPS.

I-Config.proxies yeqa ukukhethwa kwe-proxy okuvela kuziguquguquki zemvelo i-HTTP_PROXY ne-HTTPS_PROXY zalelo klayenti. Amanye amaklayenti angakhiwa ngezinto zawo ze-Config; ukwakha lokhu akushintshi isiguquguquki semvelo sonke inqubo.

Gcina noma yiziphi ezinye izinketho zeklayenti ezidingekayo, njengesifunda nenqubomgomo yokuzama futhi, lapho ufaka lokhu kuhlelo lokusebenza. Imininingwane yokufakazela ye-AWS ihlala ekucushweni okujwayelekile kwemininingwane yokufakazela yohlelo. Akudingeki kushintshwe i-EndpointCreator noma enye indlela eyimfihlo ye-botocore.

Ngokuxhumana kwe-TLS ku-proxy ye-HTTPS, i-Config futhi inezinketho ze-proxies_config njenge-proxy_ca_bundle ne-proxy_client_cert. Lezi ziphathelene nokwethenjwa nokuqinisekiswa kwesitifiketi seklayenti ekuxhumaneni kwe-proxy. Zihlukile ekukhetheni indawo yokugcina yesevisi ye-AWS noma ekusayineni izicelo ze-AWS API.

Izihloko ezihlobene