This article examines a critical AWS architecture decision: whether to use Lambda functions or direct API integration when processing SQS events triggered by DynamoDB streams. The author describes a common pattern where account deletion triggers a cascade of child account deletions. The traditional approach uses a Lambda as an intermediary between Event Bridge and the API, while the alternative proposes eliminating this 'glue' layer entirely.

Key considerations include managing dead letter queues, handling additional API load from polling, and reducing maintenance overhead. The author seeks community input on whether direct API consumption of events via libraries like sqs-consumer represents good practice. This architectural choice impacts system complexity, operational costs, and scalability.

Understanding these trade-offs is essential for teams building event-driven systems on AWS, particularly when balancing developer productivity against infrastructure efficiency.