cloud▌

Server-side identity and user lookup for CloudBase Node.js backends and cloud functions. \n \n Retrieve caller identity ( uid , customUserId , openId ) in cloud functions using getUserInfo() for authorization and personalization decisions. \n Query CloudBase user profiles by uid or login identifier (phone, email, username, custom ID) using getEndUserInfo() and queryUserInfo() . \n Issue custom login tickets from Node backends to bridge existing user systems into CloudBase without requiring separ

Scaffold a new Terraform provider using the Plugin Framework. \n \n Generates a new Go module workspace with the standard \"terraform-provider-\" naming convention and initializes required dependencies \n Provides a template main.go file following HashiCorp's Plugin Framework patterns, with TODO markers for customization \n Validates the setup by running build and test commands to ensure the provider compiles and passes initial checks \n Handles workspace management by confirming intent before c

AWS Lambda function invocation, management, and Spring Boot integration using AWS SDK for Java 2.x. \n \n Supports synchronous and asynchronous Lambda invocation with JSON payload serialization and typed response parsing \n Covers function lifecycle operations: create, update, delete, list, and retrieve configurations including environment variables and concurrency settings \n Includes Spring Boot integration patterns with bean configuration, service abstractions, and type-safe Lambda invoker se

AWS KMS key management, encryption, and digital signing for Java applications with envelope encryption and Spring Boot integration. \n \n Covers key creation, encryption/decryption, envelope encryption for large data, digital signatures, and key rotation using AWS SDK for Java 2.x \n Includes synchronous and asynchronous client setup, Spring Boot service configuration, and IAM permission patterns \n Provides envelope encryption patterns to reduce KMS API calls and support data larger than 4KB li

Architects design workloads by integrating platform services, functionality, and code to meet both functional and nonfunctional requirements. To design effective workloads, you must understand these requirements and select topologies and methodologies that address the challenges of your workload's constraints. Cloud design patterns provide solutions to many common challenges.

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and platform services. \n \n Covers 40+ Cloudflare products organized by use case: compute (Workers, Pages, Durable Objects, Workflows), storage (KV, D1, R2, Queues), AI/ML (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), and security (WAF, Bot Management, Turnstile) \n Includes decision trees to route users to the right product based on their need (run code, store data, add AI, networking, security, or

Deploy static sites and serverless APIs to Azure with local development emulation and CLI automation. \n \n Provides local emulator ( swa start ) with API proxy, authentication simulation, and framework auto-detection for React, Vue, Angular, Next.js, and others \n Supports Azure Functions backends with Node.js, Python, and .NET runtimes; configure via staticwebapp.config.json for routes, auth rules, and headers \n Includes deployment workflow: swa init (auto-detects framework), swa build , swa

Infrastructure as code implementation across AWS, Azure, and GCP with modular design and state management. \n \n Covers module development, state backend configuration with locking and encryption, provider setup, and multi-environment workflows \n Enforces validation, semantic versioning, and security constraints; includes error recovery patterns for state drift, auth failures, and dependency issues \n Provides structured workflows: analyze requirements, design composable modules, configure remo

Category: test

Category: test