You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The AWS request signing filter and AWS Lambda filter uses default credentials provider chain to get the AWS credentials. Is it possible to add option on aws/v3/credential_provider.proto so that the user has option to pick the exact credentials provider they want to use. This will help with optimizing the flow to pick the right credentials provider and execution don't have to go through the list of credentials provider one by one, thereby optimizing the flow.
Example: Say the DefaultCredentialsChain uses a chain of 'n' checks. IMDS is the last in the chain. By configuring to use ImdsCredentialsProvider, Envoy will directly query IMDS for credentials.
The text was updated successfully, but these errors were encountered:
The AWS request signing filter and AWS Lambda filter uses default credentials provider chain to get the AWS credentials. Is it possible to add option on aws/v3/credential_provider.proto so that the user has option to pick the exact credentials provider they want to use. This will help with optimizing the flow to pick the right credentials provider and execution don't have to go through the list of credentials provider one by one, thereby optimizing the flow.
Example: Say the DefaultCredentialsChain uses a chain of 'n' checks. IMDS is the last in the chain. By configuring to use ImdsCredentialsProvider, Envoy will directly query IMDS for credentials.
The text was updated successfully, but these errors were encountered: