From 4c6d2fe30748b6615797de60fbbe653438e65127 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 5 Jun 2026 14:30:04 +0000 Subject: [PATCH] =?UTF-8?q?docs:=20update=20AWS=20services=20for=20aioboto?= =?UTF-8?q?3=20=E2=86=92=20aiobotocore=20migration?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Update credential chain references from 'boto3' to 'botocore' to match pipecat PR #4643, which replaced aioboto3 with aiobotocore. Changes: - AWS Bedrock LLM: Updated credential chain and client config descriptions - AWS Transcribe STT: Updated credential chain description - AWS Polly TTS: Updated credential chain description --- api-reference/server/services/llm/aws.mdx | 8 ++++---- api-reference/server/services/stt/aws.mdx | 4 ++-- api-reference/server/services/tts/aws.mdx | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/api-reference/server/services/llm/aws.mdx b/api-reference/server/services/llm/aws.mdx index 8803bb0f..23daff6f 100644 --- a/api-reference/server/services/llm/aws.mdx +++ b/api-reference/server/services/llm/aws.mdx @@ -75,8 +75,8 @@ Before using AWS Bedrock LLM services, you need: AWS access key ID. If `None`, falls back to environment variables and the - default boto3 credential chain (instance profiles, IRSA, ECS task roles, SSO, - etc.). + default botocore credential chain (instance profiles, IRSA, ECS task roles, + SSO, etc.). @@ -109,7 +109,7 @@ Before using AWS Bedrock LLM services, you need: - Custom boto3 client configuration. If `None`, uses defaults with 5-minute + Custom botocore client configuration. If `None`, uses defaults with 5-minute connect/read timeouts and 3 retry attempts. @@ -207,7 +207,7 @@ await task.queue_frame( ## Notes -- **Credential resolution**: Credentials are resolved via a fallback chain: explicit parameters → environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`) → boto3 credential provider chain (instance profiles, IRSA, ECS task roles, SSO, credential files). Services running with IAM roles no longer need to export static credentials. +- **Credential resolution**: Credentials are resolved via a fallback chain: explicit parameters → environment variables (`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`) → botocore credential provider chain (instance profiles, IRSA, ECS task roles, SSO, credential files). Services running with IAM roles no longer need to export static credentials. - **No-op tool handling**: AWS Bedrock requires at least one tool to be defined when tool content exists in the conversation. The service automatically adds a placeholder tool when needed to prevent API errors. - **Model-specific parameters**: Some models (e.g., Claude Sonnet 4.5) don't allow certain parameter combinations. The service only includes explicitly set parameters in the inference config to avoid conflicts. - **Retry behavior**: When `retry_on_timeout=True`, the first attempt uses the `retry_timeout_secs` timeout. If it times out, a second attempt is made with no timeout limit. diff --git a/api-reference/server/services/stt/aws.mdx b/api-reference/server/services/stt/aws.mdx index ef14edc7..87ea5cea 100644 --- a/api-reference/server/services/stt/aws.mdx +++ b/api-reference/server/services/stt/aws.mdx @@ -67,8 +67,8 @@ Before using AWS Transcribe STT services, you need: AWS secret access key. If `None`, falls back to environment variables and the - default boto3 credential chain (instance profiles, IRSA, ECS task roles, SSO, - etc.). + default botocore credential chain (instance profiles, IRSA, ECS task roles, + SSO, etc.). diff --git a/api-reference/server/services/tts/aws.mdx b/api-reference/server/services/tts/aws.mdx index 133285c6..3b0e1a17 100644 --- a/api-reference/server/services/tts/aws.mdx +++ b/api-reference/server/services/tts/aws.mdx @@ -70,8 +70,8 @@ Before using AWS Polly TTS services, you need: AWS secret access key. If `None`, falls back to environment variables and the - default boto3 credential chain (instance profiles, IRSA, ECS task roles, SSO, - etc.). + default botocore credential chain (instance profiles, IRSA, ECS task roles, + SSO, etc.).