aws connectors¶

Amazon Web Services integrations. 46 connectors covering compute, storage, messaging, databases, ML, security, networking, and CI/CD. All 46 are now wired to aws-sdk-go-v2 for binary protocol fidelity, IAM credential-chain support (env vars, shared profile, EC2 instance role, ECS task role), and full operation coverage. Every connector accepts an endpoint field for LocalStack / VPC-endpoint scenarios. signing.go is an internal SigV4 helper, kept only for backwards-compatible imports.

Connectors in this category¶

signing.go is a helper, not a registered connector. The other 46 register via init().

Native-SDK deep section¶

aws_s3¶

Source: pkg/connector/connectors/aws/s3.go. Uses aws-sdk-go-v2/service/s3 with the v2 credential chain. Supports binary multipart uploads, range GETs, and presigned URLs.

connectors:
  s3:
    type: aws_s3
    config:
      region: us-east-1
      bucket: my-bucket
      # Optional explicit credentials; otherwise IAM role / env / shared file
      access_key_id: ${AWS_ACCESS_KEY_ID}
      secret_access_key: ${AWS_SECRET_ACCESS_KEY}

Send a PutObject by setting headers operation=put, key=path/to/object; the exchange body becomes the object body.

aws_sqs¶

Source: pkg/connector/connectors/aws/sqs.go. Outbound SendMessage and inbound long-polling ReceiveMessage (with DeleteMessage after handler returns).

connectors:
  events-out:
    type: aws_sqs
    config:
      region: us-east-1
      queue_url: https://sqs.us-east-1.amazonaws.com/123456789012/events

aws_dynamodb, aws_lambda, aws_kinesis, aws_sns, aws_eventbridge, aws_ec2, aws_rds, aws_secrets_manager¶

Same pattern: typed v2 service clients, set the operation via exchange header, body is the operation request payload (JSON or struct). See the Connector SDK guide for a full walk-through.

See also¶

• Connector SDK guide — adding native-SDK connectors
• pkg/component/s3/ — the first-class S3 component for high-volume pipelines
• IAM credential chain: standard aws-sdk-go-v2 resolution order (env vars → shared file → IMDS → ECS task role)