AWS Elastic Load Balancing Operations Create a Network Load Balancer with Amazon Console

From NovaOrdis Knowledge Base
Revision as of 05:46, 3 April 2019 by Ovidiu (talk | contribs) (Created page with "=Internal= * Elastic Load Balancing Operations =Overview= {{Note|This network load balancer was cr...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Internal

Overview


This network load balancer was created to service ECS FARGATE containers. It must be created before the corresponding FARGATE service is defined.

Go to Amazon EC2 console -> Load Balancers -> Create Load Balancer -> Network Load Balancer.

Basic Configuration

Name. For more details about load balancer names, see:

Name

It should not start with "internal-...".

Example: "playground-nlb"

Scheme. For more details about load balancer scheme, see:

Scheme

I have used "internet-facing", because this is what I was able to make work. 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..

Listeners

For more details about listeners, see:

Listeners

Use TCP over port 80.

Availability Zones

For more details see:

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: Return to Elastic IP.

Security Settings

Refers to TLS configuration, which should be mandatory for public facing load balancers. Return here.

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 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:

Target Group]]

Target group: New target group

Name: to-be-deleted

Target type: Instance

Protocol: TCP

Port: 55555

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".

Health Checks

Protocol: TCP Return here.

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

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.