Bug: Incorrect data types for `sourceIPAddress` and `sequencer` Fields in S3RecordSchema Model

[leandrodamascena]

Expected Behavior

When working with S3 LifecycleTransition events, the value of the sourceIPAddress field is s3.amazonaws.com instead of an IPv4 value. Additionally, the sequencer field is only populated on PUT and delete object events.

Current Behavior

These fields are using incorrect data types.

Code snippet

No code snippet.

Steps to Reproduce

use this payload with this model.

{
   "eventVersion":"2.3",
   "eventSource":"aws:s3",
   "awsRegion":"us-east-1",
   "eventTime":"2025-02-21T21:46:45.775Z",
   "eventName":"LifecycleTransition",
   "userIdentity":{
      "principalId":"s3.amazonaws.com"
   },
   "requestParameters":{
      "sourceIPAddress":"s3.amazonaws.com"
   },
   "responseElements":{
      "x-amz-request-id":"something-1",
      "x-amz-id-2":"something-2"
   },
   "s3":{
      "s3SchemaVersion":"1.0",
      "configurationId":"some-sns",
      "bucket":{
         "name":"bucket-name",
         "ownerIdentity":{
            "principalId":"PRICIPAL"
         },
         "arn":"arn:aws:s3:::bucket-name"
      },
      "object":{
         "key":"/path/to/file.parquet",
         "size":12345,
         "eTag":"abcdef1232423423",
         "versionId":"SomeThingThere"
      }
   },
   "lifecycleEventData":{
      "transitionEventData":{
         "destinationStorageClass":"INTELLIGENT_TIERING"
      }
   }
}

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

latest

AWS Lambda function runtime

22.x

Packaging format used

npm

Execution logs

[dreamorosi]

Thanks for opening the issue Leo, I've put this in the backlog.

I've added the help-wanted and good-first-issue labels, so if anyone wants to pick this up in the next few days feel free to leave a comment to claim the issue.

If not, we'll work on it most likely before the end of the iteration, when we've completed the current backlog.

[ConnorKirk]

I can pick this up