feat(lb): more migration doc

Author: RoRoJ

pages/load-balancer/reference-content/migrating-aws.mdx

@@ -20,14 +20,28 @@ AWS offers several different "Elastic" Load Balancer products. Scaleway offers a
 | Protocols    | HTTP, HTTPS, TCP       | HTTP, HTTPS        | TCP, TLS, UDP  | All IP traffic | HTTP, HTTPS, TCP, TLS |
 
 
+## Key concepts and naming differences
+
+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:
+
+| AWS                            | Scaleway                                      |
+|--------------------------------|-----------------------------------------------|
+| Target group                   | Backend                                       |
+| Target                         | Backend server                                |
+| Listener                       | Frontend                                      |
+| Listener rules                 | Route rules                                   |
+| Internal Load Balancer         | Private Load Balancer                         |
+| Security group                 | ACL                                           |
+| Metrics with Amazon CloudWatch | Metrics with Scaleway Cockpit                 |
+
 ## Scaleway Load Balancer features
 
 Scaleway Load Balancer offers the following features:
 
 **Frontend:**
 - Public IPv4 and optional public IPv6 address (or private IP only)
 - SSL/TLS certificate upload
-- ACLs
+- ACLs to filter incoming traffic
 - HTTP/3 support
 - HTTP Host header and SNI routes
 
@@ -46,57 +60,33 @@ Scaleway Load Balancer offers the following features:
 - Compatibility with Scaleway Kubernetes Kapsule and Scaleway CCM
 - Caching and WAF via Edge Services
 
-## Key concepts and naming differences
-
-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:
-
-| AWS                            | Scaleway                                      |
-|--------------------------------|-----------------------------------------------|
-| Target group                   | Backend servers (identified by server IPs)    |
-| Listener                       | Frontend                                      |
-| Listener rules                 | Route rules                                   |
-| Internal Load Balancer         | Private Load Balancer                         |
-| Security group                 | ACL                                           |
-| Metrics with Amazon CloudWatch | Metrics with Scaleway Cockpit                 |
-
 ## Creating an AWS Load Balancer vs a Scaleway Load Balancer
 
 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.
 
 | AWS                                                      | Scaleway                                                    |
 |----------------------------------------------------------|-------------------------------------------------------------|
-| 1. Configure target group                                | 1. Create Load Balancer (AZ, commercial type, public and/or private IP |
+| 1. Configure target group                                | 1. Create Load Balancer (AZ, commercial type, public and/or private IP) |
 | 2. Choose and create load balancer type (Network / Application etc) | 2. Create and configure frontend (port)                   
 | 3. Configure load balancer and listener                  | 3. Create and configure backend (port, protocol, traffic management, backend server IP addresses, advanced settings, health checks)                |
 |                                                          | 4. Configure additional settings (SSL/TLS certs, ACLs, routes, HTTP3, Edge Services, additional frontends and backends etc.) |
 
-## Other differences
-
-Product Simplicity vs. Granularity
-AWS ELB provides multiple types of load balancers with highly granular configuration options.
-Scaleway Load Balancer is simpler, with most ALB/NLB features unified under a single product
-Implication: You’ll trade some fine-grained controls for ease-of-use. Ideal for most use cases, but edge cases may need workarounds.
-
-Plans and pricing?
-
-Routing Rules Are Per Frontend
-In AWS ALB, you configure listeners with rules tied to target groups.
-In Scaleway, you configure a routing table per frontend, with rules based on HTTP method, host, path, etc.
-✅ The routing flexibility is similar — just organized differently.
+The full process of creating a Load Balancer with Scaleway is detailed in the [Load Balancer Quickstart](/load-balancer/quickstart/).
 
-SSL/TLS Management
-AWS integrates SSL certificates via ACM (auto-renewal possible).
-Scaleway requires manual upload of certificates.
-🟥 Implication: You'll need a separate automation or manual process for certificate renewals unless you use wildcard Let's Encrypt certs with automation.
+## Plans and pricing
 
+Like AWS, the pricing model for Scaleway Load Balancers is based on an hourly rate. Different commercial types of Load Balancer have a different hourly rate, based on:
 
-Recommendations for Migrating Successfully
-Choose the Right LB Plan: Match features (e.g., SSL, max connections) to your needs.
+- **Maximum supported bandwidth**
+- **Multicloud support** (whether the Load Balancer can forward traffic to backend servers outside of Scaleway)
 
-Review Backend Architecture: Ensure your backends are reachable by public IP or properly configured private networks.
+For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/network/#load-balancer).
 
-Automate Cert Management: Consider integrating Let's Encrypt with Scaleway’s API for SSL cert renewal.
+## Useful documentation
 
-Adjust Routing Logic: Translate AWS ALB listener rules into Scaleway's route rules.
+To learn more about Scaleway Load Balancer, try the following documentation:
 
-Replace ASG Target Registration: Script the backend registration if you're using autoscaling.
+- [Load Balancer Documentation Home](/load-balancer/)
+- [Load Balancer Concepts](/load-balancer/concepts/)
+- [Load Balancer Quickstart](/load-balancer/quickstart/)
+- [Load Balancer FAQ](/load-balancer/faq/)