Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 591 discussion

"The company needs to route incoming requests to the appropriate microservices" In Kubernetes world, this would be called an Ingress Service so it will need B https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.6/ https://kubernetes.io/docs/concepts/services-networking/ingress/

Not D because - even with an API gateway you'd need an ALB or ELB (so B+D would work, but D alone does not) - you would use AWS API Gateway Controller (not "Amazon API Gateway") to create the API Gateway

Option B: Use the AWS Load Balancer Controller to provision an Application Load Balancer (ALB). Explanation: The AWS Load Balancer Controller can provision ALBs, which operate at the application layer (Layer 7). ALBs support advanced routing capabilities such as routing based on HTTP paths or hostnames. This makes ALBs well-suited for routing requests to different microservices based on URL paths or domains. This approach integrates well with Kubernetes and is a common pattern for microservices architectures.

ALB is cost-effectively

ALB is considered as expensive than API Gateway, particularly on higher load. If you do not need any specific functionalities of API Gateway so you must choose ALB because it will be cheaper.

API Gateway has a pricing model that includes a cost per API call, and depending on the volume of requests, this could potentially be more expensive than using an Application Load Balancer.

Routing requests to the appr. microserv. can easily be done with ALB and ingress. The ingress handles routing rules to the micro.serv. With answer D you wil still need ALB or NLB as can be seen in the pics of https://aws.amazon.com/blogs/containers/integrate-amazon-api-gateway-with-amazon-eks/ or https://aws.amazon.com/blogs/containers/microservices-development-using-aws-controllers-for-kubernetes-ack-and-amazon-eks-blueprints/ so that is not the most cost-effectively.

Both ALB and API gateway can be used to route traffic to the microservices, but the question seeks the most 'cost effective' option. You are charged for each hour or partial hour that an Application Load Balancer is running, and the number of Load Balancer Capacity Units (LCU) used per hour. With Amazon API Gateway, you only pay when your APIs are in use. I say API gateway is the best option for this case.

AWS Load Balancer Controller: The AWS Load Balancer Controller is a Kubernetes controller that makes it easy to set up an Application Load Balancer (ALB) or Network Load Balancer (NLB) for your Amazon EKS clusters. It simplifies the process of managing load balancers for applications running on EKS. Application Load Balancer (ALB): ALB is a Layer 7 load balancer that is capable of routing requests based on content, such as URL paths or hostnames. This makes it suitable for routing requests to different microservices based on specific criteria. Cost-Effectiveness: ALB is typically more cost-effective than an NLB, and it provides additional features at the application layer, which may be useful for routing requests to microservices based on specific conditions. Option D: Amazon API Gateway is designed for creating, publishing, and managing APIs. While it can integrate with Amazon EKS, it may be more feature-rich and complex than needed for simple routing to microservices within an EKS cluster.

API Gateway provides an entry point to your microservices. https://aws.amazon.com/blogs/containers/integrate-amazon-api-gateway-with-amazon-eks/

B is correct, it is a required before exposing through api gateway

B: is correct. For EKS, use application load balancer to expose microservices

Routing to ms in k8s -> Ingresses -> Ingress Controller -> AWS Load Balancer Controller https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.6/

Microservices--> API--> API GW

D. Use Amazon API Gateway to connect the requests to Amazon EKS.

API Gateway is a fully managed service that makes it easy for you to create, publish, maintain, monitor, and secure APIs at any scale. API Gateway provides an entry point to your microservices.

https://aws.amazon.com/blogs/containers/microservices-development-using-aws-controllers-for-kubernetes-ack-and-amazon-eks-blueprints/