Mapping Request and Response of CustomResource used by Type: AWS::Lambda::Function.

Motivation:

Avoid to write repeated code for every Swift Lambda Function where is used a CustomResource to pass properties. Inspired on event.go and response.go from https://github.com/aws/aws-lambda-go.git.

Modifications:

Added two new structs: Request and Response for Lambda event triggered by CloudFormation.

Result:

New models to be shared between Swift Lambda Functions that use CustomResource.

Create LambdaProxyEvent

previous PR with original template https://github.com/swift-server/swift-aws-lambda-events/pull/16

Motivation:

I was getting Decoding errors when invoking my lambda using APIGateway Event Request. I looked at the AWS Documentation and Serverless documentation and notice a different object from what is currently in the package

Modifications:

Edit a couple of the properties in the APIGatewayV2Request

Result:

My lambda is able to receive the Event from APIGateway along with the body I included in my http request

Add request and response object models for invoking Lambda function URLs.

Motivation:

Instead of having to spin up (and pay for) API Gateway endpoints, Lambdas can spin up bare URLs for public access. There are no existing request or response objects for these requests like there are for other event types.

Modifications:

• Created a FunctionURLRequest object matching the request payload format
• Created a FunctionURLResponse object matching the response payload format

These payloads are very similar (but not identical to) API Gateway V1 requests, so this is mostly just forked from that and tested until it works with simple requests. Note that I have only tested completely public endpoints, and cannot speak for the accuracy of the Authorizer sub-type.

Result:

After this change, users will be able to write:

struct FunctionURLHandler: LambdaHandler {
	typealias Event  = FunctionURLRequest
	typealias Output = FunctionURLResponse

	func handle(_ event: Event, context: LambdaContext) async throws -> Output {
		...
	}
}

and then be able to simply invoke their Lambdas without API Gateway:

curl https://abcd1234.lambda-url.{region}.on.aws

Edit a couple of the properties in the APIGatewayV2Request

Motivation:

I was getting Decoding errors when invoking my lambda using APIGateway Event Request. I looked at the AWS Documentation and Serverless documentation and notice a different object from what is currently in the package

Modifications:

Edit a couple of the properties in the APIGatewayV2Request

Result:

My lambda is able to receive the Event from APIGateway along with the body I included in my http request

Add support for the existing domainName property to API Gateway V1 events in Swift.

Motivation:

According to AWS example events and documentation, this seems to be included in all requests. We should be able to access this seamlessly in Swift.

Modifications:

• Added domainName property to requestContext in APIGatewayRequest object
• Added example values for domainName to corresponding tests

Result:

After this change, users can access the domain name with:

struct ApiGatewayHandler: LambdaHandler {
	typealias Event  = APIGatewayRequest
	typealias Output = APIGatewayResponse

	func handle(_ event: Event, context: LambdaContext) async throws -> Output {
		...
		let domainName: String = event.domainName
		...
	}
}

Make properties of CloudFormation templates public to be accessed by other modules that import the AWSLambdaEvents module.

Motivation:

The properties of CloudFormation templates (request and response) have the default internal access, making it impossible for other modules to use them.

Modifications:

Add public access level to properties.

Result:

The properties will be visible by other modules.

Make APIGatewayV2Request authorizer claims optional.

Motivation:

The current non-optional claims property is not compatible with the Lambda Runtime Interface Emulator.

Aside from this, the AWS Docs specify a null value in this example: https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-input-format

Modifications:

Make APIGatewayV2Request authorizer claims optional.

Result:

APIGatewayV2Request authorizer claims is optional, allowing a nil value so that the Lambda Runtime Interface Emulator works with this library and so it's in accordance with the AWS docs.

Expose Authorizer claims

Motivation:

Currecnt version doesn't expose Cognito signed user details

Modifications:

Added an option field, that doesnt break existing code

Result:

APIGateway.Request.requestContext.authorizer? is now available

Updated incorrect sns event fields to match correct format

Motivation:

Issue: #25

Modifications:

Updated incorrect sns event fields to match correct format. Correct format can be seen here

Result:

Correct parsing of a SNS Event

Motivation

We have potential name clashes with existing AWS libraries, if we namespace our events under the service name. For example S3.Event. This problem has been documented here: https://github.com/swift-server/swift-aws-lambda-runtime/issues/119

Changes

This PR picks up the fix, that was initially intended to land in the runtime repo directly: https://github.com/swift-server/swift-aws-lambda-runtime/pull/203

Result:

No more namespace issues with AWS libraries.

motivation: events may be used in an async context and as such musct conform to Sendable

changes:

• define common abstraction for Sendable & Codable
• conform all events Sendable

Support for one Cognito Lambda Trigger (PreSignUp_SignUp), with infrastructure to support all 20 others.

Motivation:

I've been playing around with implementing WebAuthn (passkeys) using only Swift. It turned out to be complex, because Cognito doesn't support it yet, and requires the use of 3/4 lambda triggers.

Modifications:

Added a basic Cognito trigger enum that should be able to model all 21 lambda trigger types. Made some tests for the single trigger I've currently actually used.

Result:

Cognito triggers are a little funny in that they all have a common shape, but differ in some ways depending on the type. And, because there are so many (21 as of right now), I didn't want to create a bunch of duplicate structs. So, I opted for a enum that stores the trigger-specific data.

I think this change is potentially useful, even though it is far from a complete implementation. I figured I'd propose it in PR form just to see what you all think. Happy to entertain suggestions!

Expected behavior

Correct parsing using JSONDecoder().decode(SNS.Message.self, from: data)

Actual behavior

Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: \"SigningCertUrl\", intValue: nil) (\"SigningCertUrl\").", underlyingError: nil))

SigningCertUrl and SubscribeUrl will result in parsing error

Steps to reproduce

1. Create a Lambda and parse a SNS Event.

SNS Message Structure

SwiftAWSLambdaRuntime version/commit hash

main branch

Swift & OS version (output of swift --version && uname -a)

swift-driver version: 1.62.15 Apple Swift version 5.7.1 (swiftlang-5.7.1.135.3 clang-1400.0.29.51)

Expected behavior

Expected my lambda to return a APIGatewayV2Response along with my body

Actual behavior

Found the following in the CloudWatch Logs

2022-04-25T15:40:54+0000 warning Lambda : lifecycleIteration=1 lambda handler returned an error: requestDecoding(Swift.DecodingError.keyNotFound(CodingKeys(stringValue: "version", intValue: nil), Swift.DecodingError.Context(codingPath: [], debugDescription: "No value associated with key CodingKeys(stringValue: \"version\", intValue: nil) (\"version\").", underlyingError: nil)))

Steps to reproduce

1. Use the Deployment Lambda found in the Examples dir and deployed to AWS using APIGateway with a Lambda_PROXY
2. make an HTTP call to your APIGateway
3. Observe the errors in the CloudWatch Log

If possible, minimal yet complete reproducer code (or URL to code)

serverless.yml

service: helloworld-swift-aws

provider:
    name: aws
    runtime: provided
    region: us-east-2
    
package:
    artifact: .build/lambda/HelloWorld/lambda.zip

functions:
    hello:
        handler: HelloWorld
        memorySize: 128
        events:
          - http:
              method: ANY
              path: /{proxy+}
              cors: true

SwiftAWSLambdaRuntime version/commit hash

main branch

Swift & OS version (output of swift --version && uname -a)

Apple Swift version 5.6 (swiftlang-5.6.0.323.62 clang-1316.0.20.8) MacOS Monterrey 12.3.1

Received SNS object has uppercased "URL" coding keys.

Motivation:

The received SNS object has uppercased "URL" coding keys. The object can not be decoded otherwise. Currently, the coding keys contain a lower case "Url", for example "SigningCertUrl" but should be "SigningCertURL".

{
  "Timestamp": "2021-10-08T11:18:40.043Z",
  "SigningCertURL": "https://sns.eu ****",
  "MessageId": "776e6308-8c44-5ee ****",
  "Type": "Notification",
  "SignatureVersion": "1",
  "Signature": "s71McLg8d9OP86E4a *****",
  "TopicArn": "arn:aws:sns:eu-west-1:06 *****",
  "UnsubscribeURL": "https://sns.eu-w****",
  "Message": "{\"action\":\"upload_document_version\",\"entityId\":\"1633691914791-1796da229943***aace80d5e023f3***c\",\"entityType\":\"DocumentVersion\",\"organizationId\":\"d-9367073c36\",\"parentEntityId\":\"516d7ab0537aff5d39a469439c*****2d0d4\",\"parentEntityType\":\"Document\"}"
}

Modifications:

The coding keys string value has been changed.

Result:

We can now use the decoded object with dot notation.

Expected behavior

Package is correctly installed.

Actual behavior

error: Dependencies could not be resolved because no versions of 'swift-aws-lambda-events' match the requirement 0.1.0..<1.0.0 and root depends on 'swift-aws-lambda-events' 0.1.0..<1.0.0.

There are no appropriate git tags on the repository.

Steps to reproduce

1. Add as dependency to Package.swift
2. Attempt install/build/etc.

If possible, minimal yet complete reproducer code (or URL to code)

SwiftAWSLambdaRuntime version/commit hash

Swift & OS version (output of swift --version && uname -a)

Apple Swift version 5.4.2 (swiftlang-1205.0.28.2 clang-1205.0.19.57). Darwin breathwork.local 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64 x86_64