First off, I want to say that the n8n team clearly emphasizes how easy this can be. That being said, AWS really likes to make things over-complicated. I’m currently hosting n8n on an EC2 Docker container in ECS but I can’t get the data to persist after restarting the container. I’ve tried a lot of different combinations in the “Volumes” section and in the container config in my task definition and I do get his encouraging output in the CloudFront logs:
Alas, when I restart the container, I have no data persistence. When I log into the CentOS server that this is running inside, I can see that Docker has the container running and that the volume I made is mounted.
What’s confusing is that even though the previous log message says that the /home/node/.n8n/config file was created, the /home/node directory is empty even after I did a “mkdir /home/node/.n8n”
My guess is that this is a stupid AWS problem as it usually is but I also may be totally missing something.
Any help would be greatly appreciated!