Collecting Vehicle Inspection Booking Changes at a Repair Shop
This supports a car maintenance company with 12 workshops in collecting changes and cancellations of vehicle inspection bookings in one place and passing them on to review parts orders. An EventBridge rule selects only the events from the company's own account that the booking app sends, and puts them in an SQS queue. The process that takes them out of the queue is not part of this architecture. The business scenario is a fictional example prepared by IceShore, not a real company or system. Source: https://github.com/aws-samples/serverless-patterns/tree/a6cb0af285a2c326cbc35acd3ee5dc0c659db75d (Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.; License: MIT No Attribution (MIT-0)). The original files are reproduced without modification.
Actors
Use cases
- Collecting inspection booking changes
This diagram supports a car maintenance company with 12 workshops as it collects changes and cancellations of vehicle inspection bookings in one place and passes them on for a review of parts orders. Of the events the booking app sends, an EventBridge rule selects only those from the company's own account whose source is demo.sqs, and puts them in an SQS queue. The business scenario is a fictional example prepared by IceShore, not a real company or system. The diagram is based on eventbridge-sqs/template.yaml from aws-samples/serverless-patterns (license: MIT-0).
How booking changes reach the queue
The diagram has three elements. The first is the inspection booking app, which calls PutEvents to publish custom events with source demo.sqs to the default event bus. It is not defined in the template; it was inferred from the event pattern and placed as an external system. The second is an EventBridge rule (EventRule) that selects the events. The third is an SQS queue (MySqsQueue) that holds the booking changes as messages. Data flows from the booking app to the rule, then to the queue. The queue policy allows SQS:SendMessage for events.amazonaws.com. The process that takes changes out of the queue to review parts orders is not part of this setup.
Use case: Collecting inspection booking changes
The use case starts when a customer changes or cancels an inspection date on the web or by phone, and the booking app sends a demo.sqs event through the EventBridge PutEvents API. The EventRule event pattern matches events whose account is the deploying account and whose source is demo.sqs. Matching events are sent to the SQS queue via SendMessage as the rule's target. The queue holds the changes as messages until a later process takes them out. The template sets no queue properties, so settings such as retention stay at the SQS defaults. About 300 changes a day are assumed, with more at lunchtime and in the evening. The data is "Booking changes" (booking number, workshop, date and time before and after the change, vehicle model and parts category), and it is assumed not to include customers' names or contact details.
Source IaC
The source is eventbridge-sqs/template.yaml in aws-samples/serverless-patterns (commit a6cb0af285a2c326cbc35acd3ee5dc0c659db75d, license MIT-0). It is a CloudFormation (SAM) template with Transform AWS::Serverless-2016-10-31. Its main resources are: - AWS::SQS::Queue (MySqsQueue) - AWS::Events::Rule (EventRule), including the event pattern and target - AWS::SQS::QueuePolicy (EventBridgeToToSqsPolicy) Its Outputs return the queue name, ARN, and URL. The template has no settings about inspections or bookings; the business content is a scenario added by IceShore.
How this diagram was made
An AI read the IaC in the public repository and wrote the diagram description (ADL) through IceShore's MCP (Model Context Protocol) server. IceShore then rendered the diagram from that description. The booking app is not in the template; because the event pattern implies a sender, it was added as an external system. The car maintenance company scenario and its volumes are a fictional example prepared by IceShore.
FAQ
Can an architecture diagram be generated automatically from a CloudFormation (SAM) template?
Yes. This diagram was made from eventbridge-sqs/template.yaml: an AI wrote the diagram description through IceShore's MCP server, and IceShore rendered it. Elements not in the template, in this case the booking app, are added with a note in the description that they are outside the template.
Does the diagram include the process that takes booking changes out of the queue?
No. The source template defines no consumer resources, so the diagram stops at enqueuing messages into the SQS queue. That a parts-order review process takes them out later is part of this example's scenario.
Which events are sent to the queue?
Only events that match the EventRule pattern: events whose account is the deploying account itself and whose source is demo.sqs.
Source: aws-samples/serverless-patterns（MIT-0）
Load your IaC to get a diagram like this for your own system. What is IceShore
