Please support aws-stepfunctions-local 100%

1

Why did AWS decide not to officially support aws-stepfunctions-local docker image anymore ? As stated here:

Step Functions Local is unsupported and here and here

And on docker hub the image is archived. How you can archive a 5M+ image?

Can you tell me real alternatives for local testing and CICD testing? We have a lot of integration tests still relying on this docker image and we don't want that it deprecates more in future.

Can you give me a hint to whom we should talk to, for further support on this topic?

1 Answer
-1

AWS has indeed decided not to officially support the aws-stepfunctions-local Docker image anymore. While the exact reasons for this decision are not explicitly stated in the available sources, it's important to understand that Step Functions Local was primarily intended as a testing tool and not for production use.

For local testing and CI/CD testing alternatives, you have a few options to consider:

  1. Third-party solutions: AWS suggests considering third-party solutions that emulate Step Functions for testing purposes. These might offer more robust and maintained alternatives to Step Functions Local.

  2. Mocked service integrations: You can use mocked service integrations for testing your state machines. This involves creating a mock configuration file that defines mocked responses and test cases for your state machine executions. This approach allows you to test your workflows without making actual service calls.

  3. AWS SAM with local Lambda: You can use AWS Serverless Application Model (SAM) in combination with a local version of AWS Lambda for testing. This setup allows you to configure and test your state machines on your local computer.

  4. EventBridge with API destinations: For scenarios involving external API calls, you might consider using Amazon EventBridge with API destinations. This can be particularly useful for handling authentication requirements like Bearer tokens.

As for getting further support on this topic, the best approach would be to reach out to AWS Support directly if you have an AWS support plan. They would be best positioned to provide guidance on migration strategies and potential alternatives that align with your specific use case.

Alternatively, you could post your concerns and questions on AWS re:Post, which is a community-driven Q&A platform where AWS experts and community members can provide insights and suggestions.

Given that Step Functions Local is no longer officially supported, it's advisable to start planning a migration strategy for your integration tests. Consider evaluating the suggested alternatives and determine which approach best fits your testing requirements and workflow.
Sources
Using mocked service integrations for testing in Step Functions Local - AWS Step Functions
Testing state machines with Step Functions Local (unsupported) - AWS Step Functions
How to mock CodeBuild with Step Functions Local | AWS re:Post
Step Function - Call Third party API - Bearer Token | AWS re:Post

profile picture
answered 22 days ago
profile pictureAWS
EXPERT
reviewed 22 days ago
  • Can you please help me to understand the answer? Does "not for production use" mean that I should not use it for CICD testing while deploying to a production environment in AWS? I know that other teams in my organization are also quite unhappy with this situation. Why is it not supported anymore? Can someone bring more light into this? Can you propose some good alternatives?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions