aws-elb

AWS Fargate - Application load balancer(ELB) shows unhealthy targets with error “Health checks failed with these codes: [502]”

由 安稳与你 提交于 2020-12-15 04:39:25
问题 My app is running on port 3000 and web context is /app, so "http://host:3000/app/index.html" successfully returns index.html page running the app locally. Load balancer(public) listens on port 80 and forwards traffic to targets on port 3000. AWS Fargate - task definition has host and container port mapped to port 3000. - tasks are shown as RUNNING and status HEALTHY but eventually stops because ELB health checks fails. And i am able to see my app start up logs in cloud watch (tasks -> logs).

How to create and attach a ELB properly in Boto3

由 ♀尐吖头ヾ 提交于 2020-01-12 11:40:10
问题 I'm new to Amazon's Boto3 API. I created a basic diagram of my sample architecture shown below, with an ELB, 4 instances, 2 subnets and and 2 target groups in 2 different Availability Zones (2 instances in each target group). I know how to create an EC2 instance, a target group, subnets, and an ELB. But what ELB functions to use, is not clear to me. How I can attach the ELB to other components? Basically, how to add instances to the ELB? I'm not sure what next steps and functions are needed

Aws-elb health check failing at 302 code

由 与世无争的帅哥 提交于 2019-12-22 05:33:24
问题 Hi i created ALB listener 443 and target group instance on 7070 port (not-ssl) I can access instanceip:7070 without problem , but with https://elb-dns-name not able to access.. instance health check also failed with 302 code ALB listener port https and instance is http protocol , when i browse with https://dns-name it redirecting to http://elb-dns-name 回答1: you get 302 when performing URL redirection, any ELB Health check will look for success code 200 for the health check to pass. In ALB,

Kubernetes and AWS: Set LoadBalancer to use predefined Security Group

由 耗尽温柔 提交于 2019-12-20 10:57:15
问题 As the title says, I am looking for a way to force a LoadBalancer service to use a predefined security group in AWS. I do not want to have to manually edit the inbound/outbound rules of the security group that is created for the ELB by Kubernetes. I have not been able to find anything within the documentation, nor have I located anything that works elsewhere online. Here is my current template: apiVersion: v1 kind: Service metadata: name: ds-proxy spec: type: LoadBalancer ports: - port: 8761

Websocket closing after 60 seconds of being idle while connection node server using AWS ELB

由 久未见 提交于 2019-12-07 06:43:07
问题 I have one node server running on EC2 instance and client is also running on same EC2 instance, Client open websocket connection to communicate node server, it is working in QA and Dev AWS environment but same web connection is getting close after 60 seconds of being idle in prod environment ,I am running client and node server behind ELB in aws environment. Client Code: ws = new WebSocket('ws://localhost:8443'); ws.onclose = function () { console.log("Websocket connection has been closed.");

Websocket closing after 60 seconds of being idle while connection node server using AWS ELB

由 偶尔善良 提交于 2019-12-05 11:14:52
I have one node server running on EC2 instance and client is also running on same EC2 instance, Client open websocket connection to communicate node server, it is working in QA and Dev AWS environment but same web connection is getting close after 60 seconds of being idle in prod environment ,I am running client and node server behind ELB in aws environment. Client Code: ws = new WebSocket('ws://localhost:8443'); ws.onclose = function () { console.log("Websocket connection has been closed."); clientObj.emit('LogoffSuccess', 'LogoffSuccessfully'); }; ws.onerror=function(event) { console.log

Aws-elb health check failing at 302 code

由 匆匆过客 提交于 2019-12-05 08:38:55
Hi i created ALB listener 443 and target group instance on 7070 port (not-ssl) I can access instanceip:7070 without problem , but with https://elb-dns-name not able to access.. instance health check also failed with 302 code ALB listener port https and instance is http protocol , when i browse with https://dns-name it redirecting to http://elb-dns-name you get 302 when performing URL redirection, any ELB Health check will look for success code 200 for the health check to pass. In ALB, this can be configured under health check in the ELB console. To modify the health check settings of a target
订阅 aws-elb