aws-application-load-balancer

Redirect non www to www using ALB Ingress Controller

大城市里の小女人 提交于 2021-01-27 19:10:02
问题 I am trying to redirect a non www request to www . I checked the annotations here https://kubernetes-sigs.github.io/aws-alb-ingress-controller/guide/ingress/annotation/ but could not find specific to non www to www redirect. I already have a http to https redirect set and it's working. below is my ingress resource manifest file. apiVersion: extensions/v1beta1 kind: Ingress metadata: name: eks-learning-ingress namespace: production annotations: kubernetes.io/ingress.class: alb alb.ingress

How to set AWS ALB instead of ELB in Istio?

蹲街弑〆低调 提交于 2020-12-30 08:55:31
问题 I am trying to setup ALB load balancer instead of default ELB loadbalancer in Kubernetes AWS.The loadbalancer has to be connected to the istio ingressgateway.I looked for solutions and only found one. But the istio version mentioned is V1 and there has been so many changes in istio now.I tried to change service type to nodeport in the chart (according to the blog)but still the service comes as a Loadbalancer. Can someone mention steps how to configure ALB for istio ingressgateway? Thanks for

AWS - Unable to make API calls to EC2 server via Application Load Balancer (ALB)

白昼怎懂夜的黑 提交于 2020-08-10 19:15:10
问题 I am trying to deploy a MERN Stack app to AWS but I am kinda stuck now. Current Progress: ALB is set up with a valid SSL Certificate issued by AWS. ALB URL: https://xyz.alb.com/ Also, ALB has three listeners: a. HTTP [80] b. HTTPS [443] c. HTTPS [5000] (For accessing ec2 backend server, is this right?) EC2 instance public IP: 78.45.43.23 (Say) (I can access my server on 78.45.43.23:5000/api/) I have whitelisted, ALB, https://xyz.alb.com in my server CORS (Node) [Important]. Problem Statement:

AWS - Unable to make API calls to EC2 server via Application Load Balancer (ALB)

生来就可爱ヽ(ⅴ<●) 提交于 2020-08-10 19:14:30
问题 I am trying to deploy a MERN Stack app to AWS but I am kinda stuck now. Current Progress: ALB is set up with a valid SSL Certificate issued by AWS. ALB URL: https://xyz.alb.com/ Also, ALB has three listeners: a. HTTP [80] b. HTTPS [443] c. HTTPS [5000] (For accessing ec2 backend server, is this right?) EC2 instance public IP: 78.45.43.23 (Say) (I can access my server on 78.45.43.23:5000/api/) I have whitelisted, ALB, https://xyz.alb.com in my server CORS (Node) [Important]. Problem Statement:

AWS LoadBalancer to Listen on multiple ports

£可爱£侵袭症+ 提交于 2020-06-27 11:22:28
问题 I have a few applications running as Microservices in aws. Some of them are running on port 80 and some of them are running on port 3000. I want my ALB to listen to traffic on both ports. Then I have a ListenRules to direct the traffic to Microservices. I want to achieve something like below, Resources: LoadBalancer: Type: AWS::ElasticLoadBalancingV2::LoadBalancer Properties: Name: !Ref EnvironmentName Subnets: !Ref Subnets SecurityGroups: - !Ref SecurityGroup Tags: - Key: Name Value: !Ref

AWS LoadBalancer to Listen on multiple ports

落爺英雄遲暮 提交于 2020-06-27 11:22:15
问题 I have a few applications running as Microservices in aws. Some of them are running on port 80 and some of them are running on port 3000. I want my ALB to listen to traffic on both ports. Then I have a ListenRules to direct the traffic to Microservices. I want to achieve something like below, Resources: LoadBalancer: Type: AWS::ElasticLoadBalancingV2::LoadBalancer Properties: Name: !Ref EnvironmentName Subnets: !Ref Subnets SecurityGroups: - !Ref SecurityGroup Tags: - Key: Name Value: !Ref

Exposing kubernetes app using AWS Elastic LoadBalancer

一笑奈何 提交于 2019-12-25 18:32:42
问题 I created an internal AWS elastic application loadbalancer and in AWS console it shows its state as active. Note that I created this ALB using a jenkins job and in the job I have specified my AWS EC2 instance server which is configured as my kubernetes master. And I can see following details after the job was completed successfully. In AWS console under description, I can see below details - DNS internal-myservices-987070943.us-east-1.elb.amazonaws.com Scheme internal Type application IP