-
Notifications
You must be signed in to change notification settings - Fork 29
Closed
Milestone
Description
In DCR we are currently using ELB (Classic Load Balancer) which will probably be deprecated in the near future.
dotcom-rendering/dotcom-rendering/cdk/lib/dotcom-rendering.ts
Lines 89 to 97 in cea44e3
| /** | |
| * TODO - migrate this ELB (classic load balancer) to an ALB (application load balancer) | |
| * @see https://github.com/guardian/cdk/blob/512536bd590b26d9fcac5d39329e8217103d7859/src/constructs/loadbalancing/elb.ts#L24-L46 | |
| * | |
| * GOTCHA: The load balancer name appends `-ELB` when the `app = "rendering"` for backwards compatibility | |
| * We removed this to avoid the `LoadBalancerName.length > 32`. This will be fixable once we migrate to ALBs. | |
| */ | |
| const loadBalancerName = app === 'rendering' ? `${stack}-${stage}-${app}-ELB` : `${stack}-${stage}-${app}`; | |
| const loadBalancer = new GuClassicLoadBalancer( |
The DevX recommendation is to use GuClassicLoadBalancer only when migrating an existing stack and need to retain the load balancer. This was done in #8566
This ticket is to migrate from using ELB to ALB Load Balancer Type. As load balancer is a stateful resource and replacement is unexpected, we need to follow the DevX Migration Guide.
Useful docs
- AWS migration guide
- Good blogpost on the differences between ELB and ALB.
Metric
What metric should we use to evaluate this change?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels