amazon-elb

How can I assign a static IP address to a ELB. Seems like I cannot. Some articles online asks to create a Route 53 record but this requires changing CNAME of domain which also redirect email traffic. I just want to change A record not CNAME. Some articles also mention that I can use a EC2 instance as a reverse proxy. But will a single proxy be able to handle a lot of traffic? Any solution for this? AWS' Elastic Load Balancer is actually elastic on two levels as described here: http://shlomoswidler.com/2009/07/elastic-in-elastic-load-balancing-elb.html The first level is the load balancer

Issue: User logs in with https://example.com/login Authentication is approved As configured in security.yml Symfony2 redirects user to profile page after login. But it redirects them to the wrong url http://example.com/homepage security.yml : security: encoders: FOS\UserBundle\Model\UserInterface: sha512 role_hierarchy: ROLE_ADMIN: ROLE_USER ROLE_SUPER_ADMIN: [ROLE_USER, ROLE_ADMIN, ROLE_ALLOWED_TO_SWITCH] providers: fos_userbundle: id: fos_user.user_provider.username_email firewalls: main: pattern: ^/ form_login: check_path: /login_check login_path: /login default_target_path: /profile

How do you put up a maintenance page in AWS when you want to deploy new versions of your application behind an ELB? We want to have the ELB route traffic to the maintenance instance while the new auto-scaled instances are coming up, and only "flip over" to the new instances once they're fully up. We use auto-scaling to bring existing instances down and new instances, which have the new code, up. The scenario we're trying to avoid is having the ELB serve both traffic to new EC2 instances while also serving up the maintenance page. Since we dont have sticky sessions enabled, we want to prevent

I have an AWS Elastic Beanstalk environment that is created with an Elastic Load Balancer, and which specifies the default ELB security group ("ELB created security group used when no security group is specified during ELB creation") as the source for inbound HTTP. If I replace this default ELB security group as the source for my environment's security group's inbound rules with a port range does traffic still come through the ELB and is it still filtered by the ELB's security group's rules or does traffic then "skip" the ELB (or at least it's security group) and come directly to my instances?

Docker containers behind ELB get dynamic ports which are auto registered with ELB so that they can get traffic redirected to them. In order to make your web servers accessible to ELB you have to open all these ports 1024 - 65535 originating from within your security group. Is there a way to not to have to open up a security group to a range of port but only to the pots that ELB is using? Security groups are never modified by AWS as this might cause conflicts and security issues. The only exception would be services such as Elastic Beanstalk. You'd likely have to do what the forum says and

I am currently using Spark on AWS EMR, but when this is behind a Load Balancer (AWS ELB), it is redirecting the traffic from https to http, which then ends up getting denied because I don't allow http traffic through the load balancer for the given port. It appears that this might derive from Yarn being a proxy as well, but I have no idea. 来源： https://stackoverflow.com/questions/56412083/spark-history-server-behind-load-balancer-is-redirecting-to-http

I have a V2 ELB that is internet facing. It routes requests to instances in VPC just fine when I connect to it from my laptop. However when I try to connect to it from another instance inside the same VPC the Security Group firewall rules block the connection. The only way I can get the instances in VPC to connec to the ELB is by opening the https port (443) to the world. What am I doing wrong? The ELB ( https://elb.domain.com ) has the following attrs: Internet facing, V2 (not classic ELB) VPC: vpc-aaa AZs: subnet-a,subnet-b Listeners: 443 -> 8080 instance port source security group: my-vpc

We’re trying to create a setup of multiple APIs via the Amazon AWS Elastic Beanstalk (AEB) component. The reason we have chosen AEB is because it provides seamless deployment and scaling for the applications we deploy, without the need to manually create Load Balancers (LB) and scaling rules. We would very much like to keep it this way as we are planning on launching a (large) number of applications and APIs. However, we’re facing a number of challenges with AEB. First and foremost, some of the API’s need to communicate internally, and low latency is a core requirement for us. In order to