aws-opentelemetry-distro incompatible with google-adk>=1.26.0 — no published version resolves due to exact opentelemetry-sdk pinning

[andiper12]

aws-opentelemetry-distro cannot be installed alongside google-adk>=1.26.0 in the same Python environment. Google ADK requires opentelemetry-sdk>=1.36.0, <1.39.0, but every published version of aws-opentelemetry-distro pins opentelemetry-sdk to an exact version outside that range.

This blocks observability (CloudWatch/X-Ray) for Google ADK agents deployed on Amazon Bedrock AgentCore Runtime, following the procedure documented at Add observability to your AgentCore resources.

This is particularly relevant because the AgentCore CLI lists GoogleADK as a supported framework (agentcore create --framework GoogleADK --protocol A2A).

Versions tested
Every published version of aws-opentelemetry-distro was checked:

aws-opentelemetry-distro opentelemetry-sdk pinned Compatible with ADK (>=1.36.0, <1.39.0)?
0.16.0 (latest) ==1.40.0 No — above upper bound
0.15.0 ==1.39.1 No — above upper bound
0.14.2 ==1.33.1 No — below lower bound
0.14.1 ==1.33.1 No — below lower bound
0.14.0 ==1.33.1 No — below lower bound
0.12.x ==1.33.1 No — below lower bound
0.11.0 ==1.33.1 No — below lower bound
0.10.x ==1.33.1 No — below lower bound

There is a gap from opentelemetry-sdk==1.33.1 (ADOT ≤0.14.x) to ==1.39.1 (ADOT 0.15.0), skipping the entire 1.34.x–1.38.x range.

Google ADK versions affected: 1.26.0, 1.27.1–1.27.5, 1.28.0, 1.28.1, and 2.0.0a2. All have the same opentelemetry-sdk>=1.36.0, <1.39.0 constraint (source)

Reproducible test case

# Attempt with latest ADOT — fails
$ uv pip install --dry-run "aws-opentelemetry-distro==0.16.0" "google-adk[a2a]>=1.26.0"

x No solution found when resolving dependencies:
  -> Because google-adk==1.26.0 depends on opentelemetry-sdk>=1.36.0,<1.39.0
  and aws-opentelemetry-distro==0.16.0 depends on opentelemetry-sdk==1.40.0,
  we can conclude that aws-opentelemetry-distro==0.16.0 and
  google-adk[a2a]>=1.26.0 are incompatible.
  And because you require aws-opentelemetry-distro==0.16.0 and
  google-adk[a2a]>=1.26.0, we can conclude that your requirements
  are unsatisfiable.

# Verify ADOT 0.16.0 pins opentelemetry-sdk exactly
$ pip3 install --dry-run --ignore-installed "aws-opentelemetry-distro==0.16.0" 2>&1 | grep "opentelemetry-sdk=="
Collecting opentelemetry-sdk==1.40.0 (from aws-opentelemetry-distro==0.16.0)

# Verify Google ADK accepted range
$ pip3 install --dry-run --ignore-installed "google-adk==1.28.1" 2>&1 | grep "opentelemetry-sdk"
Collecting opentelemetry-sdk<1.39.0,>=1.36.0 (from google-adk==1.28.1)

# Also fails with Google ADK 2.0.0 alpha
$ pip3 install --dry-run --ignore-installed "google-adk==2.0.0a2" "aws-opentelemetry-distro==0.16.0"
ERROR: Cannot install aws-opentelemetry-distro==0.16.0 and google-adk==2.0.0a2
because these package versions have conflicting dependencies.
The conflict is caused by:
    google-adk 2.0.0a2 depends on opentelemetry-api<1.39.0 and >=1.36.0
    aws-opentelemetry-distro 0.16.0 depends on opentelemetry-api==1.40.0

# Version mapping script used to generate the table above
$ for v in 0.16.0 0.15.0 0.14.2 0.14.1 0.14.0 0.12.2 0.12.1 0.12.0 0.11.0 0.10.1 0.10.0; do
    sdk=$(pip3 install --dry-run --ignore-installed "aws-opentelemetry-distro==$v" 2>&1 \
      | grep "opentelemetry-sdk==" | head -1 \
      | grep -o "opentelemetry-sdk==[0-9.]*")
    echo "ADOT $v => $sdk"
  done

No modifications were made to either package. This is a clean install attempt with published PyPI versions only.

Environment

• Python: 3.13
• OS: macOS (also reproducible on Linux)
• pip: 25.2 / uv: latest
• No virtual environment modifications or overrides

[viw-test1]

1. Acknowledge the issue. It is a dependency version conflict, not a bug in either package.
2. The exact pinning (==) of opentelemetry-sdk in aws-opentelemetry-distro is by design, since each release is tested against a specific OTel SDK version.
3. The conflict is that google-adk caps at <1.39.0, while ADOT 0.15.0+ requires >=1.39.1. Earlier ADOT versions are at 1.33.1, below ADK's lower bound.
4. This needs to be resolved on the Google ADK side by changing their upper bound to include >=1.39.0. This is current ADK: <1.39.0,>=1.36.0.
5. I'd suggest filing an issue on google adk-python to request that update.