1

I am testing out a flow where I use one Step Function to invoke another. The child State Machine will be used to invoke a lambda for data processing.

To bear this out, I am creating very simple objects via the web console, however, when attempting to run the parent process, I am getting the following error

User: arn:aws:sts::xxxxxxx:assumed-role/StepFunctions-ETL_POC-role-xxxx/step-functions-express-xxxx is not authorized to access this resource (Service: AWSStepFunctions; Status Code: 400; Error Code: AccessDeniedException; 

I have played around by adding the Step Functions Full Access managed policy to the IAM role, but that didn't seem to do the trick.

What am I missing?

4
  • 1
    Can you update your question to include a sanitized version of your workflow definitions (ASL) as well as the policies for the execution role on your parent state machine? Commented Apr 17, 2023 at 1:03
  • Yes, I will later on today. Thanks for reaching out. Commented Apr 17, 2023 at 19:45
  • Oh my gosh. Thank you for asking me to walk through that process! I could have sworn that I specified my child SFN's ARN, but it was the boiler plate setup; the ARN was generic and not pointing at my actual Child SFN. Yikes. Thanks again. Commented Apr 17, 2023 at 22:49
  • 1
    Cool, glad you were able to get it fixed! Commented Apr 18, 2023 at 13:28

1 Answer 1

2

The issue was that the definition of the State Machine was using the default placeholder text. I was attempting to do everything via the web console and never once thought to check if I had properly referenced the ARN.

This was only found after the first comment from Justin above.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.