Which AWS Services Do Not Asynchronously Invoke AWS Lambda Functions?

Answer: C, E.

The following are the functions that invoke synchronously and asynchronously the AWS Lambda function.

Among the options listed, the two services that do not asynchronously invoke AWS Lambda functions are:

C. AWS Cognito and D. AWS CodeCommit.

AWS Lambda can be triggered in two ways - Synchronous and Asynchronous.

Synchronous invocation of Lambda function happens when the calling service waits for the Lambda function to return a response or the calling service receives a failure response immediately.

Asynchronous invocation of Lambda function happens when the calling service sends an event to the Lambda function and does not wait for the response. Instead, Lambda function processes the event asynchronously and writes the response to an Amazon S3 bucket or an Amazon Kinesis stream or an Amazon DynamoDB table.

Let's look at the options:

A. AWS S3 can trigger a Lambda function when a new object is created in the S3 bucket. This can happen either synchronously or asynchronously, depending on how the Lambda function is configured to be triggered.

B. AWS SNS can trigger a Lambda function asynchronously when a new message is published to an SNS topic.

C. AWS Cognito is an identity management service that can authenticate and authorize users. However, it does not trigger a Lambda function.

D. AWS CodeCommit is a version control service that stores code in repositories. It does not trigger a Lambda function.

E. AWS CloudFront is a content delivery network that can trigger a Lambda function asynchronously when a viewer request is received for a resource that is associated with the Lambda function.

So, the correct options are C. AWS Cognito and D. AWS CodeCommit.