​

Cloud Provider Support

​

Overview

• Multi-cloud deployment - Deploy on AWS, Azure, GCP, or local infrastructure
• Provider flexibility - Switch cloud providers without code changes
• Testability - Test locally without cloud dependencies
• Future-proof architecture - Add new providers as requirements evolve

​

Supported Providers

​

Production Ready

​

AWS (Amazon Web Services)

• DynamoDB for component and API key storage
• Secrets Manager for configuration and secrets management
• CloudWatch for metrics publishing

​

Local Provider

• In-memory storage using thread-safe ConcurrentHashMap
• Zero external dependencies - no AWS, Docker, or cloud services
• Instant startup with no configuration overhead
• Automatic cleanup for expired sharables

​

GCP (Google Cloud Platform)

• Cloud Firestore (Native Mode) for component and API key storage
• Secret Manager for configuration and secrets management
• Cloud Monitoring for metrics publishing

​

Development Tools

​

LocalStack

• DynamoDB, Secrets Manager, and other AWS services
• Useful for testing AWS-specific behavior locally

​

Future Support

• Azure - Cosmos DB, Key Vault, Application Insights
• Custom - Implement your own provider for specialized infrastructure

​

How It Works

┌─────────────────────────────────────────┐
│         Hub Backend                     │
│    (Business Logic & Workflow Engine)   │
└──────────────────┬──────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────┐
│      Cloud Provider API                 │
│   (Provider-Agnostic Interfaces)        │
└──────────────────┬──────────────────────┘
                   │
        ┌──────────┼──────────┬──────────┐
        ▼          ▼          ▼          ▼
┌──────────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ AWS Provider │ │  Local   │ │   GCP    │ │  Future  │
│  - DynamoDB  │ │ Provider │ │ Provider │ │ Providers│
│  - Secrets   │ │ -InMemory│ │-Firestore│ │  - Azure │
│  - CloudWatch│ │ -NoSetup │ │ -Secrets │ │  - Custom│
└──────────────┘ └──────────┘ │-Monitoring│ └──────────┘
                               └──────────┘

​

Choosing a Provider

hub:
  cloud:
    provider:
      type: aws  # Options: aws, gcp, local (future: azure, custom)

• aws - Production deployments on AWS (default for backward compatibility)
• gcp - Production deployments on Google Cloud Platform
• local - Local development and testing (zero dependencies)

​

Key Features

​

Component Storage

• Storing and retrieving Hub components with versioning
• Managing component revisions
• Supporting optimistic locking for concurrent updates

​

Configuration Management

• Storing component configuration securely
• Version management
• Encrypted storage where supported

​

Secrets Management

• Managing API key secrets
• Permission management
• Secure storage with encryption

​

Sharable Token Storage

• Temporary token storage with TTL
• Automatic expiration
• High-performance retrieval

​

Configuration Overview

​

Getting Started

​

Using AWS Provider (Default)

1. Configure AWS credentials:

hub:
  aws:
    region: us-east-1
    dynamodb:
      prefix: my-hub
      createTables: true
    secrets:
      prefix: my-hub

2. Ensure IAM permissions for DynamoDB and Secrets Manager
3. Deploy - Tables and secrets are created automatically

​

Using Local Provider

1. Add dependency to build.gradle:

dependencies {
    implementation project(':backend-spring-boot-starter')
    implementation project(':cloud-provider-local')
}

2. Configure local provider in application.yml:

hub:
  cloud:
    provider:
      type: local  # Zero config required!

3. Run Hub - that’s it! No external services needed.

• Instant startup (<100ms)
• No AWS credentials
• No Docker/LocalStack
• Perfect for testing and CI/CD

​

Using GCP Provider

1. Add dependency to build.gradle:

dependencies {
    implementation project(':backend-spring-boot-starter')
    implementation project(':cloud-provider-gcp:gcp-spring-boot-starter')
}

2. Enable GCP APIs:

gcloud services enable firestore.googleapis.com
gcloud services enable secretmanager.googleapis.com
gcloud services enable monitoring.googleapis.com

3. Configure GCP provider in application.yml:

hub:
  cloud:
    provider:
      type: gcp
  gcp:
    projectId: your-gcp-project-id
    # credentialsLocation: /path/to/key.json  # Optional - uses ADC if omitted

4. Deploy - Firestore collections and secrets are created automatically

• Application Default Credentials (ADC) support
• Firestore Native Mode for storage
• Secret Manager for configuration
• Cloud Monitoring for metrics
• Workload Identity on GKE

​

Using LocalStack (AWS Emulation)

1. Start LocalStack:

docker run -d -p 4566:4566 localstack/localstack

2. Configure Hub for LocalStack:

hub:
  cloud:
    provider:
      type: aws
  aws:
    region: us-east-1
    accessKey: test
    secretKey: test
    dynamodb:
      endpoint: http://localhost:4566
    secrets:
      endpoint: http://localhost:4566

​

Architecture Deep Dive

• Module structure
• Interface design
• Adapter pattern
• Exception handling
• Testing strategies

​

Migration Guide

• Your existing hub.aws.* configuration continues to work
• No code changes required
• Migration is optional but recommended

​

Configuration Reference

​

See Also

• Architectural Overview
• Component Model
• Customization and Configuration
• Testing