Meta tags:
description= Discover how Nitric provisions and manages key-value stores across AWS, GCP, and Azure with Terraform and Pulumi.;
Headings (most frequently used words):
sequence, key, value, build, stores, get, started, deploy, languages, reference, misc, system, context, component, code, runtime, store, module,
Text of the page (most frequently used words):
api (48), key (35), value (34), nitric (21), file (20), route (20), secret (19), bucket (19), store (18), #stores (16), the (16), delete (16), sql (15), get (14), websocket (14), aws (13), access (13), overview (12), terraform (11), and (11), sdk (11), storage (11), put (11), queue (11), topic (11), job (11), secrets (10), schedule (9), schedules (9), apis (9), code (8), module (8), google (8), queues (8), topics (8), sequence (7), pulumi (7), keys (7), websockets (7), batch (7), patch (7), post (7), runtime (6), write (6), cloud (6), dynamodb (6), version (6), gcp (5), operations (5), for (5), app (5), provider (5), iam (5), read (5), all (5), databases (5), websites (5), github (4), this (4), page (4), modules (4), azure (4), application (4), developer (4), with (4), plugin (4), register (4), firestore (4), send (4), dequeue (4), enqueue (4), subscribe (4), publish (4), set (4), submit (4), handler (4), search (4), guides (3), foundations (3), support (3), required (3), use (3), resource (3), developers (3), functions (3), services (3), roles (3), policies (3), provides (3), data (3), request (3), example (3), iac (3), cli (3), provision (3), resources (3), their (3), custom (3), close (3), cron (3), every (3), connectionstring (3), files (3), latest (3), follow (2), contributions (2), 2026 (2), edit (2), component (2), system (2), context (2), keyvalue (2), are (2), created (2), infrastructure (2), dart (2), python (2), reference (2), uses (2), from (2), logic (2), providers (2), unique (2), using (2), document (2), forward (2), below (2), diagram (2), showing (2), operation (2), worker (2), requirements (2), build (2), provide (2), retrieve (2), create (2), secure (2), serves (2), backend (2), define (2), service (2), getuploadurl (2), getdownloadurl (2), exists (2), http (2), async (2), messaging (2), architecture (2), docs (2), youtube, join, our, discord, server, inc, last, updated, jan, open, issue, have, feedback, will, extend, including, both, nodejs, language, that, configures, implements, manage, abstracts, underlying, implementation, enabling, consistent, experience, across, different, offers, event, driven, workflows, allowing, integration, notification, systems, triggered, changes, enables, dynamic, control, assigning, permissions, applications, based, predefined, ensuring, least, privilege, scalable, cost, efficient, configurations, suitable, variable, workloads, supports, definition, attributes, partition, optional, sort, optimize, organization, querying, ensures, identification, standardized, naming, convention, randomly, generated, identifiers, convert, flow, shows, which, reads, its, spec, events, when, registers, lambda, tables, default, overridden, necessary, target, requires, implement, securely, values, within, faq, examples, misc, containers, env, vars, other, config, preview, features, sqldatabase, uploadurl, downloadurl, listfiles, accessversion, newroute, newwebsocket, newschedule, newtopic, newbucket, newsqldatabase, newsecret, newqueue, newkv, newjob, newapi, connection_string, upload_url, download_url, methods, node, languages, install, docker, adding, types, extension, mappings, deploy, hpc, deployment, local, development, security, configuration, projects, why, quick, start, installation, started, introduction, documentation,
Text of the page (random words):
architecture key value stores nitric documentation foundations guides search search docs 1 9k search search docs introduction get started installation quick start guides foundations why nitric projects overview configuration infrastructure overview services resources security local development deployment architecture overview services apis schedules websockets websites storage key value stores async messaging queues topics sql databases secrets build apis batch ai ml hpc schedules websockets websites storage key value stores sql databases async messaging secrets deploy overview pulumi overview aws google cloud azure terraform overview aws google cloud azure service mappings aws apis batch schedules websockets websites storage key value stores sql databases topics queues secrets azure apis schedules websites storage key value stores sql databases topics queues secrets google cloud apis batch schedules websites storage key value stores sql databases topics queues secrets custom overview provider extension custom providers adding resource types install with docker languages overview node js overview apis api api get api post api put api delete api patch api route api route all api route get api route post api route put api route delete api route patch batch job job handler job submit http http key value stores kv kv get kv set kv delete kv keys topics topic topic publish topic subscribe queues queue queue enqueue queue dequeue secrets secret secret put secret version secret latest secret version access storage bucket bucket on bucket file bucket files file exists file read file write file delete file getdownloadurl file getuploadurl sql sql sql connectionstring schedules schedule schedule every schedule cron websockets websocket websocket on websocket send websocket close python overview apis api api get api post api put api delete api patch api methods api all batch job job handler job submit key value stores kv kv get kv set kv delete kv keys topics topic topic publish topic subscribe queues queue queue enqueue queue dequeue secrets secret secret put secret version secret latest secret version access storage bucket bucket on bucket file bucket files file read file write file delete file download_url file upload_url sql sql sql connection_string schedules schedule websockets websocket websocket on websocket send go overview resources newapi newjob newkv newqueue newsecret newsqldatabase newbucket newtopic newschedule newwebsocket apis api get api post api put api delete api patch api newroute api route all api route get api route post api route put api route delete api route patch batch job handler job submit key value stores kv get kv set kv delete kv keys topics topic publish topic subscribe queues queue enqueue queue dequeue secrets secret put secret accessversion secret access storage bucket on bucket listfiles bucket read bucket write bucket delete bucket downloadurl bucket uploadurl sql sqldatabase connectionstring schedules schedule every schedule cron websockets websocket on websocket send websocket close dart overview apis api api all api get api post api put api delete api patch api route api route all api route get api route post api route put api route delete api route patch batch job job handler job submit key value stores kv kv get kv set kv delete kv keys topics topic topic publish topic subscribe queues queue queue enqueue queue dequeue secrets secret secret put secret version secret latest secret version access storage bucket bucket on bucket file bucket files file exists file read file write file delete file getdownloadurl file getuploadurl sql sql sql connectionstring schedules schedule schedule every schedule cron websockets websocket websocket on websocket send websocket close reference cli preview features other config env vars custom service containers misc examples faq contributions support key value stores 1 system context developers use nitric to define required key value stores within their application app code uses the key value resource from the nitric sdk developers define key value stores their application requires and implement logic to securely read write delete values with unique keys operations use default or overridden iac e g terraform modules to provision the necessary resources for their target cloud example aws provider aws dynamodb serves as the key value store backend aws iam provides roles and policies for secure access to dynamodb tables code terraform create dynamodb store retrieve data provide access developer operations nitric up aws dynamodb key value store aws lambda functions aws iam example gcp provider google firestore serves as the key value store backend google iam provides roles and policies for secure access to firestore code terraform create firestore store retrieve data provide access developer operations nitric up google firestore key value store google cloud functions google iam 2 sequence build sequence below is a sequence diagram showing the sequence of events when a developer registers a key value store with nitric app worker s nitric sdk nitric cli nitric provider plugin iac e g terraform register key value store register access requirements register key value store register access requirements forward nitric spec provision key value store provision iam app worker s nitric sdk nitric cli nitric provider plugin iac e g terraform runtime sequence below is a sequence diagram showing the runtime flow of a key value store operation using nitric the example shows a get operation which reads a value by its key app code nitric sdk nitric runtime plugin document db e g aws dynamodb get key forward request convert request key value api request app code nitric sdk nitric runtime plugin document db e g aws dynamodb 3 component key value store module ensures unique identification of key value stores by using a standardized naming convention or randomly generated identifiers supports the definition of attributes partition keys and optional sort keys to optimize data organization and querying provides scalable and cost efficient storage configurations suitable for variable workloads enables dynamic access control by assigning permissions to applications or services based on predefined roles and policies ensuring least privilege access offers support for event driven workflows allowing integration with notification systems or functions triggered by changes in the store abstracts the underlying key value storage implementation enabling consistent developer and operations experience across different cloud providers 4 code developers write application code that uses the key value resource from the sdk configures the secret and implements the application logic to access and manage secrets sdk reference by language nodejs sdk python sdk go sdk dart sdk operations will use or extend the nitric infrastructure modules including both terraform and pulumi terraform modules aws key value store terraform module gcp key value store terraform module keyvalue stores are created at runtime in gcp so no terraform module is required pulumi modules aws key value store pulumi module gcp key value store pulumi module keyvalue stores are created at runtime in gcp so no pulumi module is required azure key value store pulumi module edit this page on github have feedback on this page open github issue last updated on jan 5 2026 on this page 1 system context 2 sequence 3 component 4 code edit this page on github 2026 nitric inc contributions support foundations guides follow us on x follow us on github join our discord server youtube
|
