Feature request: Missing event source classes for IoT Core events

[leandrodamascena]

Use case

Original issue for Parser: #5891

On AWS IoT, you can configure registry events, which send messages to MQTT topics on for example creation, updating or deletion of things.

This generates the underneath format.

{
    "eventType" : "THING_EVENT",
    "eventId" : "f5ae9b94-8b8e-4d8e-8c8f-b3266dd89853",
    "timestamp" : 1234567890123,
    "operation" : "CREATED|UPDATED|DELETED",
    "accountId" : "123456789012",
    "thingId" : "b604f69c-aa9a-4d4a-829e-c480e958a0b5",
    "thingName" : "MyThing",
    "versionNumber" : 1,
    "thingTypeName" : null,
    "attributes": {
                "attribute3": "value3",
                "attribute1": "value1",
                "attribute2": "value2"
    }
}

Solution/User Experience

@event_source(model=IoTCRUDEvent)
def handle(event: IoTCRUDEvent, _: LambdaContext):
    ...

Alternative solutions

Acknowledgment

• This feature request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[basvandriel]

Hi @leandrodamascena. I'm sorry for the late reply. I'll pick this up ASAP! Feel free to assign it to my name.

[leandrodamascena]

Hi @leandrodamascena. I'm sorry for the late reply. I'll pick this up ASAP! Feel free to assign it to my name.

Thats amazing to hear @basvandriel! For event source data class, please add a comment in each property, ok? Something like this.

Assigned to you.

[basvandriel]

I'll make the pull request ready tomorrow. Drafted the changes here

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.