All Topics
All Topics
Technology
Technology
AI
AI
Business
Business
Entertainment
Entertainment
News
News
Programming
Programming
Security
Security
Science
Science
Design
Design
Environment
Environment
Finance
Finance
Crypto
Crypto
Politics
Politics
Sports
Sports
Education
Education
Gaming
Gaming
Art
Art
Music
Music
Health
Health
Books
Books
Food
Food
Travel
Travel
Personal
Personal
Bluesky
Twitter

Using AWS Workload Credentials Provider for cross-account secret retrieval and prefetching

By

Derik Wang Derik is a Software Engineer on the AWS Secrets Manager team.

2d ago· 7 min readen

Summary

This article explains how to use two new features of the AWS Workload Credentials Provider: role chaining for cross-account secret retrieval and prefetching of secrets to reduce cold-start latency. It provides a step-by-step guide for configuring IAM role chaining to access secrets across multiple AWS accounts through a single provider instance, and demonstrates how prefetching can improve performance for latency-sensitive applications by populating the provider's in-memory cache ahead of time.

Source

bskyUsing AWS Workload Credentials Provider for cross-account secret retrieval and prefetchingaws.amazon.com

Key quotes

· 3 pulled
If you manage secrets across multiple AWS accounts or need faster secret access for latency-sensitive applications, this post shows you how to meet those requirements using two new features of the AWS Workload Credentials Provider.
By using role chaining, you can access secrets across AWS accounts through a single provider instance by assuming AWS Identity and Access Management (IAM) roles.
Prefetching populates the provider's in-memory cache to reduce cold-start latency.
Snippet from the RSS feed
If you manage secrets across multiple AWS accounts or need faster secret access for latency-sensitive applications, this post shows you how to meet those requirements using two new features of the AWS Workload Credentials Provider (provider). You will lea

You might also wanna read

Comments

Sign in to join the conversation.

No comments yet. Be the first.