aws-load-balancer

问题 I am trying to expose a service to the outside world using the loadBalancer type service. For that, i have followed this doc https://aws.amazon.com/premiumsupport/knowledge-center/eks-kubernetes-services-cluster/ My loadbalancer.yaml looks like this apiVersion: v1 kind: Service metadata: name: nginx-service spec: type: LoadBalancer selector: app: nginx ports: - protocol: TCP port: 80 targetPort: 80 But the load balancer is not creating as expected I am getting the following error Warning

问题 I am trying to expose a service to the outside world using the loadBalancer type service. For that, i have followed this doc https://aws.amazon.com/premiumsupport/knowledge-center/eks-kubernetes-services-cluster/ My loadbalancer.yaml looks like this apiVersion: v1 kind: Service metadata: name: nginx-service spec: type: LoadBalancer selector: app: nginx ports: - protocol: TCP port: 80 targetPort: 80 But the load balancer is not creating as expected I am getting the following error Warning

问题 I am trying to expose a service to the outside world using the loadBalancer type service. For that, i have followed this doc https://aws.amazon.com/premiumsupport/knowledge-center/eks-kubernetes-services-cluster/ My loadbalancer.yaml looks like this apiVersion: v1 kind: Service metadata: name: nginx-service spec: type: LoadBalancer selector: app: nginx ports: - protocol: TCP port: 80 targetPort: 80 But the load balancer is not creating as expected I am getting the following error Warning

问题 I am trying to expose a service to the outside world using the loadBalancer type service. For that, i have followed this doc https://aws.amazon.com/premiumsupport/knowledge-center/eks-kubernetes-services-cluster/ My loadbalancer.yaml looks like this apiVersion: v1 kind: Service metadata: name: nginx-service spec: type: LoadBalancer selector: app: nginx ports: - protocol: TCP port: 80 targetPort: 80 But the load balancer is not creating as expected I am getting the following error Warning

问题 While certificate manager UI shows my imported certificated with status "issued" , when trying to use it from an ELB (application lb) I get: " no certificates available " (the POST request to the api returns with empty list) Also when I run aws acm list-certificates --max-items 10 I don't get the imported certificate , only my second (Not imported) one Any ideas what's wrong here? is there a setting on the imported certificate I should be configuring? 回答1: I've got only half answer here: but

问题 I have set up a a cluster, with 1 service containing 1 task. The task contains 2 docker containers. One for my UI (post 3000 ) and one for my API (port 8080 ). I can access both ports via [public-ip]:3000 and [public-ip]:8080 . I then set up an Application Load Balancer that points to the service. It points these target group : https://pasteboard.co/JFQfvD9.png So now I CAN reach the UI via the DNS name for the load balancer but the API calls that the application makes always fail with 404 .

问题 I have set up a a cluster, with 1 service containing 1 task. The task contains 2 docker containers. One for my UI (post 3000 ) and one for my API (port 8080 ). I can access both ports via [public-ip]:3000 and [public-ip]:8080 . I then set up an Application Load Balancer that points to the service. It points these target group : https://pasteboard.co/JFQfvD9.png So now I CAN reach the UI via the DNS name for the load balancer but the API calls that the application makes always fail with 404 .

问题 In Short I've managed to run Traefik locally and on AWS ECS but now I'm wondering how should I setup some sort of load balancing to make my two services with random IPs available to the public. My current setup on ECS [Internet] | [Load balancer on port 443 + ALB Security group on 443] | [Target group on port 443 + Security group from *any* port] | [cluster] | [service1 container ports "0:5000"] While this works, I'd now like to add another container, eg. service2 also with random ports eg 0

问题 Ideally, I'd like to lock down my ALB so that it can only be accessed by API Gateway. I've looked into whether I can associate API gateway with an Inbound Rule - however, I have found that API Gateway cannot be associated with an IP address, or a security group. I've also looked into an Internal facing ALB, but I've been unable to get these working as VPC link only supports NLB. Any help will be greatly appreciated - I've been looking in the Gateway Settings but cannot find this option. What

问题 Ideally, I'd like to lock down my ALB so that it can only be accessed by API Gateway. I've looked into whether I can associate API gateway with an Inbound Rule - however, I have found that API Gateway cannot be associated with an IP address, or a security group. I've also looked into an Internal facing ALB, but I've been unable to get these working as VPC link only supports NLB. Any help will be greatly appreciated - I've been looking in the Gateway Settings but cannot find this option. What