A Step Functions Task to publish messages to SNS topic.
import { SnsPublish } from 'aws-cdk-lib/aws-stepfunctions-tasks';Or use the module namespace:
import * as stepfunctions_tasks from 'aws-cdk-lib/aws-stepfunctions-tasks';
// stepfunctions_tasks.SnsPublishConfiguration passed to the constructor as SnsPublishProps.
messageRequiredTaskInputThe message you want to send. With the exception of SMS, messages must be UTF-8 encoded strings and at most 256 KB in size. For SMS, each message can contain up to 140 characters.
topicRequiredITopicThe SNS topic that the task will publish to.
messageAttributesOptional{ [key: string]: MessageAttribute }Add message attributes when publishing. These attributes carry additional metadata about the message and may be used for subscription filters.
Default: {}
messageDeduplicationIdOptionalstringThis parameter applies only to FIFO topics. Every message must have a unique MessageDeduplicationId, which is a token used for deduplication of sent messages. If a message with a particular MessageDeduplicationId is sent successfully, any message sent with the same MessageDeduplicationId during the 5-minute deduplication interval is treated as a duplicate. If the topic has ContentBasedDeduplication set, the system generates a MessageDeduplicationId based on the contents of the message. Your MessageDeduplicationId overrides the generated one.
Default: - Not used for standard topics, required for FIFO topics with ContentBasedDeduplication disabled.
messageGroupIdOptionalstringThis parameter applies only to FIFO topics. The MessageGroupId is a tag that specifies that a message belongs to a specific message group. Messages that belong to the same message group are processed in a FIFO manner (however, messages in different message groups might be processed out of order). Every message must include a MessageGroupId.
Default: - Not used for standard topics, required for FIFO topics.
messagePerSubscriptionTypeOptionalbooleanSend different messages for each transport protocol. For example, you might want to send a shorter message to SMS subscribers and a more verbose message to email and SQS subscribers. Your message must be a JSON object with a top-level JSON key of "default" with a value that is a string You can define other top-level keys that define the message you want to send to a specific transport protocol (i.e. "sqs", "email", "http", etc)
Default: false
subjectOptionalstringUsed as the "Subject" line when the message is delivered to email endpoints. This field will also be included, if present, in the standard JSON messages delivered to other endpoints.
Default: - No subject
TaskStateBasePropsresultPathOptionalinherited from TaskStateBasePropsstringJSONPath expression to indicate where to inject the state's output. May also be the special value JsonPath.DISCARD, which will cause the state's input to become its output.
Default: $
resultSelectorOptionalinherited from TaskStateBaseProps{ [key: string]: any }The JSON that will replace the state's raw result and become the effective result before ResultPath is applied. You can use ResultSelector to create a payload with values that are static or selected from the state's raw result.
Default: - None
StateBasePropscommentOptionalinherited from StateBasePropsstringA comment describing this state.
Default: No comment
queryLanguageOptionalinherited from StateBasePropsQueryLanguageThe name of the query language used by the state. If the state does not contain a `queryLanguage` field, then it will use the query language specified in the top-level `queryLanguage` field.
Default: - JSONPath
stateNameOptionalinherited from StateBasePropsstringOptional name for this state.
Default: - The construct ID will be used as state name
TaskStateBaseOptionscredentialsOptionalinherited from TaskStateBaseOptionsCredentialsCredentials for an IAM Role that the State Machine assumes for executing the task. This enables cross-account resource invocations.
Default: - None (Task is executed using the State Machine's execution role)
heartbeatOptionalDeprecatedinherited from TaskStateBaseOptionsDurationTimeout for the heartbeat.
Default: - None
Deprecated: use `heartbeatTimeout`
heartbeatTimeoutOptionalinherited from TaskStateBaseOptionsTimeoutTimeout for the heartbeat. [disable-awslint:duration-prop-type] is needed because all props interface in aws-stepfunctions-tasks extend this interface
Default: - None
integrationPatternOptionalinherited from TaskStateBaseOptionsIntegrationPatternAWS Step Functions integrates with services directly in the Amazon States Language. You can control these AWS services using service integration patterns. Depending on the AWS Service, the Service Integration Pattern availability will vary.
Default: - `IntegrationPattern.REQUEST_RESPONSE` for most tasks.
`IntegrationPattern.RUN_JOB` for the following exceptions:
`BatchSubmitJob`, `EmrAddStep`, `EmrCreateCluster`, `EmrTerminationCluster`, and `EmrContainersStartJobRun`.
taskTimeoutOptionalinherited from TaskStateBaseOptionsTimeoutTimeout for the task. [disable-awslint:duration-prop-type] is needed because all props interface in aws-stepfunctions-tasks extend this interface
Default: - None
timeoutOptionalDeprecatedinherited from TaskStateBaseOptionsDurationTimeout for the task.
Default: - None
Deprecated: use `taskTimeout`
AssignableStateOptionsassignOptionalinherited from AssignableStateOptions{ [key: string]: any }Workflow variables to store in this step. Using workflow variables, you can store data in a step and retrieve that data in future steps.
Default: - Not assign variables
JsonPathCommonOptionsinputPathOptionalinherited from JsonPathCommonOptionsstringJSONPath expression to select part of the state to be the input to this state. May also be the special value JsonPath.DISCARD, which will cause the effective input to be the empty object {}.
Default: $
outputPathOptionalinherited from JsonPathCommonOptionsstringJSONPath expression to select part of the state to be the output to this state. May also be the special value JsonPath.DISCARD, which will cause the effective output to be the empty object {}.
Default: $
JsonataCommonOptionsoutputsOptionalinherited from JsonataCommonOptionsanyUsed to specify and transform output from the state. When specified, the value overrides the state output default. The output field accepts any JSON value (object, array, string, number, boolean, null). Any string value, including those inside objects or arrays, will be evaluated as JSONata if surrounded by {% %} characters. Output also accepts a JSONata expression directly.
Default: - $states.result or $states.errorOutput
Our bi-weekly newsletter teaches hands-on AWS fundamentals. No certification fluff - just practical knowledge.
Subscribe to Newsletteraws-stepfunctions-tasks