CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/SaaS & Cloud

☁️ SaaS & Cloud · Deployment · Pro

Serverless API Deployment

A serverless backend on AWS: API Gateway, Lambda functions, DynamoDB, S3 events and Cognito for sign-in, with no servers to manage.

More SaaS & Cloud templates

Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.

Drawing diagram…

What this diagram shows

  • API Gateway routes each endpoint to a Lambda function
  • Cognito handles sign-up, login and tokens
  • S3 uploads trigger background processing functions

Prompt used

Serverless deployment on AWS: a single-page app on S3 and CloudFront signs users in with Amazon Cognito, calls API Gateway with a JWT, API Gateway routes to Lambda functions (orders, profile, uploads) that read and write DynamoDB. File uploads go to S3 via presigned URLs, and S3 events trigger a Lambda that processes images and publishes to SNS/SQS for notifications. Secrets in Secrets Manager, logs and traces in CloudWatch and X-Ray.

Mermaid code
flowchart TB
  U[Users] -->|"HTTPS :443"| CF[CloudFront]
  CF -->|"Static app"| SPA[(S3 - single-page app)]
  U -->|"Sign-in, OAuth"| COG[Amazon Cognito - sign-in]
  U -->|JWT| APIGW[API Gateway]
  subgraph Lambdas[Lambda functions]
    L1[orders]
    L2[profile]
    L3[upload-url]
    L4[process-image]
  end
  APIGW -->|"Invoke"| L1
  APIGW -->|"Invoke"| L2
  APIGW -->|"Invoke"| L3
  L1 -->|"Orders"| DDB[(DynamoDB)]
  L2 -->|"Profiles"| DDB
  L3 -->|Presigned URL| U
  U -->|Upload| S3[(S3 uploads)]
  S3 -->|Object created event| L4
  L4 -->|"Image processed events"| SNS[SNS / SQS notifications]
  L1 -.->|"logs, traces"| CW[CloudWatch and X-Ray]

Inside this diagram

A deployment diagram with 13 components in 1 environment and 14 connections.

Environments and what runs in them

  • Lambda functions: orders, profile, upload-url and process-image

Outside these environments

  • Users
  • CloudFront
  • S3 - single-page app
  • Amazon Cognito - sign-in
  • API Gateway
  • DynamoDB
  • S3 uploads
  • SNS / SQS notifications
  • CloudWatch and X-Ray

Data stores

  • S3 - single-page app
  • DynamoDB
  • S3 uploads

Connections

  • Users β†’ CloudFront: HTTPS :443
  • CloudFront β†’ S3 - single-page app: Static app
  • Users β†’ Amazon Cognito - sign-in: Sign-in, OAuth
  • Users β†’ API Gateway: JWT
  • API Gateway β†’ orders: Invoke
  • API Gateway β†’ profile: Invoke
  • API Gateway β†’ upload-url: Invoke
  • orders β†’ DynamoDB: Orders
  • profile β†’ DynamoDB: Profiles
  • upload-url β†’ Users: Presigned URL
  • Users β†’ S3 uploads: Upload
  • S3 uploads β†’ process-image: Object created event
  • process-image β†’ SNS / SQS notifications: Image processed events
  • orders β†’ CloudWatch and X-Ray: logs, traces

Make your own diagram like this

Describe your own system in plain English and the AI cloud architecture diagram generator draws it in seconds, in the same style as this template.

Related templates

DeploymentProSaaS & Cloud

Kubernetes Microservices Deployment

How a microservices app runs on Kubernetes in the cloud: ingress, namespaces, services with multiple replicas, managed databases and monitoring.

FlowchartSaaS & Cloud

CI/CD Pipeline Flowchart

A typical CI/CD pipeline from a pull request to production: build, tests, security scans, staging deploy, approval and a canary release.

SequenceSaaS & Cloud

OAuth 2.0 / OpenID Connect Login

The authorization code flow with PKCE used by most modern web and mobile apps to log users in through an identity provider.

C4 ArchitectureProSaaS & Cloud

Multi-Tenant SaaS Architecture

A B2B SaaS product serving many customer organisations from one platform: tenant-aware services, per-tenant data isolation, billing and admin.

DeploymentProSaaS & Cloud

AWS Three-Tier Web Application

The classic three-tier web app on AWS: CloudFront and a load balancer, an autoscaling app tier in private subnets, and a Multi-AZ database.

C4 ArchitectureProSaaS & Cloud

Event-Driven Architecture with Kafka

Services that talk through events instead of direct calls: an order service publishes events that inventory, payments, notifications and analytics react to.