Install aws CLI, kubectl and eksctl

- Create an eks cluster
eksctl create cluster --name my-cluster --region <region-code>
Note: we are using my-cluster in the following sections so you need to replace it if named different.

- Associate OIDC provider with the cluster
eksctl utils associate-iam-oidc-provider --cluster my-cluster --approve

 - Download an IAM policy that allows the AWS Load Balancer Controller to make calls to AWS APIs on your behalf and attach it to the IAM role:
curl -o tmp_iam_policy.json https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.4.4/docs/install/iam_policy.json

- create IAM policy with the above policy document
aws iam create-policy --policy-name AWSLoadBalancerControllerIAMPolicy --policy-document file://tmp_iam_policy.json



-  create a service account named aws-load-balancer-controller in the kube-system namespace for the AWS Load Balancer Controller
[nuxeo@ip-172-31-23-102 ~]$ eksctl create iamserviceaccount \
> --cluster=my-cluster \
> --namespace=kube-system \
> --name=aws-load-balancer-controller \
> --attach-policy-arn=<[policy arn from the policy cerated in step before this one> \
> --override-existing-serviceaccounts \
> --approve

- get the role created
eksctl get iamserviceaccount --cluster my-cluster --name aws-load-balancer-controller --namespace kube-system

After this you can use any mechanism to access the cluster services. We used AWS ALB and NgInx ingress controller to run tests. The error is seen more in the NgInx case
and this could be due to the fact it has more users on it.

To use AWS ALB do this:
 - Add Helm repo and TargetGroupBinding custom resource definitions (CRDs) AWS  LBC
	helm repo add eks https://aws.github.io/eks-charts
	kubectl apply -k "github.com/aws/eks-charts/stable/aws-load-balancer-controller//crds?ref=master"

 - Install AWS LBC using helm:
 

helm install aws-load-balancer-controller eks/aws-load-balancer-controller \
>     --set clusterName=my-cluster \
> --set serviceAccount.create=false \
> --set region=<your-region> \
> --set vpcId=<your_vpc> \
> --set serviceAccount.name=aws-load-balancer-controller \
> -n kube-system


If you want to use NgInx controller use this https://www.nginx.com/blog/deploying-nginx-ingress-controller-on-amazon-eks-how-we-tested/ or the easier way
https://blog.saeloun.com/2023/03/21/setup-nginx-ingress-aws-eks/

You need to add these configuration items to see web ui without breaks https://doc.nuxeo.com/nxdoc/http-and-https-reverse-proxy-configuration/ I don't think 
this setup has anything to do with the previewer breaking but might prevent you doing rapid tests.

Configure S3 to allow the role created by the 'eksctl create iamserviceaccount' to access S3 and configure CORS for S3 as documented in Nuxeo documentation.

Once this is done you can install Nuxeo with helm chart or other means. To install with Helm chart https://github.com/nuxeo/nuxeo-helm-chart or otherwise.