Skip to main content
Comparison

AWS Lambda Functions vs Google Cloud Run functions

Compare categories, runtimes, pricing, regions, infrastructure, and platform trade-offs.

Comparison space

Updated

Platform

Hosting model
Managed
Managed
Services
Functions
Functions
Workloads
APIs
APIs
Backend Services
Backend Services
Background Workers
Background Workers
Data Processing
Data Processing
Scheduled Jobs
Scheduled Jobs
Web Applications
Web Applications
Capabilities
Compute Autoscaling
Compute Autoscaling
Deployment Rollbacks
Deployment Rollbacks
Deployment Traffic Splitting
Deployment Traffic Splitting
Preview Environments
Preview Environments
Scale to Zero
Scale to Zero
Zero-Downtime Application Deployments
Zero-Downtime Application Deployments

Development & Execution

Deployment & packaging
Docker / OCI
Docker / OCI
Local Emulator
Local Emulator
Serverless (Managed Runtime)
Serverless (Managed Runtime)
Runtimes
.NET Runtime
.NET Runtime
Custom Runtime
Custom Runtime
JVM
JVM
Node.js
Node.js
Languages
C#
C#
Go
Go
Java
Java
JavaScript
JavaScript
PHP
PHP
Python
Python
Ruby
Ruby
Rust
Rust
TypeScript
TypeScript
Triggers
Database Events
Database Events
Direct Invocation
Direct Invocation
Event Streams
Event Streams
HTTP Requests
HTTP Requests
Publish-Subscribe Topics
Publish-Subscribe Topics
Queue Messages
Queue Messages
Scheduled Invocation
Scheduled Invocation
Storage Events
Storage Events

Pricing

Billing basis
Resource based AWS Lambda On-Demand Usage
Resource based Cloud Run Functions First-Generation Usage
Requests / executions
  • Requests — $0.20 · per 1 million requests
  • Invocations — $0.40 · per 1 million invocations
Compute
  • x86 execution duration — $0.0000166667 · per GB-second
  • Memory time — $0.0000025 · per GB-second
  • CPU time — $0.0000100 · per GHz-second
Free entry / commitment
Recurring free allowances
Recurring free allowances

Infrastructure & Availability

Infrastructure provider
  • Amazon Web Services
  • Google Cloud Platform
Execution & placement
  • Execution: Single Region
  • Execution: Multi Region
  • Scope: Regional
  • Execution: Single Region
  • Execution: Multi Region
  • Scope: Regional
Availability footprint
  • 38 Regions
  • 43 Regions

Resource & Execution Limits

Execution time
15 minutes Per invocation
60 minutes 2nd gen HTTP function
Memory
128-10,240 MB Per function
32 GiB 2nd gen function
Concurrency
1,000 Default regional account quota
Unknown
Request payload
6 MB request / 6 MB response Per invocation
32 MB 2nd gen HTTP function

Security & Compliance

Access & identity
Access Control
IAM execution roles, identity policies and resource policies
Function-level IAM and authenticated invocation Role differs for 1st gen and Cloud Run-based functions
Audit Logging
AWS CloudTrail management events Some data-event coverage requires configuration
Cloud Audit Logs Management coverage; data-access classes may require configuration
Encryption & secrets
Encryption at Rest
AWS-managed encryption; customer-managed KMS keys supported Coverage depends on Lambda data type
Customer-managed encryption keys Supported build and runtime resources; customer configuration
Secrets Management
AWS Secrets Manager integration Separate AWS service; customer IAM configuration required
Unknown
Network isolation & protection
Private Networking
Customer VPC access Functions still run in a Lambda-managed VPC
VPC Service Controls perimeter and VPC egress Customer organization and network configuration
Assurances & programs
FedRAMP
Class C / Class D East/West / GovCloud respectively
FedRAMP High Authorized service and region/configuration scope
HIPAA
HIPAA eligible Executed AWS BAA and customer controls required
HIPAA-eligible use Google Cloud BAA and customer controls required