Meta tags:
description= Details on the cloud providers supported by Nitric;
Headings (most frequently used words):
providers, deploying, nitric, applications, get, started, build, deploy, languages, reference, misc, pre, built, custom, default, cloud, services,
Text of the page (most frequently used words):
api (51), file (20), route (20), custom (19), the (19), cloud (19), secret (19), bucket (19), #providers (18), you (18), nitric (17), provider (17), sql (17), delete (15), storage (14), websocket (14), get (13), overview (13), key (11), secrets (11), put (11), queue (11), topic (11), job (11), can (10), aws (10), queues (10), value (10), stores (10), schedules (10), batch (10), apis (10), github (9), topics (9), schedule (9), and (8), your (8), azure (8), websockets (8), this (7), read (7), are (7), services (7), google (7), patch (7), post (7), pre (6), built (6), new (6), resources (6), databases (6), websites (6), version (6), page (5), specific (5), requirements (5), existing (5), build (5), terraform (5), use (5), deploy (5), all (5), foundations (4), have (4), for (4), that (4), more (4), about (4), extend (4), using (4), deployment (4), service (4), pulumi (4), messaging (4), application (4), send (4), write (4), access (4), dequeue (4), enqueue (4), subscribe (4), publish (4), keys (4), set (4), submit (4), handler (4), search (4), discord (3), guides (3), open (3), development (3), currently (3), create (3), creating (3), here (3), way (3), deployed (3), infrastructure (3), with (3), code (3), other (3), see (3), docker (3), gateway (3), deploying (3), close (3), cron (3), every (3), connectionstring (3), files (3), latest (3), our (2), follow (2), support (2), contributions (2), 2026 (2), edit (2), issue (2), team (2), want (2), request (2), feature (2), extending (2), from (2), deployments (2), work (2), meet (2), languages (2), plugins (2), source (2), how (2), any (2), features (2), repository (2), manager (2), pubsub (2), event (2), table (2), not (2), implemented (2), gcp (2), local (2), resource (2), underlying (2), following (2), default (2), each (2), available (2), supported (2), microsoft (2), these (2), learn (2), recommend (2), guide (2), quick (2), start (2), getuploadurl (2), getdownloadurl (2), exists (2), http (2), async (2), docs (2), youtube, join, server, inc, last, updated, jan, feedback, improving, ease, flexibility, priority, need, help, touch, met, scratch, easiest, add, change, there, two, ways, another, premises, building, reusing, automation, such, modules, changing, preferred, regulatory, policy, within, organization, engine, cdk, instead, language, than, develop, written, many, because, able, them, common, reasons, include, exactly, handled, runtime, then, make, changes, fit, some, may, unimplemented, but, interest, requests, appreciated, let, know, cloudrun, container, apps, lambda, vault, sqs, grid, sns, database, rds, boltdb, firestore, dynamodb, seaweedfs, blob, cdn, front, door, cloudfront, scheduler, dapr, binding, cloudwatch, bridge, coming, soon, management, both, same, shows, used, actively, working, expanding, number, like, please, raise, description, publishes, which, part, core, enable, running, across, select, meets, starting, will, walk, through, setting, project, stack, better, understanding, reading, section, when, ready, choose, variety, has, either, own, applications, faq, examples, misc, containers, env, vars, config, preview, cli, reference, dart, sqldatabase, uploadurl, downloadurl, listfiles, accessversion, newroute, newwebsocket, newschedule, newtopic, newbucket, newsqldatabase, newsecret, newqueue, newkv, newjob, newapi, connection_string, upload_url, download_url, methods, python, node, install, adding, types, extension, mappings, hpc, architecture, security, configuration, projects, why, installation, started, introduction, documentation,
Text of the page (random words):
overview 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 deploying nitric applications when you re ready to deploy your nitric application you can choose from a variety provider plugins nitric has pre built providers that use either pulumi or terraform to deploy to aws google cloud or microsoft azure if you have specific requirements you can extend these providers or build your own custom provider if you re new to nitric or want a better understanding of nitric providers work we recommend reading the foundations section to learn how to deploy your nitric application we recommend starting with the quick start guide this guide will walk you through setting up a nitric project creating a new stack and deploying your application use this page to learn more about the cloud providers supported by nitric and select or build a provider that meets your deployment requirements pre built providers nitric publishes pre built providers for aws google cloud gcp and microsoft azure which are available as part of the core open source repository on github these providers enable deploying and running code across aws google cloud and azure the following is a description of the underlying cloud services that each of the pre built providers use the nitric team is actively working on expanding the number of pre built providers available if you have a specific cloud provider or service you d like to see supported please raise a feature request on github default cloud services currently both the pulumi and terraform providers use the same underlying cloud services to deploy your application the following table shows the cloud services used by default on each cloud resource aws azure google cloud local apis api gateway api management api gateway custom batch aws batch coming soon gcp batch custom schedules cloudwatch event bridge dapr binding cloud scheduler custom websockets api gateway not implemented not implemented custom websites aws cloudfront front door cloud cdn custom storage s3 blob storage cloud storage seaweedfs key value stores dynamodb table storage firestore boltdb sql databases rds azure database cloud sql docker messaging topics sns event grid pubsub custom messaging queues sqs storage queues pubsub custom secrets secrets manager key vault secret manager custom services lambda container apps cloudrun docker the code is open source on github so you can see exactly how resources are deployed and handled at runtime then make any changes you see fit some features may be unimplemented but any interest or requests are appreciated let us know on discord or by creating an issue on our github repository custom providers because nitric providers are plugins you re able to create or extend them to meet your specific deployment requirements common reasons for custom provider development include using a language other than go to develop a provider nitric providers can be written in many other languages using a specific infrastructure as code engine e g using terraform or aws cdk instead of pulumi changing the way resources are deployed to use a preferred service or meet regulatory or policy requirements within your organization reusing existing work on infrastructure automation such using existing terraform modules for deployment with nitric deployments to another cloud provider or on premises deployments you can read more about building custom providers here currently there are two ways to build a custom provider extend an existing provider this is the easiest way to build a custom provider you can extend an existing provider to add new resources or change the way resources are deployed you can read more about extending providers here create a new provider if you have specific requirements that can t be met by extending an existing provider you can create a new provider from scratch you can read more about creating a new provider here improving the ease and flexibility of custom provider development is currently a priority for the nitric team if you need help or want to request a feature get in touch on github or discord edit this page on github have feedback on this page open github issue last updated on jan 5 2026 on this page pre built providers custom providers 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
|
