Boto3 yana karɓar manufar wakili bayyananna ta hanyar abin Config na 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)

Maɓallan taswirar suna zaɓar ka'idar alkibla. Ƙimomin suna bayyana ƙarshen wakilin. Wannan misali yana aika buƙatun sabis na HTTP da HTTPS ta hanyar wakilin HTTP gaba ɗaya. Don gwajin da aka yarda na ƙarshen AWS na jama'a ba tare da asusun wakili ba, shigarwar HTTP daga jerin wakilan HTTP na iya samar da waɗannan URL biyu.

Ƙimar https:// a maimakon haka tana buƙatar mai sauraron wakili wanda ke karɓar haɗin TLS daga abokin ciniki. Kada ka canza tsarin ƙimar kawai don dacewa da maɓallin HTTPS.

Config.proxies yana wuce zaɓin wakili daga maɓallan muhalli HTTP_PROXY da HTTPS_PROXY ga wancan abokin ciniki. Ana iya gina wasu abokan ciniki da nasu abubuwan Config; gina wannan ba ya canza maɓallin muhalli na dukan tsari.

Riƙe duk wani zaɓi na abokin ciniki da ake buƙata, kamar yanki da manufar sake gwadawa, lokacin shigar da wannan cikin aikace-aikace. Takardun shaidar AWS suna kasancewa cikin daidaitaccen tsarin shaidar aikace-aikacen. Babu buƙatar canza EndpointCreator ko wata hanyar sirri ta botocore.

Don haɗin TLS zuwa wakilin HTTPS, Config yana da zaɓuɓɓukan proxies_config kamar proxy_ca_bundle da proxy_client_cert. Waɗannan sun shafi amincewa da tabbatar da takardar shaidar abokin ciniki akan haɗin wakilin. Sun bambanta da zaɓar ƙarshen sabis na AWS ko sanya hannu kan buƙatun AWS API.

Labarai masu alaƙa