# Deploying Keycloak on AWS EKS Fargate

**URL:** <https://forum.keycloak.org/t/deploying-keycloak-on-aws-eks-fargate/775>\
**Category:** Getting advice\
**Created:** [December 23, 2019, 3:18pm UTC](https://forum.keycloak.org/t/deploying-keycloak-on-aws-eks-fargate/775 "2019-12-23T15:18:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![asierg95](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@asierg95](https://forum.keycloak.org/u/asierg95)\
**Post date:** [December 23, 2019, 3:18pm UTC](https://forum.keycloak.org/t/deploying-keycloak-on-aws-eks-fargate/775/1 "2019-12-23T15:18:23Z")

</div>

I have tried to deploy Keycloak, when I access via the ALB ingress it returns “503 Service Temporarily Unavailable”. I have try the same deployment on my local Kubernetes and it works fine. So it is a bug of Keycloak with AWS.

Also I see that the keycloak pods restarts after some time running.  
Is it necessary to configure something different when deploying to AWS?

Thanks

---

<div class="post-metadata">

**Author:** ![asierg95](https://avatars.discourse-cdn.com/v4/letter/a/d9b06d/32.png) [@asierg95](https://forum.keycloak.org/u/asierg95)\
**Post date:** [January 3, 2020, 7:27am UTC](https://forum.keycloak.org/t/deploying-keycloak-on-aws-eks-fargate/775/2 "2020-01-03T07:27:09Z")

</div>

Solved adding more memory to the container.