When running with >=2 container instances in AWS ECS fargate I needed to enable sticky session on my aws alb target group for services to start up. Is this a requirement? From what I read it would help in performance, but not requirement.
Correct. It is not a requirement. However, if you plan to bring instances up and down frequently (e.g. if you are bundling extensions that you update often) the performance benefit isn’t often realized.
I appreciate feedback, but maybe missing environmental variable as admin page spins on two instances. What is minimal required variables using ecs fargate against mysql database in production mode. Maybe I’m missing caching and/or proxy requirements?
One thing to note is I removed sticky session and added JGROUPS_DISCOVERY_PROTOCOL = JDBC_PING from article I read. I now get admin prompt but doesn’t feel consistent as page refresh to admin page puts me back in page spinning. What else is required
I was able to get Keycloak running via ecs fargate using S3_PING instead of JDBC PING without the use of sticky session. Closing this issue out