ScalewaySkip to loginSkip to main contentSkip to footer section

ai-PULSE 2024: Pre-registrations are open. Apply now! Nov 7, Paris

Q3 Product updates and launches

Elevate your Cloud experience with our latest offerings

  • Summer has set, but our innovations are on the rise.

    Dive into our Q3 2023 launches and discover the future of cloud, tailored for you. From expansive Availability Zones to cutting-edge database solutions, we're setting new standards in cloud reliability, scalability, and security.

    Are you ready to transform your cloud journey?

    👇 Dive in now!

Q3 products summary

ProductStageDocumentationConsole availability
AMS-3 AZGeneral AvailabilityGet started with InstancesYes
WAW-3 AZGeneral AvailabilityGet started with InstancesYes
VPC Multi-AZGeneral AvailabilityHow to benefit from VPC Multi-AZ?Yes
Production-Optimized Managed Database SQLGeneral AvailabilityHow to create a Managed Database?Yes
Private Load BalancerGeneral AvailabilityQuickstart to Load BalancerYes
Serverless SQL databasePrivate BetaHow to get started with Serverless SQL Database?Yes
API GatewayPrivate BetaHow to deploy an API Gateway?No

Q3 features summary

FeatureStageDocumentationConsole availability
Kapsule, Secret Manager and Object Storage metrics available in CockpitGeneral AvailabilityActivate your CockpitYes
Kapsule Dedicated Control Plane Self-Serve optionGeneral AvailabilityDiscover the Control Plan offerYes
Managed Database SQL - Multi-AZ Read ReplicaGeneral AvailabilityCreate a Read ReplicaYes
Serverless Trigger for ContainersPublic BetaAdd a trigger to containerYes

Find the solution that's made for you

Reliable infrastructure

Optimize your deployment strategy for unparalleled uptime and resilience

  1. Initialize AMS1 Setup: Begin with a POP2 Managed Databases MySQL in AMS1. While it sets up, prepare a Public Gateway, VPC, and Private Network.
  2. Deploy WordPress on AMS1: Start a POP2 Instance without a Flexible IP and use a script to launch WordPress. Connect the Instance to the Private Network.
  3. Load Balancer integration: Establish a Load Balancer in AMS1 (without backends initially) and integrate it with the Private Network.
  4. WordPress-database link: On the Managed Database MySQL node, set up a “wordpress” database. Configure WordPress to access this database.
  5. Snapshot & AMS3 replication: Capture a snapshot of the AMS1 Instance volume, store it, and then import it to AMS3. Launch a new POP2 instance in AMS3 from this snapshot and connect it to the Private Network.
  6. Load Balancer finalization: Set up backends on the Load Balancer to link with both AMS1 and AMS3 instances. Adjust WordPress settings to use the Load Balancer’s IP.
  7. Backup and Multi-AZ Replica: Backup the WordPress database using Multi-AZ Object Storage. For demonstration, create a Multi-AZ read replica linked to the Private Network.

A picture's worth a thousand words

Want to know more about Scaleway?

Food for thought