If you use a container orchestration service (ECS, GKE) then you use that system to upgrade container image with new app versions.
If you use autoscaling groups / managed instance groups, then you use that to replace VMs with new ones running containers with the new app image.
Using rolling updates, the load balancer drains connections to a container and then it is replaced.
Ideally this is done using your IaC system. So a deployment just involves changing the container image (app version) and applying the update.
Then there's more nuanced things that most teams will miss early on without someone pointing the problem and the solution e.g. decouple configuration from the app, design stateless apps (e.g. 12 factor app), use secrets management easily (e.g. dynamoDB based solutions like credstash are dirt cheap, AWS secrets is okay-ish), used managed DBs (RDS is the most common choice) and more.
I have provided infrastructure-as-a-service for many many baremetal/VMS/containers, but then I wasn't managing them (e.g: it was many small team's infra, not a small team of 10 people using 20-120 VMs as per OP)
The number of nodes was used to run a monolith. Same deployments and all, wasn’t as complicated as it might sound (terraform to manage infra, few custom apps to talk to external APIs, etc)
These were definitely not 500 fortune companies but AFAIK all of them had some cash flow or were acquired by behemoths.
Use an IaC system (Terraform, Pulumi, etc) to manage everything from Day 1:
1. Use a major cloud provider (AWS or GCP, probably)
2. Get a managed HTTP load balancer (ELB, ALB, whatever)
3. Run your app on 3+ containers behind it (running on bare VMs, K8S, whatever you prefer)
4. Set up a managed database cluster with Postgres or MySQL
5. Run 2 machines (for redundancy) for asynchronous jobs (using cron, a message bus, or DIY)
6. Store any large files in cloud storage and put them behind a CDN
That's all 99% of companies will ever need to do. These are all old technologies that Just Work.