EventBridge Pipes

EventBridge Pipes — source → (filter/enrich) → target integrations. The control plane is exposed over the SDK (ListPipes, CreatePipe, DescribePipe, UpdatePipe, DeletePipe, StartPipe, StopPipe, plus tagging) at `pipes.<region>` and `/v1/pipes`, and via CloudFormation (AWS::Pipes::Pipe).

REST-JSON multi-tenant 10 operations

Quick start

import boto3
pipes = boto3.client("pipes", endpoint_url="http://localhost:4566",
                     region_name="us-east-1",
                     aws_access_key_id="test", aws_secret_access_key="test")
pipes.create_pipe(Name="ddb-to-sns",
    Source="arn:aws:dynamodb:us-east-1:000000000000:table/t/stream/2024-01-01T00:00:00.000",
    Target="arn:aws:sns:us-east-1:000000000000:topic",
    RoleArn="arn:aws:iam::000000000000:role/pipe")
print([p["Name"] for p in pipes.list_pipes()["Pipes"]])

Supported operations

10 operations exposed by this service as of MiniStack 1.5.8. Extracted directly from the handler dispatch in the source module.

CreatePipe DeletePipe DescribePipe ListPipes ListTagsForResource StartPipe StopPipe TagResource UntagResource UpdatePipe

CloudFormation

The CloudFormation engine provisions these resource types via this service:

AWS::Pipes::Pipe

See CloudFormation engine for intrinsic support and lifecycle details.

Known limitations

Only the DynamoDB Streams source with an SNS or Step Functions target is actually executed (a background poller forwards records, a state machine getting one StartExecution per batch); all other source/target combinations are stored as metadata only.

Source

ministack/services/pipes.py

Read the source to verify the ops list above — dispatch tables and handler functions are the ground truth.

See also: all services · configuration · limitations.