1 Answer
- Newest
- Most votes
- Most comments
0
Verify that the IAM user or role you are using has the necessary permissions to access resources in the EKS cluster. The cluster's aws-auth ConfigMap maps IAM identities to Kubernetes RBAC roles.
Check that pods are deployed successfully in the cluster by running kubectl get pods
Ensure the application load balancer is configured with the correct target group and security group to route traffic to the pods.
Try deploying a simple test application like the echoserver using:
apiVersion: apps/v1
kind: Deployment
...
kubectl create -f deployment.yaml
And check if you can access it at the load balancer endpoint.
Relevant content
- asked a year ago
- asked 4 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 4 months ago
Hi Blueagle, can you clarify why this was tagged with "SAP on AWS"? Is there some SAP-related context that this addresses also? If not please remove the tag; to help keep searches by others, relevant.