<p>Issue is resolved by updating the subnet to a private subnet which uses a nat gateway instead of a public subnet with an internet gateway. <a href="https://stackoverflow.com/questions/45017329/why-doesnt-my-lambda-function-start-an-execution-on-an-aws-state-machine">This</a> SO post lead my in the right direction.</p>

CC BY-SA 4.0
2020-02-21T01:48:30.547Z
2020-02-21T01:48:30.547Z
joshk132
<p>I recently moved my development account away from my prod one, everything seemed fine except I have a service that runs a lambda to start a step function - not ideal but used to work.</p>

<p>My issue comes in that I am now able to run everything up to and including the execute step function from the npm package provided by aws. I have checked and the account ID is updated in the arn of the step function/machine. I see in my cloudwatch logs that it is timing out after 30 seconds (had a 6 but changed to test).</p>

<p>What are some possible causes of a step function not executing after an account change with no code changes other than the account ID update.</p>

<amazon-web-services><node.js><step-functions>
Unable to start step function after account move
joshk132
# Unable to start step function after account move

(Asked by: username_0 on 2020-02-21)

I recently moved my development account away from my prod one, everything seemed fine except I have a service that runs a lambda to start a step function - not ideal but used to work.

My issue comes in that I am now able to run everything up to and including the execute step function from the npm package provided by aws. I have checked and the account ID is updated in the arn of the step function/machine. I see in my cloudwatch logs that it is timing out after 30 seconds (had a 6 but changed to test).

What are some possible causes of a step function not executing after an account change with no code changes other than the account ID update.

**Tags:** amazon-web-services, node.js, step-functions


---

## 1 answers

### Answer by username_0 on 2020-02-21. Score: 1

Issue is resolved by updating the subnet to a private subnet which uses a nat gateway instead of a public subnet with an internet gateway. [This](https://stackoverflow.com/questions/45017329/why-doesnt-my-lambda-function-start-an-execution-on-an-aws-state-machine) SO post lead my in the right direction.


---

