I have created my own version of these directions below because the sample on the AWS site is based upon the IntelliJ IDE rather than the Rider IDE so some of the steps are slightly unclear or look different. The directions are available from the AWS site here. Installing the toolkit is simple once all the prerequisites are completed. Instructions (Should be covered in the CLIs, but just in case)īefore we can walk through the new toolkit, we have to get it installed. The SAM CLI will download and create a container to invoke your Lambda locally.

Make sure you’re running tests on the same version you’re targeting. The regular CLI install steps, shown here, are also not trivial. SAM Instructions are several steps long and not trivial.

The AWS CLI (Command Line Interface) and AWS SAM (Serverless Application Model) CLI tools, which the plugin uses to build, deploy and invoke your code.

An AWS account configured with the correct permissions.

NOTE: There is actually more work that needs to be done to fully configure your system to support the AWS Toolkit in Rider. If you don’t already have Rider, you can download a 30-day trial version at their site. It is also considerably less expensive then is Visual Studio. Rider is based on JetBrains’ IntelliJ platform and ReSharper, and can be considered a direct competitor to Visual Studio. For those that aren’t familiar with it, Rider is JetBrains’ cross-platform. JetBrains just announced their release of their Amazon Web Services Toolkit for Rider.

Download intellij rider