https://v1-18.docs.dapr.io/developing-applications/integrations/aws/Recent content in Integrations with AWS on Dapr DocsHugoenhttps://v1-18.docs.dapr.io/developing-applications/integrations/aws/authenticating-aws/Mon, 01 Jan 0001 00:00:00 +0000https://v1-18.docs.dapr.io/developing-applications/integrations/aws/authenticating-aws/<p>Dapr components leveraging AWS services (for example, DynamoDB, SQS, S3) utilize standardized configuration attributes via the AWS SDK. <a href="https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html#specifying-credentials">Learn more about how the AWS SDK handles credentials</a>.</p> <p>You can configure authentication using the AWS SDK’s default provider chain or one of the predefined AWS authentication profiles outlined below. Verify your component configuration by testing and inspecting Dapr runtime logs to confirm proper initialization.</p> <h3 id="terminology">Terminology</h3> <ul> <li><strong>ARN (Amazon Resource Name):</strong> A unique identifier used to specify AWS resources. Format: <code>arn:partition:service:region:account-id:resource</code>. Example: <code>arn:aws:iam::123456789012:role/example-role</code>.</li> <li><strong>IAM (Identity and Access Management):</strong> AWS&rsquo;s service for managing access to AWS resources securely.</li> </ul> <h3 id="authentication-profiles">Authentication Profiles</h3> <h4 id="access-key-id-and-secret-access-key">Access Key ID and Secret Access Key</h4> <p>Use static Access Key and Secret Key credentials, either through component metadata fields or via <a href="https://docs.aws.amazon.com/sdkref/latest/guide/creds-config-files.html">default AWS configuration</a>.</p>