chore: add extended request ID to general AWS Attributes

[trivikr]

Fixes #1670

Changes

Adds extended request ID to general AWS Attributes under aws.extended_request_id

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• schema-next.yaml updated with changes to existing conventions.

[trivikr]

From my understanding, the schema-next.yaml is not required to be changed, as no existing attribute is being updated. This PR adds a new attribute.

Docs: https://opentelemetry.io/docs/specs/otel/schemas/file_format_v1.0.0/#span_events-section

[lmolkova]

Please reference this attribute from AWS spans you expect the attribute to be available on - there are quite a few of them defined here https://github.com/open-telemetry/semantic-conventions/blob/main/model/aws/sdk-spans.yml

Also, is it populated by any instrumentations?

[trivikr]

is it populated by any instrumentations?

I've been maintaining AWS SDK for JavaScript for 5+ years, and was recently added as component owner of it's OpenTelemetry Instrumentation in open-telemetry/opentelemetry-js-contrib#2557. I plan to add the attribute as soon as it's merged and released in semantic convention.

AWS SDK for Go Observability solution does use it https://github.com/aws/aws-sdk-go-v2/blob/a164d844a90d8b9f86f8cb827b3fef512eabaabf/service/internal/s3shared/metadata_retriever.go#L53

[trivikr]

Please reference this attribute from AWS spans you expect the attribute to be available on

Added in 24ada32 (#1671)

[trivikr]

The markdown-link-check either incorrectly checks the link from the logs, or the link might have been down when the test was performed.

  ERROR: 1 dead links found in ./docs/system/system-metrics.md !
  [✖] https://blogs.oracle.com/linux/post/understanding-linux-kernel-memory-statistics → Status: 0
make: *** [Makefile:72: markdown-link-check] Error 1

It's failing for other PRs too:

• https://github.com/open-telemetry/semantic-conventions/actions/runs/12139916442/job/33848539883
• https://github.com/open-telemetry/semantic-conventions/actions/runs/12293003057/job/34324346286

Can you re-run the workflow?

[damemi]

@trivikr hi, could you please clarify if this header should be required for all AWS services? In your initial issue, you mentioned that x-amz-id-2 is used in S3, but here it was also added to services like DynamoDB

I just opened another issue (before I saw this) because it doesn't seem like Dynamo uses x-amz-id-2 in any of its documentation or client code. Should this attribute be removed from the required list for AWS services that don't use it?