How to use the AWS Workload Credentials Provider for cross-account secret retrieval and prefetching secrets
Security Blog
This article explains how to use two new features of the AWS Workload Credentials Provider: role chaining for cross-account secret retrieval and prefetching to reduce cold-start latency.
- Role chaining allows a single provider instance to access secrets across AWS accounts by assuming IAM roles
- Prefetching populates the provider's in-memory cache at startup, eliminating first-request network latency
- Configure explicit secrets or use tag-based discovery to prefetch secrets from source and target accounts
- Requires IAM permissions for sts:AssumeRole, secretsmanager:GetSecretValue, and secretsmanager:DescribeSecret
- Provider supports EC2, ECS, EKS, and Lambda with post-quantum TLS and SSRF token security
These features simplify multi-account architectures and improve performance for latency-sensitive applications retrieving secrets across AWS accounts.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Jun 11
2026
2026
AWS announces AWS Workload Credentials Provider
Aug 31
2026
2026
AWS Workload Credentials Provider is now available as a one-click install for Linux and Windows
May 4
2026
2026
AWS Payment Cryptography announces support for cross account key sharing
Jun 5
2026
2026
The AWS MCP Server now supports cross-account and cross-role access
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.