Serverless Containers

Run a small HTTP container on managed serverless container platforms with registry-backed images, managed secret injection, health checks, public ingress, and autoscaling across AWS, Azure, and GCP.

Step 1 of 1

Choose cloud

Choose an option to continue.

Frequently asked questions

What does this guide deploy?
It deploys a tiny HTTP app with / and /health, builds a container image locally, pushes it to a managed container registry, and runs it behind the cloud’s managed public ingress.
Does the starter include a real app?
Yes. The download includes a small Node.js service and Dockerfile so pulumi up can build and publish a working image without bringing your own app first.
How are secrets handled?
The stack creates one sample managed secret and injects it into the container as APP_MESSAGE. Replace the value with your own stack secret before using the starter for a real service.
How does scaling work?
Each variant exposes minimum and maximum scale settings, plus request concurrency or utilization settings where the platform supports them, then maps those values to the platform-native autoscaling resource.
What does it cost?
Expect registry storage, build/push transfer, and container runtime costs. AWS also creates an Application Load Balancer, which has a baseline hourly cost. Destroy the stack when you are done experimenting.