We are currently running our app on the following stack:
AWS ECS -> Fargate -> RDS DB -> Media on EFS
We are struggling with auto scaling our ECS pods. The backend turns white and is unusable.
Plus, media transfer via Usync exporter/ Usync Publisher and even manually, is causing data integrity issues. These errors usually cause the entire app to crash and show 503 error.
Is someone here running their Umbraco on ECS and can explain their architecture / what might be the issue with our architecture?
I've been closely following the threads started by Hadar and Dekel and wanted to emphasize that this is not an isolated issue. It seems that hosting Umbraco on AWS ECS is presenting a set of challenges that many of us are grappling with. These problems are severe enough that they are causing application crashes and severe data integrity concerns.
Key Challenges:
Unpredictable Auto Scaling: The behavior of auto scaling on ECS, especially with Umbraco back-office operations, is erratic. This leads to the backend going blank and becoming inoperative. It's not just about tuning metrics; there seems to be a deeper underlying issue.
Data Integrity with uSync: Data integrity is paramount. With both manual transfers and using tools like uSync, we're seeing discrepancies. This is leading to application crashes which is highly alarming.
503 Errors: These errors are more frequent than they should be. For a platform as robust as AWS and a CMS as reliable as Umbraco, it's puzzling and concerning.
If multiple members in our community, with possibly varied setups, are encountering such challenges, it points to systemic issues that need addressing.
I urge anyone with experience, insights, or even similar concerns to weigh in. It's crucial for our community to come together, shed light on these issues, and work towards a solution. Additionally, if we gather enough collective insights, we could even approach AWS or the Umbraco team for more specialized assistance.
Thank you, and looking forward to a proactive discussion.
Umbraco AWS ECS hosting
We are currently running our app on the following stack: AWS ECS -> Fargate -> RDS DB -> Media on EFS
We are struggling with auto scaling our ECS pods. The backend turns white and is unusable. Plus, media transfer via Usync exporter/ Usync Publisher and even manually, is causing data integrity issues. These errors usually cause the entire app to crash and show 503 error.
Is someone here running their Umbraco on ECS and can explain their architecture / what might be the issue with our architecture?
Thank you in advance, Hadar
I'm having a similar issue, would love to hear some answers as well
Hello all,
I've been closely following the threads started by Hadar and Dekel and wanted to emphasize that this is not an isolated issue. It seems that hosting Umbraco on AWS ECS is presenting a set of challenges that many of us are grappling with. These problems are severe enough that they are causing application crashes and severe data integrity concerns.
Key Challenges:
Unpredictable Auto Scaling: The behavior of auto scaling on ECS, especially with Umbraco back-office operations, is erratic. This leads to the backend going blank and becoming inoperative. It's not just about tuning metrics; there seems to be a deeper underlying issue.
Data Integrity with uSync: Data integrity is paramount. With both manual transfers and using tools like uSync, we're seeing discrepancies. This is leading to application crashes which is highly alarming.
503 Errors: These errors are more frequent than they should be. For a platform as robust as AWS and a CMS as reliable as Umbraco, it's puzzling and concerning.
If multiple members in our community, with possibly varied setups, are encountering such challenges, it points to systemic issues that need addressing.
I urge anyone with experience, insights, or even similar concerns to weigh in. It's crucial for our community to come together, shed light on these issues, and work towards a solution. Additionally, if we gather enough collective insights, we could even approach AWS or the Umbraco team for more specialized assistance.
Thank you, and looking forward to a proactive discussion.
is working on a reply...