Assume WIF is generally available and name it in the partition note

Drops the pre-publish caveat about Enterprise-only gating for Workload
Identity Federation; these pages stay gated with private: true until the
rollout, by which point the gate is lifted.

Also names Workload Identity Federation in the AWS partition
prerequisite, which described it as "cloud-based authentication", and
links it there.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: tedkahwaji

hugo/content/en/integrations/guide/aws-agent-installation-technical-reference.md

@@ -129,8 +129,6 @@ The API key is stored in your own Secrets Manager, encrypted at rest. Only the s
 
 Lambda instrumentation stores no Datadog credential in your account. The Datadog extension authenticates with the function's AWS execution identity through [Workload Identity Federation][5], using the `DD_ORG_UUID` and `DD_SITE` values Datadog sets on the function. No Datadog API key, secret ARN, or KMS-encrypted key is written into the function's configuration.
 
-<!-- TODO(DOCS-14545): Workload Identity Federation for intake is documented as Enterprise-only at /account_management/workload_identity_federation/. Lambda instrumentation depends on it being available to the orgs this feature targets, so confirm that gating is lifted before publishing this page. -->
-
 For that authentication to succeed, Datadog authorizes the function's execution role to send telemetry to your Datadog organization. Datadog sets up this authorization before it updates a function, and matches the execution role exactly rather than by a broader pattern.
 
 Because a single execution role is often shared across functions, Datadog creates these mappings but does not remove them on uninstall. Removing a mapping for a shared role could break another function that still depends on it.

hugo/content/en/integrations/guide/aws-agent-installation.md

@@ -70,7 +70,7 @@ For all workloads, confirm the following:
 ### AWS Lambda functions
 
 - **Resource collection**: [Resource collection][10] must be enabled on the AWS integration. Datadog uses it to list your functions and preview which ones a rule matches.
-- **AWS partition**: The commercial `aws` partition only. Functions in AWS GovCloud or the AWS China partitions are not supported, because Lambda instrumentation authenticates through cloud-based authentication, which those partitions don't support.
+- **AWS partition**: The commercial `aws` partition only. Functions in AWS GovCloud or the AWS China partitions are not supported, because Lambda instrumentation authenticates through [Workload Identity Federation][16], which those partitions don't support.
 - **Package type**: Zip functions only. Container image functions are not supported, because Datadog instrumentation is distributed as Lambda layers, which container image functions can't use.
 - **Architecture**: `x86_64` or `arm64`. A function must report a single architecture.
 - **Layer count**: AWS limits a function to five layers. Datadog adds up to two, so a function that already carries four or more layers is not eligible.