# How to deploy openreplay via EKS?

**URL:** <https://forum.openreplay.com/t/how-to-deploy-openreplay-via-eks/571>\
**Category:** 🛠️ Deployment\
**Created:** [September 14, 2026, 6:42am UTC](https://forum.openreplay.com/t/how-to-deploy-openreplay-via-eks/571 "2026-09-14T06:42:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AzureLemur48](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@AzureLemur48](https://forum.openreplay.com/u/AzureLemur48)\
**Post date:** [September 14, 2026, 6:42am UTC](https://forum.openreplay.com/t/how-to-deploy-openreplay-via-eks/571/1 "2026-09-14T06:42:02Z")

</div>

I have been trying to deploy openreplay via EKS for some time now, and there are many unexpected issues popping up. the latest one I am facing is sink and storage are on seperate nodes and needs a shared EFS to function, but VPC in my clusters is not configured the way that openreplay expects it.  
Is there any way to keep sink and storage as a single node?

The hosting is done, and it lists many recordings, but I am unable to view it because the sessions themselves were never written to my S3 bucket.