Scripts run after localstack is "ready" are no longer working

I have scripts that get run that
1. Create lambdas (if they aren't present already - I make function lookup call to check this)
2. create sqs and sns related data
3. create s3 buckets

In each of these scenarios I actually first check if what I am looking to create already exists. If yes then don't run again.
This worked fine with localstack pods as I first loaded the data from the pods and then ran these scripts. How can I ensure this works with your scripts as well?

ALso instead of persisting data through lifespan of the running image, would it be easier and make sense to override the "shutdown" logic of localstack and persist at moment of shutdown?