AWS SDK Wrapper
Actions15
Overview
This node acts as a generic wrapper for AWS SDK service requests, allowing users to interact with any AWS service by specifying the service name, operation, and input parameters. It is particularly useful when you want to perform operations on various AWS services without needing dedicated nodes for each service.
For the ResendValidationEmail operation under the default resource, this node enables resending a validation email through the specified AWS service (likely Amazon SES or Cognito). This can be beneficial in scenarios where a user needs to trigger a resend of a verification or validation email, such as account confirmation or email address verification workflows.
Practical example:
- Resend a validation email to a user who did not receive the original verification email during sign-up.
- Trigger a resend of an email validation in automated user management systems.
Properties
| Name | Meaning |
|---|---|
| Region | Choose the AWS region where the service request will be sent. Options include all major AWS regions like US East (N. Virginia), EU (Frankfurt), Asia Pacific (Tokyo), etc. Default is "us-east-1". |
| Service | Select the AWS service to use for the request. The list includes all AWS services such as ACM, S3, SES, CognitoIdentityServiceProvider, Lambda, DynamoDB, etc. Default is "S3". |
| Version | Specify the API version to use for the selected AWS service. Different services have different available versions. The version dropdown updates based on the selected service. |
| Request Has Input | Boolean flag indicating whether the request requires input parameters. For operations that do not require input (e.g., listing buckets), set this to false. Defaults to true. |
| Request Input | JSON object representing the input parameters for the AWS service operation. Must be correctly formatted according to the AWS SDK API for the chosen operation. Visible only if "Request Has Input" is true. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:
json: The response from the AWS SDK operation call, which varies depending on the service and operation used. For ResendValidationEmail, it would typically contain confirmation of the email resend request.pairedItem: The index of the input item this output corresponds to.
If the operation returns binary data (not typical for ResendValidationEmail), it would be included accordingly, but this operation generally returns JSON confirmation.
Dependencies
- Requires an AWS API authentication credential configured in n8n with access key ID, secret access key, and optionally a session token.
- Uses the AWS SDK for JavaScript v2 internally.
- The node dynamically loads the AWS service client based on the selected service and version.
- Proper permissions must be granted to the AWS credentials to perform the requested operation (e.g., permission to resend validation emails).
Troubleshooting
- Invalid Service Error: If the selected service is not recognized by the AWS SDK, the node throws an error stating the service is invalid. Ensure the service name matches one of the supported AWS services.
- Invalid Operation Error: If the operation does not exist for the selected service, an error is thrown. Verify the operation name is correct and supported by the AWS SDK for that service.
- Credential Issues: Errors occur if AWS credentials are missing or incomplete. Make sure valid AWS credentials with necessary permissions are configured.
- Malformed Input: If the JSON input for the request is invalid or does not match the expected structure for the operation, the AWS SDK will return an error. Validate the JSON input carefully.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, returning the error details alongside the input data.
Links and References
- AWS SDK for JavaScript v2 Documentation
- AWS Regions and Endpoints
- Amazon SES - Resend Verification Email API (if applicable)
- n8n Documentation - Working with Credentials
Note: This summary is based on static analysis of the node's code and provided property definitions. Runtime behavior depends on actual AWS service responses and configured credentials.