amazon-elb

问题 We are using ECS Farget container service for our ruby on rails containers. We have implemented NLB with HTTP health checks in the target group but as we know that "NLB Target Group health checks are out of control". This is consuming our CPU of each container up to 8% so we are thinking of to migrate HTTP HealthChecks to TCP HealthChecks. Can anyone comment on how TCP HealthCheck works??? Does it only connects to port for a health check or it's actually hit the API? Ref: NLB Target Group

问题 We are using ECS Farget container service for our ruby on rails containers. We have implemented NLB with HTTP health checks in the target group but as we know that "NLB Target Group health checks are out of control". This is consuming our CPU of each container up to 8% so we are thinking of to migrate HTTP HealthChecks to TCP HealthChecks. Can anyone comment on how TCP HealthCheck works??? Does it only connects to port for a health check or it's actually hit the API? Ref: NLB Target Group

问题 I am wanting to setup an AWS Elastic Load Balancer in front of a Phabricator installation. I would like the ELB to balance HTTP, HTTPS and SSH traffic. Is this possible or do I need to run my own SSH load balancer with HAProxy or similar? To clarify, I am aiming to load balance git operations which occur over SSH, as distinct from administrative SSH. 回答1: In my case of Phabricator + AWS ELB setup Allowed ELB port for phab instances. Configured VirtualHost redirection from HTTP to HTTPS in

问题 I have a set of instances running within an ELB and an API to stop/ start any of those instance developed using java SDKs. However the instances are getting terminated as soon as it goes to stopped state, which i don't want to happen. Is this a known behavior and is there a way to stop this from happening and to keep these instances in the stopped state? 回答1: Instances are terminated if they are associated with an auto scaling group Check this Instance Termination in autoscaling groups for

问题 I'm trying to associate an ELB (NLB actually) with a CodeDeploymentGroup, using the prescribed format of ElbInfoList. This is in CloudFormation. CodeDeploy won't have it. During deploy, it says, > *The specified load balancer does not exist. for activityId="5" of activityType={Name: > ExecuteCentralizedCommandOnInstanceActivity.runCentralizedCommand,Version: > 1.00}* My deployment group looks like so: "CodeDeploymentGroup" : { "Type" : "AWS::CodeDeploy::DeploymentGroup", … "Properties" : {…

问题 I am trying to create rules in my ALB so there are parts of the path that I do not forward on to the target. So for example, my underlying service may accept a call like GET http://hostname/dogs But in the ALB I might add a version to the path for routing purposes: GET http://hostname/v1/dogs or I could call GET http://hostname/v2/dogs Both versions would be running in different target groups. I was thinking I could then drop the version part off so that my application doesn't have to be

问题 I use Netlify to host my static site example.com . Since I don't want to append www , I have to use Netlify's DNS nameservers. example.com uses API backend api.example.com , which is a CNAME record that resolves to an ELB address *.elb.amazonaws.com . So 2 DNS lookup is required: first to example.com then to *.elb.amazonaws.com . Alternative: Setup Route 53 with another custom domain example.org with an ALIAS record api.example.org that points to *.elb.amazonaws.com , and use api.example.org

问题 I have a site which is hosted in AWS EC2 instance with a ELB URL. The DNS mapping is done. When I try to open the site in Chrome it takes about 1.3 mins to open whereas in Safari it takes about 3 secs. On investigating further I found out that the initial connection is taking 1.3 secs and subsequently it takes 3-4 secs to load the website. Is this a DNS issue? Need help to solve this issue as I am not a network expert. Thanks for your help. Sukrity 来源： https://stackoverflow.com/questions

问题 We use the following AWS infrastructure: Route53-> CloundFront -> Elasticbeanstalk(+LoadBalancer=ELB) -> EC2 instances Now we have ssl certificates set up on CloudFront level and the same one on ELB level thus providing us end-to-end encryption between CF and ELB. End2End between AWS CF and origin is described as best practice here. This refers to Full SSL(strict) on this picture(this is for CloudFlare stack but it is for better illustration so never mind). We want to offload SSL on AWS CF

问题 I recently started reading about and playing around with AWS. I have particular interest in the different high availability architectures that can be acheived using the platform. Specifically, I am looking for a reliable poor man's solution that can be implemented using the least amount of servers. So far, I am satisfied with solutions for the main HA concerns: load balancing, redundancy, auto recovery, scalability ... The only sticking point I have is with failover solutions. Using an ELB