- 最新
- 最多得票
- 最多評論
The issue might stem from an incomplete definition in your mock configuration file. If you haven't specified mocked service integration responses in the file, Step Functions Local will attempt to invoke the actual AWS service integration using the ARN provided in your state machine definition.
For instance, if your state machine includes a task with the resource ARN for an AWS CodeBuild project (arn:aws:states:::codebuild:startBuild.sync), and there's no mocked response for this task in the configuration file, Step Functions Local will try to start an actual build using the CodeBuild service. This explains the error message you're encountering: The provided ARN 'arn:aws:states:us-east-1:123456789012:codebuild:startBuild.sync' is invalid. because the mocked service integration responses were not found.
Try to check the Key sources to properly construct your mock configuration file.
Key sources:
相關內容
- 已提問 6 個月前
AWS 官方已更新 1 年前- AWS 官方已更新 1 年前
Thanks for your reply - I've been working from those resources and my MockConfigFile.json already looks like so: "MockedStartBuildSuccess":{ "0": { "Return": { "StatusCode": 200 "BuildId": "testid" } } }, I am still getting the same error. If I swap this CodeBuild stage for a Lambda function the step passes. Do the return arguments need to be different for CodeBuild, or is this CodeBuild resource not supported by Step Functions Local?