AWS Serverless

AWS Lambda

Runs your code in response to events without servers; you pay only for execution time.

What is AWS Lambda?

Lambda runs your code when something happens: an HTTP request through API Gateway or a function URL, a file uploaded to S3, a message in a queue or a schedule. There are no servers to manage; AWS runs as many copies as needed and you pay only for the time your code runs.

Key features

  • Supports Node.js, Python, Java, .NET, Go, Ruby and custom runtimes
  • Triggers from 200+ AWS services and events
  • Automatic scaling and high availability
  • Container image packaging up to 10 GB
  • Provisioned concurrency to avoid cold starts

What it is used for

  • APIs and webhooks
  • Processing uploaded files
  • Scheduled jobs and automation

When to use it

  • APIs and webhooks with variable traffic
  • File and data processing on events
  • Scheduled automation

When something else fits better

  • Long-running processes over 15 minutes
  • Constant heavy load where a server is cheaper

How pricing works

Charged per request and per millisecond of compute time, depending on the memory you allocate. A monthly free tier covers many small workloads. Prices change and differ by region; we confirm current costs for your setup before you commit.

Equivalent on Google Cloud

The closest Google Cloud service is Cloud Run functions: event-driven functions (formerly Cloud Functions) that run code without servers.

How DomainHostly helps with AWS Lambda

  • Plan: choose the right setup, size and region for your workload and budget.
  • Set up securely: configure AWS Lambda with least-privilege access, encryption and backups where they apply.
  • Migrate: move from shared hosting, your own servers or the other cloud with minimal downtime.
  • Run and optimise: monitoring, updates and regular cost reviews so you only pay for what you use.

Serverless: Run code and APIs without managing servers; you pay for what actually runs.

What to consider: Serverless

  • Serverless suits spiky or event-driven work; constant heavy load can be cheaper on servers or containers.
  • Watch time limits, cold starts and concurrency limits for each service.
  • Keep functions small, give each only the permissions it needs, and send logs to central monitoring.

Related services: Serverless