---
title: "Running an AWS Lambda Command from Windows Shells"
url: https://daily.dev/posts/running-an-aws-lambda-command-from-windows-shells-mg2pgipdo
source_url: https://nodogmablog.bryanhogan.net/2021/08/running-an-aws-lambda-command-from-windows-shells
type: article
source: "No Dogma Blog (Bryan Hogan)"
published: 2026-05-31T07:46:58.588Z
updated: 2026-05-31T08:17:58.151Z
tags: ["aws", "windows", ".net", "aws-lambda", "powershell"]
reading_time: 3
upvotes: 0
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Running an AWS Lambda Command from Windows Shells

**[No Dogma Blog \(Bryan Hogan\)](https://daily.dev/sources/bryanhogan)** · 3 min read · 0 upvotes · 0 comments

## Summary

Invoking AWS Lambda functions via the CLI behaves differently across Windows shells. The Linux command using single-quoted JSON payloads fails in both Command Prompt and PowerShell, requiring different escaping strategies for each. Command Prompt needs double quotes wrapping the payload with escaped inner quotes, while PowerShell uses single quotes with escaped inner double quotes. WSL Ubuntu and Git Bash accept the original Linux syntax unchanged. The post also covers the dotnet lambda invoke-function CLI tool as an alternative, detailing the shell-specific payload escaping for JSON objects and plain string payloads.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://nodogmablog.bryanhogan.net/2021/08/running-an-aws-lambda-command-from-windows-shells>

---

Tags: [#aws](https://daily.dev/tags/aws), [#windows](https://daily.dev/tags/windows), [#.net](https://daily.dev/tags/.net), [#aws-lambda](https://daily.dev/tags/aws-lambda), [#powershell](https://daily.dev/tags/powershell)

[View this post on daily.dev](https://daily.dev/posts/running-an-aws-lambda-command-from-windows-shells-mg2pgipdo)