Documentation for Automation with AWS AWS 1.1 – other releases are available in the Automation with AWS Documentation Directory.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This parameters template demonstrates invoking a Lambda function with the Invoke Lambda Function action:

JSON escaping requirements

If a parameter within the JSON formatted parameters template is a JSON structure in itself, it needs to be escaped before adding it as a value - this has two implications:

  • (tick) custom content needs to be escaped, which can be achieved with one of the many offline and online tools for this purpose, for example Code Beautify's Javascript Escape/Unescape
  • (error) variables with conflicting content (notably multi line variables like JIRA's $issue.description or Bamboo's $notification.textEmailContent) can not currently be used in this context (while all variables are escaped by default, they need to be escaped again when used within an already nested JSON structure) - this will be addressed in a near future release

{
  "FunctionName	": "arn:aws:sns:ap-southeast-2:123456789012:sample-AutomationWithAWSQuickstartLamb-1RRX37PWXZXLS",
  "Payload": "{\n \"Event\":\"${event.simpleName}\",\n \"Timestamp\": \"${event.timestamp}\",\n  \"TraceID\": \"${event.traceId}\"\n}"
}

  • No labels