amazon web services - Loadbalancer cannot get a good health check -


i'm confused how aws load balancers work. have pretty simple setup...

i have rest based api needs exposed internet (port 80) via load balancer. want load balancer exposed internet traffic. have security group setup instance restricts direct access ipaddress testing purposes.

the load balancer not ip restricted on http, has port 80 open (with listener api service on port 3001). problem load balancer cannot see instance if setup ip restrictions on instances in question. once remove restrictions on instances, health checks start working , can access service through load balancer. problem instances have ports open internet don't want.

is there additional need allow load balancer access instances when using ip restrictions?

one final note, health checks work fine until add instance-level ip restrictions know health check not problem. think if added load balancer's ip whitelist, work, ip dynamic , not viable purpose.

don't use ip restrictions.

1) select lb, select security tab , note security group id (something sg-5555abb). click on id edit it

2) when edit load balancer security group, add 1 allow rule: http tcp 80 0.0.0.0/0 (and/or 443 if need it, idea).

3) next go instance's security group. allow load balancer's security group access instance on port 3001:custom tcp rule tcp 3001 sg-5555abb (my-load-balancer). notice in source field not enter ip address/mask security group id step 1)

http://docs.aws.amazon.com/awsec2/latest/userguide/using-network-security.html#security-group-rules


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more