[{"data":1,"prerenderedAt":98},["ShallowReactive",2],{"content-svc-step-functions-guides-integrating-step-functions-with-containerized-workloads-40-external-system-integration":3},{"markdown":4,"frontMatterAttributes":5,"bodyRaw":16,"menu":17,"menuType":95,"isCollapseableMenu":20,"nextDocItem":47,"previousDocItem":29,"contributorPaths":96,"contentName":19,"slug":46,"readingTime":25},"\u003Cp>Business workflows can extend beyond AWS. They can invoke legacy services deployed in on-premise systems and third party APIs. This chapter gives you an overview of how Step Functions integrates with services and systems outside AWS. \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Third party API integration\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>With \u003Ca href=\"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-third-party-apis.html\">third party API integration\u003C\u002Fa>, you can invoke any publicly available API such as Salesforce and Stripe in your workflows. This is accomplished by using a HTTP task state in your workflow. If your containerized workload is exposed as public API, you can use this integration to directly invoke them.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Activity Integration\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconcepts-activities.html\">Activities\u003C\u002Fa> are a Step Functions feature that enables you to process messages by an external worker running in environments such as Amazon EKS, on-premise servers etc. You can think of activities as a managed queue where you can send tasks for external processing through an activity task, and these tasks can be consumed and processed by a remote worker running basically anywhere.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"\u002Fassets\u002Fexternal\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002Fassets\u002Factivity.png\" alt=\"image\">\u003C\u002Fp>\n\u003Cp>You will learn more about using \u003Ccode>Activities\u003C\u002Fcode> to integrate with workloads deployed outside AWS in the coming chapters.\u003C\u002Fp>\n",{"title":6,"order":7,"resources":8},"Connecting to systems outside AWS",40,[9,13],{"link":10,"text":11,"type":12},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-third-party-apis.html","Third party API integration","documentation",{"link":14,"text":15,"type":12},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconcepts-activities.html","Activity Integration","Business workflows can extend beyond AWS. They can invoke legacy services deployed in on-premise systems and third party APIs. This chapter gives you an overview of how Step Functions integrates with services and systems outside AWS. \n\n**Third party API integration**\n\nWith [third party API integration](https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-third-party-apis.html), you can invoke any publicly available API such as Salesforce and Stripe in your workflows. This is accomplished by using a HTTP task state in your workflow. If your containerized workload is exposed as public API, you can use this integration to directly invoke them.\n\n**Activity Integration**\n\n[Activities](https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconcepts-activities.html) are a Step Functions feature that enables you to process messages by an external worker running in environments such as Amazon EKS, on-premise servers etc. You can think of activities as a managed queue where you can send tasks for external processing through an activity task, and these tasks can be consumed and processed by a remote worker running basically anywhere.\n\n![image](\u002Fassets\u002Fexternal\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002Fassets\u002Factivity.png)\n\nYou will learn more about using `Activities` to integrate with workloads deployed outside AWS in the coming chapters.",[18],{"title":19,"collapsible":20,"isCollapsed":20,"content":21},"Integrating Step Functions with containerized workloads",false,[22,29,40,47,60,74,90],{"title":23,"order":24,"time":25,"path":26,"id":27,"link":28},"Introduction",10,"1 min","10-introduction","10-introduction.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F10-introduction",{"title":30,"order":31,"resources":32,"time":36,"path":37,"id":38,"link":39},"Service Integration patterns and AWS service integrations ",20,[33],{"link":34,"text":35,"type":12},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-to-resource.html","Service integration patterns","2 min","20-patterns","20-patterns.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F20-patterns",{"title":6,"order":7,"resources":41,"time":25,"path":44,"id":45,"link":46},[42,43],{"link":10,"text":11,"type":12},{"link":14,"text":15,"type":12},"40-external-system-integration","40-external-system-integration.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F40-external-system-integration",{"title":48,"order":49,"resources":50,"time":36,"path":57,"id":58,"link":59},"Run a job Integration",50,[51,54],{"link":52,"text":53,"type":12},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-ecs.html","Manage Amazon ECS or Fargate Tasks with Step Functions",{"link":55,"text":56,"type":12},"https:\u002F\u002Fdocs.aws.amazon.com\u002Fstep-functions\u002Flatest\u002Fdg\u002Fconnect-eks.html","Call Amazon EKS with Step Functions","50-run-a-job","50-run-a-job.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F50-run-a-job",{"title":61,"order":62,"callout":63,"resources":66,"time":36,"path":71,"id":72,"link":73},"Wait for Callback integration",60,{"title":64,"description":64,"link":65},"Parallel video processing using AWS Fargate tasks","https:\u002F\u002Fcatalog.workshops.aws\u002Fstepfunctions\u002Fen-US\u002Fuse-cases\u002Fdata-processing\u002Fmap-ecs",[67],{"link":68,"text":69,"type":70},"https:\u002F\u002Fserverlessland.com\u002Fpatterns\u002Fsfn-ecs-sam","Sample pattern for Wait for Callback","pattern","60-callback","60-callback.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F60-callback",{"title":15,"order":75,"resources":76,"callout":83,"time":36,"path":87,"id":88,"link":89},70,[77,79],{"link":14,"text":78,"type":12},"Activities",{"link":80,"text":81,"type":82},"https:\u002F\u002Fcatalog.us-east-1.prod.workshops.aws\u002Fworkshops\u002F2a22e604-2f2e-4d7b-85a8-33b38c999234\u002Fen-US\u002Fuse-cases\u002Fmonte-carlo-simulation","Run Monte Carlo Simulation with AWS Fargate and Step Functions Activity","workshop",{"title":84,"description":85,"link":86},"Using Activities with AWS Fargate","This blog post demostrates how you can use Activities with AWS Fargate at scale.","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcontainers\u002Frun-monte-carlo-simulations-at-scale-with-aws-step-functions-and-aws-fargate\u002F","70-activity","70-activity.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F70-activity",{"title":91,"order":24,"time":25,"path":92,"id":93,"link":94},"Conclusion","80-conclusion","80-conclusion.md","\u002Fcontent\u002Fservice\u002Fstep-functions\u002Fguides\u002Fintegrating-step-functions-with-containerized-workloads\u002F80-conclusion","LIST",[97],"content\u002Fcontributors\u002Fuma-ramadoss.json",1792578874805]