StepFunctionsIntegration

class aws_cdk.aws_apigateway.StepFunctionsIntegration

Bases: object

Options to integrate with various StepFunction API.

ExampleMetadata:: infused

Example:

state_machine = stepfunctions.StateMachine(self, "MyStateMachine",
    state_machine_type=stepfunctions.StateMachineType.EXPRESS,
    definition=stepfunctions.Chain.start(stepfunctions.Pass(self, "Pass"))
)

api = apigateway.RestApi(self, "Api",
    rest_api_name="MyApi"
)
api.root.add_method("GET", apigateway.StepFunctionsIntegration.start_execution(state_machine))

Static Methods

classmethod start_execution(state_machine, *, authorizer=None, headers=None, path=None, querystring=None, request_context=None, cache_key_parameters=None, cache_namespace=None, connection_type=None, content_handling=None, credentials_passthrough=None, credentials_role=None, integration_responses=None, passthrough_behavior=None, request_parameters=None, request_templates=None, timeout=None, vpc_link=None)

Integrates a Synchronous Express State Machine from AWS Step Functions to an API Gateway method.

Parameters:

state_machine (IStateMachine) –
authorizer (Optional[bool]) – If the whole authorizer object, including custom context values should be in the execution input. The execution input will include a new key authorizer: { “body”: {}, “authorizer”: { “key”: “value” } } Default: false
headers (Optional[bool]) – Check if header is to be included inside the execution input. The execution input will include a new key headers: { “body”: {}, “headers”: { “header1”: “value”, “header2”: “value” } } Default: false
path (Optional[bool]) – Check if path is to be included inside the execution input. The execution input will include a new key path: { “body”: {}, “path”: { “resourceName”: “resourceValue” } } Default: true
querystring (Optional[bool]) – Check if querystring is to be included inside the execution input. The execution input will include a new key queryString: { “body”: {}, “querystring”: { “key”: “value” } } Default: true
request_context (Union[RequestContext, Dict[str, Any], None]) – Which details of the incoming request must be passed onto the underlying state machine, such as, account id, user identity, request id, etc. The execution input will include a new key requestContext: { “body”: {}, “requestContext”: { “key”: “value” } } Default: - all parameters within request context will be set as false
cache_key_parameters (Optional[Sequence[str]]) – A list of request parameters whose values are to be cached. It determines request parameters that will make it into the cache key.
cache_namespace (Optional[str]) – An API-specific tag group of related cached parameters.
connection_type (Optional[ConnectionType]) – The type of network connection to the integration endpoint. Default: - ConnectionType.VPC_LINK if vpcLink property is configured; ConnectionType.Internet otherwise.
content_handling (Optional[ContentHandling]) – Specifies how to handle request payload content type conversions. Default: none if this property isn’t defined, the request payload is passed through from the method request to the integration request without modification, provided that the passthroughBehaviors property is configured to support payload pass-through.
credentials_passthrough (Optional[bool]) – Requires that the caller’s identity be passed through from the request. Default: Caller identity is not passed through
credentials_role (Optional[IRole]) – An IAM role that API Gateway assumes. Mutually exclusive with credentialsPassThrough. Default: A role is not assumed
integration_responses (Optional[Sequence[Union[IntegrationResponse, Dict[str, Any]]]]) – The response that API Gateway provides after a method’s backend completes processing a request. API Gateway intercepts the response from the backend so that you can control how API Gateway surfaces backend responses. For example, you can map the backend status codes to codes that you define.
passthrough_behavior (Optional[PassthroughBehavior]) – Specifies the pass-through behavior for incoming requests based on the Content-Type header in the request, and the available mapping templates specified as the requestTemplates property on the Integration resource. There are three valid values: WHEN_NO_MATCH, WHEN_NO_TEMPLATES, and NEVER.
request_parameters (Optional[Mapping[str, str]]) – The request parameters that API Gateway sends with the backend request. Specify request parameters as key-value pairs (string-to-string mappings), with a destination as the key and a source as the value. Specify the destination by using the following pattern integration.request.location.name, where location is querystring, path, or header, and name is a valid, unique parameter name. The source must be an existing method request parameter or a static value. You must enclose static values in single quotation marks and pre-encode these values based on their destination in the request.
request_templates (Optional[Mapping[str, str]]) – A map of Apache Velocity templates that are applied on the request payload. The template that API Gateway uses is based on the value of the Content-Type header that’s sent by the client. The content type value is the key, and the template is the value (specified as a string), such as the following snippet:: { “application/json”: “{ "statusCode": 200 }” }
timeout (Optional[Duration]) – The maximum amount of time an integration will run before it returns without a response. Must be between 50 milliseconds and 29 seconds. Default: Duration.seconds(29)
vpc_link (Optional[IVpcLink]) – The VpcLink used for the integration. Required if connectionType is VPC_LINK

Return type:

AwsIntegration

Example:

state_machine = stepfunctions.StateMachine(self, "MyStateMachine",
    state_machine_type=stepfunctions.StateMachineType.EXPRESS,
    definition=stepfunctions.Chain.start(stepfunctions.Pass(self, "Pass"))
)

api = apigateway.RestApi(self, "Api",
    rest_api_name="MyApi"
)
api.root.add_method("GET", apigateway.StepFunctionsIntegration.start_execution(state_machine))