AWS Elastic Load Balancing Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
[[AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Name|Name]]: playground-internal-lb (it should not start with "internal-"). | [[AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Name|Name]]: playground-internal-lb (it should not start with "internal-"). | ||
[[AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Scheme|Scheme]]: internal/internet-facing: | [[AWS_Elastic_Load_Balancing_Concepts#Load_Balancer_Scheme|Scheme]]: internal/internet-facing: internet-facing. | ||
==Listeners== | ==Listeners== | ||
Revision as of 19:42, 11 February 2019
External
Internal
Create a Network Load Balancer
Go to Amazon EC2 console -> Load Balancers -> Create Load Balancer -> Network Load Balancer.
Basic Configuration
Name: playground-internal-lb (it should not start with "internal-").
Scheme: internal/internet-facing: internet-facing.
Listeners
There's a default tcp:80 listener.
Availability Zones
Allows specifying the VPC and subnets within the VPC.
Security Settings
Return here.
Configure Routing
If this load balancer is created to service ECS FARGATE containers that have not been defined yet, that is fine, the target groups will be created during the ECS Service creation process.
Target Group
Target Group: New target group
Name: something
Target type: Instance
Protocol: TCP
Port: 80
Health Checks
Return here.
Register Targets
Registered Targets
Instances
If the load balancer is created before the ECS deployments, how do I select those?