AWS Elastic Load Balancing Operations: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 9: Line 9:
{{Internal|AWS Elastic Load Balancing V2 Deployment with CloudFormation|Elastic Load Balancing V2 Deployment with CloudFormation}}
{{Internal|AWS Elastic Load Balancing V2 Deployment with CloudFormation|Elastic Load Balancing V2 Deployment with CloudFormation}}


=<span id='Create_a_Network_Load_Balancer'></span>Create a Network Load Balancer with Amazon Console=
=Create a Network Load Balancer=


{{Note|This network load balancer was created to service ECS FARGATE containers. It must be created '''before''' the [[Amazon_ECS_Operations#Load_Balancing|corresponding FARGATE service is defined]].}}
* [[AWS Elastic Load Balancing Operations Create a Network Load Balancer with Amazon Console|Create a Network Load Balancer with Amazon Console]]
 
Go to Amazon EC2 console -> Load Balancers -> Create Load Balancer -> Network Load Balancer.
 
==Basic Configuration==
 
Name. For more details about load balancer names, see: {{Internal|AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Name|Name}}
 
It should not start with "internal-...".
 
Example: "playground-nlb"
 
Scheme. For more details about load balancer scheme, see: {{Internal|AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Scheme|Scheme}}
 
I have used "internet-facing", because this is what I was able to make work. <font color=darkgray>Return here and experiment with "internal", so the service endpoints exposed through load balancer are not publicly available, but only through an API Gateway that will be subsequently configured.</font>.
 
==Listeners==
 
For more details about listeners, see: {{Internal|AWS_Elastic_Load_Balancing_Concepts#Listener|Listeners}}
 
Use TCP over port 80.
 
==Availability Zones==
 
For more details see: {{Internal|AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_and_Availability_Zones|Load Balancers and Availability Zones}}
 
Specify the VPC in which the targets exist.
 
Then, specify at least one, possible more availability zones and one subnet per availability zone. All subnets in which target endpoint services run must be specified here.
 
Elastic IP: <font color=darkgray>Return to Elastic IP.</font>
 
==Security Settings==
 
<font color=darkgray>Refers to TLS configuration, which should be mandatory for public facing load balancers. Return here.</font>
 
==Configure Routing==
 
If this load balancer is created to service ECS FARGATE containers that have not been defined yet, so we don't have enough information to create the corresponding target group. That is fine, at this stage, the relevant target group will be created during the [[Amazon_ECS_Operations#Load_Balancing|ECS Service creation process]]. However, the load balancer cannot be created without a target group, so create a temporary one, which may be deleted later, to satisfy the console workflow.
 
===Target Group===
 
More information about target groups: {{Internal|AWS_Elastic_Load_Balancing_Concepts#Target_Group|Target Group]]}}
 
Target group: New target group
 
Name: to-be-deleted
 
[[AWS_Elastic_Load_Balancing_Concepts#Target_Type|Target type]]: Instance
 
[[AWS_Elastic_Load_Balancing_Concepts#Target_Group_Protocol|Protocol]]: TCP
 
[[AWS_Elastic_Load_Balancing_Concepts#Target_Group_Port|Port]]: 55555
 
<font color=darkgray>If we build this load balancer for an ECS service, we can create the target group in advance, by specifying the name, the protocol (TCP), the port (10001) and the target type "ip".</font>
 
===Health Checks===
 
Protocol: TCP <font color=darkgray>Return here.</font>
 
==Register Targets==
 
===Registered Targets===
 
===Instances===
 
Do not select anything now.
 
Next: Review -> Create.
 
==Information==
 
At this point, after the load balancer is created, selecting it in the load balancer tab provides access to ARN, DNS Name, Hosted Zone ID.
 
==The ECS Service==
 
{{Internal|Amazon_ECS_Operations#Create_a_Service|Create an ECS Service}}
 
==Follow-Up Tasks==
 
After the ECS-backed target group is created, come back and delete the "to-be-deleted" target group.


=Test a Network Load Balancer=
=Test a Network Load Balancer=

Revision as of 05:44, 3 April 2019

External

Internal

Elastic Load Balancing V2 Deployment with CloudFormation

Elastic Load Balancing V2 Deployment with CloudFormation

Create a Network Load Balancer

Test a Network Load Balancer

curl http://playground-nlb-85d74951c7b728b3.elb.us-west-2.amazonaws.com:10001/amazons

Create an Application Load Balancer

TODO.

Register a Target with a Target Group in Command Line

aws elbv2 register-targets --target-group-arn arn:aws:elasticloadbalancing:us-west-2:77777777777:targetgroup/themyscira/4d66315292d681f9 --targets Id=10.7.1.84
Retrieved from "https://kb.novaordis.com/index.php?title=AWS_Elastic_Load_Balancing_Operations&oldid=57577"