Leveraging AppSync and Step Functions to improve your user’s form experiences via CloudFormation. https://medium.com/ready-set-code/leveraging-appsync-and-step-functions-to-improve-your-users-form-experiences-via-cloudformation-8ad5db7cd7ba #appsync #aws #stepfunctions #ux #webdev #webdevelopment #programming #dev #developer #Coding #softwaredev

StepFunctionからEKSjobを呼び出すときに詰まったところ
https://qiita.com/kisama2000/items/bffb6a8f30b80f33ee0f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
#qiita #AWS #stepfunctions #eks #EKSjob

🚀 Are you juggling numerous AWS Step Functions and need a way to monitor them all efficiently? My latest blog post guides you through creating a one-glance dashboard using CloudWatch's custom metrics and Terraform! No more manual checks - just a comprehensive, color-coded overview. 🟢🔴 Dive into the details here: https://letsmake.cloud/guardian-of-the-functions
#AWS #Terraform #DevOps #CloudMonitoring #StepFunctions

New AWS::StepFunctions::StateMachineVersion

Use the AWS::StepFunctions::StateMachineVersion resource to create multiple versions of a state machine.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-stepfunctions-statemachineversion.html #stepfunctions #cloudformation

New AWS::StepFunctions::StateMachineAlias

Use the AWS::StepFunctions::StateMachineAlias resource to create an alias that routes traffic to one or two versions of the same state machine.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-stepfunctions-statemachinealias.html #stepfunctions #cloudformation

My triumphant return to The New Stack: There's been a resumption of the debate among #infrastructure software #developers over whether decoupling an organization's functionality into #microservices in the name of #scalability reduces complexity or re-introduces it. This happened when Amazon Prime Video engineers made an architectural decision, and chronicled it in their blog. For a streaming video monitoring function, they moved _away_ from microservices, they said, and back toward a #monolithic architecture, for purposes of simplicity, speed, performance, and cost reduction.

Before long, the whole debate fired up again: Microservices only buys you so much scalability, some said, but eventually the complexity of its messaging between services eats any speed gains you had at the start.

At least that's what Prime Video's engineers appeared to be saying. But a close examination of their situation by world-class experts, including from Amazon Web Services (AWS), revealed that the devil was lurking outside the details after all and out in the open where we should have seen him: Yes, they had consolidated some #StepFunctions, but in so doing, they actually went the other direction. They made a microservice; the blog's author simply didn't realize it.

So what was this debate truly about, then? Do we not know a monolith when we see it anymore? Are we so quick to take sides in a debate that we've lost track of what we're actually arguing about?

No, that wasn't a digression. I'm still talking about #cloudcomputing infrastructure.

Anyway, do take some time today to read this article, which features an all-star cast including Donnie Berkholz @dberkholz,
Lori MacVittie from F5, David Mooter from Forrester, Laura Tacho, Ajay Nair from AWS,
@microsoft CVP
Brendan Burns, and one of the original microservices champions, Adrian Cockcroft @adrianco.

https://thenewstack.io/amazon-prime-videos-microservices-move-doesnt-lead-to-a-monolith-after-all/

I didn't know about C# Stateless library before reading Emre Mert's post. I love the idea to build my state machine with C# code. Yet, for .NET cloud native applications, I would probably rely on AWS Step Functions to manage a state machine.
https://emremert.dev/state-machine-in-microservice-design
#dotnet #statemachine #aws #stepfunctions

Yes sir! #Flutter and #Serverless meets in Prague 🙌
---
RT @PurpleLABlife
Serverless Meetups are expanding 🌍 🔥. Mark your calendars 20.4. 18:00 in Prague, Přístavní 7, Holešovice.
Speakers @FilipPyrek, @thomasankcorn and @salihgueler will be talking about #serverless, #stepfunctions #amplify #flutter and much more
Book🪑⬇️⬇️⬇️
https://www.eventbrite.com/e/serverlesslabmeetup-4-prague-edition-tickets-595945829017?aff=twitter
https://twitter.com/PurpleLABlife/status/1640766433062780971

Getting started with serverless architectures on AWS can be a real challenge. I've had to make the case for Step Functions more times than I can remember so it seemed like a good idea to write it down finally. #aws #serverless #stepfunctions #bestpractices

https://dev.to/aws-builders/avoiding-the-serverless-workflow-antipattern-2ba1

[ BLOG ] "Using AWS Application Composer to build a serviceful application"

https://it20.info/2023/02/using-aws-application-composer-to-build-a-serviceful-application/

This blog builds on a "solution" I have sketched which involves #EventBridge and #StepFunctions and show how you can use #ApplicationComposer to "stitch" it into deploy-able IaC. Nothing deep but if you are moving baby steps into Application Composer it may be worth a read.

Overall, AWS Step Functions greatly simplifies workflow tasks, however I find their service integrations very frustrating.

At creation, you can provide the ARN of another workflow in another region which is to be executed, this is FINE till you run it, and it magically replaces the region in that ARN with the current one, then attempts to start the execution resulting in "State Machine Does Not Exist". No shit sherlock... #aws #stepfunctions 😭 😭 🤦‍♂️

An #EventBridge + #StepFunctions #nocode workflow that "changes the behavior of #ECS" and registers a single task/container public IP in a #Route53 A record.

https://github.com/aws/containers-roadmap/issues/737#issuecomment-1410169740

👺 👻

#AWS #StepFunctions can invoke nested workflows asynchronously with the resource "arn:aws:states:::states:startExecution", or synchronously by appending .sync (String response) or .sync:2 (JSON response). [https://docs.aws.amazon.com/step-functions/latest/dg/connect-stepfunctions.html]
Step Functions automatically:
• hyperlinks parent and child workflows in the AWS management console
• propagates failures to parents
• propagates a single execution ID to nested workflows with the AWS_STEP_FUNCTIONS_STARTED_BY_EXECUTION_ID parameter

Hello Step Functions enthusiasts! I am happy to announce that the AWS Step Functions Workshop is now available in French!

Workshop Link: https://buff.ly/3IXbMbo

Thanks so much to Nicolas Menciere & team for leading this initiative!

#aws #stepfunctions #machinesàétats #français

My first mastodon post is an exciting one!

I've just open sourced a Chrome extension that set up a real-time sync between #AWS #StepFunctions Workflow Studio and your local ASL file.

It also preserves any DefinitionSubstitutions you might have.

Instructions in the readme: https://github.com/ljacobsson/sfn-workflow-studio-sync

#serverless

Moving from synchronous #apigw to fat #lambda that calls in parallel #eventbridge #dynamodb #s3 #stepfunctions #sqs #sns to fully #eda lambda that calls just #dynamodb and fan-out with #sns gave me just an 8% (p99) increase in term of scalability. #eda with #eventbridge is the same as the fatty 😭

This is a massive release, we've added support for role assumption (i.e. cross account) actions to AWS Step Functions.

https://aws.amazon.com/about-aws/whats-new/2022/11/simplify-cross-account-access-aws-services-step-functions/

This will eliminate a ton of glue Lambda functions which is great news for customers.

Of course it rather negates one of my blog posts! Typical :)

https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/launch-a-codebuild-project-across-aws-accounts-using-step-functions-and-a-lambda-proxy-function.html

#aws #StepFunctions

This is a welcome release! #AWS #StepFunctions now supports cross-account actions.

It uses role assumption in the target account, so it works for any resource, not just those which support resource policies.

https://aws.amazon.com/about-aws/whats-new/2022/11/simplify-cross-account-access-aws-services-step-functions/