Skip to content

Commit ad414c3

Browse files
RoRoJjcirinosclwySamyOubouaziz
committed
feat(lb): doc for migrating from AWS (#5350)
* feat(lb): add migration doc * feat(lb): more migration doc * fix(lb): finish migration doc * Apply suggestions from code review Co-authored-by: Jessica <[email protected]> Co-authored-by: SamyOubouaziz <[email protected]> --------- Co-authored-by: Jessica <[email protected]> Co-authored-by: SamyOubouaziz <[email protected]>
1 parent 4112110 commit ad414c3

File tree

4 files changed

+123
-0
lines changed

4 files changed

+123
-0
lines changed

menu/navigation.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4256,6 +4256,10 @@
42564256
"label": "Public vs private Load Balancers",
42574257
"slug": "public-private-accessibility"
42584258
},
4259+
{
4260+
"label": "Migrating from AWS ELB",
4261+
"slug": "migrating-aws"
4262+
},
42594263
{
42604264
"label": "Deprecation of SNI routes with HTTP backends",
42614265
"slug": "sni-route-deprecation"
98.1 KB
Loading
72.1 KB
Loading
Lines changed: 119 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
---
2+
title: Migrating from AWS to Scaleway for your load balancer needs
3+
description: Migrate from AWS to Scaleway for load balancing with this guide. Learn about the differences and equivalences between AWS Elastic Load Balancers and Scaleway Load Balancers, including types, concepts, setup, and pricing
4+
tags: load-balancer ELB application network listener target-group Scaleway AWS elastic-load-balancer
5+
dates:
6+
validation: 2025-07-28
7+
posted: 2025-07-28
8+
---
9+
10+
import lbDiagSimple from './assets/scaleway-lb-diag-simple.webp'
11+
import lbDiagComplex from './assets/scaleway-lb-diag-complex.webp'
12+
13+
You may be used to creating and managing your cloud load balancers with AWS. This document is intended to help and guide users considering migrating from AWS to Scaleway for their load balancing needs. It aims to help you understand the differences and equivalences between load balancer concepts and resource creation with AWS versus Scaleway.
14+
15+
## Load Balancer products and types
16+
17+
AWS offers several different "Elastic" Load Balancer products. Scaleway offers a single **Load Balancer** product, which can be [configured in different ways](##application-vs-network-with-scaleway) to provide equivalences to the various types of AWS Elastic Load Balancer: <br/><br/>
18+
19+
20+
| | AWS Classic LB | AWS Application LB | AWS Network LB | AWS Gateway LB | SCW LB |
21+
|--------------|------------------------|--------------------|----------------|----------------|-----------------------|
22+
| OSI Layer | L4 & L7 | L7 | L4 | L3 & L4 | L4 & L7 |
23+
| Protocols | HTTP, HTTPS, TCP | HTTP, HTTPS | TCP, TLS, UDP | All IP traffic | HTTP, HTTPS, TCP, TLS |
24+
25+
## Key concepts and naming differences
26+
27+
AWS and Scaleway do not always use the same wording to describe similar Load Balancer features. The table below is designed to help you translate feature and concept naming from one cloud provider's load balancer product to another:
28+
29+
| AWS | Scaleway |
30+
|--------------------------------|-----------------------------------------------|
31+
| Target group | Backend |
32+
| Target | Backend server |
33+
| Listener | Frontend |
34+
| Listener rules | Routes |
35+
| Listener rules | Routes |
36+
| Internal Load Balancer | Private Load Balancer |
37+
| Security group | ACL |
38+
| Metrics with Amazon CloudWatch | Metrics with Scaleway Cockpit |
39+
40+
The diagram below shows the simplest form of Scaleway Load Balancer:
41+
42+
<Lightbox image={lbDiagSimple} alt="A diagram shows how user requests or connections flow through a Load Balancer's public IP, to a frontend, to a backend, to backend servers" />
43+
44+
## Scaleway Load Balancer features
45+
46+
Scaleway Load Balancer offers the following features:
47+
48+
**Frontend:**
49+
- Public IPv4 and optional public IPv6 address (or private IP only)
50+
- SSL/TLS certificate upload
51+
- ACLs to filter incoming traffic
52+
- HTTP/3 support
53+
- HTTP Host header and SNI routes
54+
55+
**Backend:**
56+
- HTTP, HTTPS, TCP, and TLS support
57+
- Balancing between Scaleway resources (Instances, Elastic Metal servers, Dedibox) identified by public or private IP, or between non-SCW resources with selected plans
58+
- Configurable balancing method: round-robin, least connections, first available
59+
- Proxy Protocol
60+
- Sticky sessions (IP-based or cookie-based)
61+
- Customizable health checks
62+
- Backend protection
63+
- Customized error page
64+
65+
**Other:**
66+
- Compatibility with Scaleway VPC
67+
- Compatibility with Scaleway Kubernetes Kapsule and Scaleway CCM
68+
- Caching and WAF via Edge Services
69+
70+
## Load Balancer creation
71+
72+
### AWS flow vs Scaleway flow
73+
74+
The process for creating a Scaleway Load Balancer is different to that of AWS. Whereas for AWS, you must first define the target group that the load balancer will forward traffic to, with Scaleway you begin by creating the Load Balancer itself and then define the target group (server IPs) during creation of the Load Balancer's backend.
75+
76+
| AWS | Scaleway |
77+
|----------------------------------------------------------|-------------------------------------------------------------|
78+
| 1. Configure target group | 1. Create Load Balancer (AZ, commercial type, public and/or private IP) |
79+
| 2. Choose and create load balancer type (Network / Application etc) | 2. Create and configure frontend (port)
80+
| 3. Configure load balancer and listener | 3. Create and configure backend (port, protocol, traffic management, backend server IP addresses, advanced settings, health checks) |
81+
| | 4. Configure additional settings (SSL/TLS certs, ACLs, routes, HTTP3, Edge Services, additional frontends and backends etc.) |
82+
83+
The full process of creating a Load Balancer with Scaleway is detailed in the [Load Balancer Quickstart](/load-balancer/quickstart/).
84+
85+
The diagram below shows a Scaleway Load Balancer with multiple frontends and backends. In this case, the frontends listen on different ports, and use routes to determine which of their attached backends to forward traffic to.
86+
87+
<Lightbox image={lbDiagComplex} alt="A diagram shows how user requests or connections flow through a Load Balancer's public IP, to one of multiple frontends, to one of multiple backends, to backend servers" />
88+
89+
### Application vs Network with Scaleway
90+
91+
To create the equivalent of an AWS **Application Load Balancer** with Scaleway, you will typically create a Load Balancer with:
92+
93+
- One or more frontends listening on port 80 or 443
94+
- One or more backends configured for HTTP or HTTPS protocol
95+
- (Optional) Routes from frontends to backends based on HTTP Host headers
96+
97+
To create the equivalent of an AWS **Network Load Balancer** with Scaleway, you will typically create a Load Balancer with:
98+
99+
- One or more frontends listening on a port matching your application
100+
- One or more backends configured for TCP protocol
101+
- (Optional) Routes from frontends to backends based on SNI
102+
103+
## Plans and pricing
104+
105+
Like AWS, the pricing model for Scaleway Load Balancers is based on an hourly rate. Different commercial types of Load Balancers have different hourly rates, based on:
106+
107+
- **Maximum supported bandwidth**
108+
- **Multicloud support** (whether the Load Balancer can forward traffic to backend servers outside of Scaleway)
109+
110+
For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/network/#load-balancer).
111+
112+
## Useful documentation
113+
114+
To learn more about Scaleway Load Balancer, try the following documentation:
115+
116+
- [Load Balancer Documentation Home](/load-balancer/)
117+
- [Load Balancer Concepts](/load-balancer/concepts/)
118+
- [Load Balancer Quickstart](/load-balancer/quickstart/)
119+
- [Load Balancer FAQ](/load-balancer/faq/)

0 commit comments

Comments
 (0)