3.2 KiB
| title | description | contentType |
|---|---|---|
| AWS credentials | Documentation for AWS credentials. Use these credentials to authenticate AWS in n8n, a workflow automation platform. | integration |
AWS credentials
You can use these credentials to authenticate the following nodes:
- AWS Bedrock Chat Model
- AWS Certificate Manager
- AWS DynamoDB
- AWS Elastic Load Balancing
- AWS Lambda
- AWS Rekognition
- AWS S3
- AWS SES
- AWS SNS
- AWS SNS Trigger
- AWS SQS
- AWS Textract
- AWS Transcribe
- Embeddings AWS Bedrock
Prerequisites
Create an AWS{:target=_blank .external-link} account.
Supported authentication methods
- API access key
Related resources
Refer to AWS's Identity and Access Management documentation{:target=_blank .external-link} for more information about the service.
Using API access key
To configure this credential, you'll need:
- The AWS Region: be sure to adjust this if you aren't using the default region
- The Access Key ID: provided when you generate an access key
- The Secret Access Key: provided when you generate an access key
Refer to the AWS Managing Access Keys documentation{:target=_blank .external-link} for instructions on generating and updating access keys.
Using a temporary security credential
You can configure the access key as a temporary security credential by toggling the slider on.
If you select this option, you must add a Session token to the credential.
Refer to the AWS Temporary security credential documentation{:target=_blank .external-link} for more information on working with temporary security credentials.
Virtual Private Cloud usage (custom endpoint)
If you use Amazon Virtual Private Cloud (VPC){:target=_blank .external-link} to host n8n, you can establish a connection between your VPC and these apps:
- Rekognition
- Lambda
- SNS
- SES
- SQS
- S3
To use these apps with a custom endpoint, toggle the Custom endpoint slider on and add the relevant custom endpoint(s).
If you don't add a custom endpoint, the n8n credential will use the default endpoint.