Running Imposter in AWS Lambda

There are many ways to run Imposter. This section describes how to run it as a Lambda function in AWS.

Other ways to run Imposter

Standalone mock server

• Using the command line client - see Imposter CLI
• As a Docker container - see Imposter Docker container
• As a JAR file on the JVM - see Imposter JAR file

Embedded in tests

• Embedded within your Java/Kotlin/Scala/JVM unit tests - see JVM bindings
• Embedded within your JavaScript/Node.js unit tests - see JavaScript bindings

AWS Lambda Features

• Access to mock server via Lambda function URL (or AWS API Gateway)
• Supports OpenAPI, REST and SOAP mocks
• Supports Stores for recording data for later use or review

Deployment options

You can deploy Imposter as a Lambda function in various ways, such as the AWS Console, using infrastructure as code (e.g. Terraform) or a framework such as Serverless.

Another option is to use the Imposter CLI, which has some opinionated choices to make things easier. You should choose the option that best suits your environment.

Deploy to Lambda using Imposter CLI

You can deploy as a Lambda function using the Imposter CLI.

📖 Deploy to Lambda using Imposter CLI

Deploy to Lambda using AWS Console

You can also deploy as a Lambda function using the AWS Console.

📖 Deploy to Lambda using AWS Console

Deploy to Lambda with Serverless Framework

You can also deploy as a Lambda function using Serverless Framework.

📖 Deploy to Lambda with Serverless Framework.

Other ways to deploy to Lambda

You can also deploy using infrastructure as code tools (e.g. Terraform or CloudFormation).

---

What's next

• Learn how to use Imposter with the Configuration guide.