Alibaba Cloud SDK:Advanced settings

HTTPS settings

Scenarios

• Data security: HTTPS encrypts data transmission over SSL/TLS to prevent eavesdropping and tampering, ensuring data integrity.

• Compliance: Industries such as finance and healthcare have strict data transmission security requirements that mandate HTTPS.

Examples

• An application retrieves sensitive data, such as billing information or user privacy data, by calling Alibaba Cloud API operations.

• An application must comply with the General Data Protection Regulation (GDPR) or other data protection regulations.

For more information, see Configure HTTPS and TLS settings in the SDK.

Proxy settings

Scenarios

• Restricted network access: If your application runs behind a proxy server, such as in an enterprise internal network or a firewall-controlled environment, configure a proxy to reach external services.

• Traffic monitoring: Use a proxy during development to capture and analyze requests for debugging.

Examples

• An application deployed in an enterprise internal network uses an HTTP or HTTPS proxy to access Alibaba Cloud services.

• Multiple applications in an enterprise share a proxy server that manages and routes requests to external services.

For more information, see Configure a proxy.

Timeout settings

Scenarios

• Network stability: When network latency is high or server response is slow, a proper timeout prevents requests from hanging indefinitely.

• User experience: A proper timeout for user-facing applications prevents prolonged waiting when a service is unavailable.

Examples

• If the network connection is interrupted while a user uploads large files to Object Storage Service (OSS), a proper timeout terminates the request promptly and allows the user to retry.

• A proper timeout for long-running API operations, such as batch operations, prevents requests from blocking indefinitely.

For more information, see Configure a timeout mechanism.

Log settings

Scenarios

• Record request and response details to quickly locate causes of API call failures, such as signature errors or missing parameters.

• Analyze log data to optimize application performance based on metrics such as request latency and success rate.

Examples

• If an Elastic Compute Service (ECS) instance fails to be created, check the logs to verify whether the HTTP request signature and parameters are valid.

• Monitor the latency of OSS upload API operations to identify potential performance issues.

For more information, see Use the logging feature.