Platforms Cloud Provisioning Cloud Resources
Core 03 · Cloud Provisioning

Provision the cloud resources your cluster needs — from a blueprint.

Managed databases, caches, queues, storage, node groups, and add-ons — created from curated blueprints in one governed catalog. Pick a blueprint, set a few values, and Atmosly provisions it directly. Encrypted and backed up by default; every request checked by guardrails.

  • Curated blueprints
  • Encrypted by default
  • Guardrail-checked
Search resources… Databases Caches Storage Node groups
Provision

RDS PostgreSQL

v15 · Multi-AZ
Provision

Aurora MySQL

serverless v2
Provision

ElastiCache Redis

cluster mode
Provision

SQS Queue

standard · DLQ
Provision

S3 Bucket

versioned · SSE
Provision

Node Group

m5.xlarge · 2–10
Provision

Persistent Volume

gp3 · 100Gi
Provision

Load Balancer

ALB · TLS
Every resource, governed

Every resource passes the same guardrails

Resources go through the same guardrail flow as everything else: encrypted and backed up by default, checked against your policy at request time, approved or escalated automatically before anything is created.

1 Request
ResourceElastiCache Redis
Sizecache.r6g.large
Scopeprod-eu-west
Byteam-checkout
2 Guardrail checks
Encryption at rest enforced
Region in allow-list · eu-west
Instance type within allow-list
Cost $560/mo · over $500 cap
3 Decision
Escalated

Encryption, region, and instance checks pass — but monthly cost is over the $500 cap, so it routes to an approver instead of provisioning silently. Under the cap, it would have auto-approved.

Blueprints, not boilerplate

A blueprint is the safe default — you just fill the blanks

Each resource is a curated blueprint with production defaults already baked in: encryption, backups, sane sizing, network scope. You set a handful of values; Atmosly creates the resource directly — no modules to write, no console to click through.

RDS PostgreSQL
Managed database blueprint
Encrypted · Multi-AZ · Backups on
Namecheckout-db
Sizedb.r6g.large
Clusterprod-eu-west
EncryptionKMS, at rest
Backups7-day PITR
NetworkVPC-only

01 · Pick a blueprint

Choose from the catalog — databases, caches, queues, storage, node groups, add-ons. Production defaults come built in.

02 · Guardrails check it

Cost, region, instance type, and security baselines are checked against your policy — auto-approved when safe, escalated when not.

03 · Created & tracked

Atmosly provisions the resource directly, links it to the cluster, and tracks it — with a clean, audited path to update or remove it.

What's in the catalog

The building blocks, encrypted and governed

Everything a workload depends on — provisioned the same governed way, whether Atmosly creates it or adopts what you already have.

Managed databases

PostgreSQL, MySQL, Aurora — Multi-AZ, encrypted, with backups enforced by policy.

Caches & queues

Redis, Memcached, SQS — the messaging and caching layer, provisioned to spec.

Storage & networking

Volumes, buckets, and load balancers — versioned, TLS-terminated, and tagged.

Node groups & add-ons

Right-sized pools and cluster add-ons, pinned and installed through guardrails.

The payoff

One catalog, one governance model

One catalog
databases, caches, storage, add-ons
By default
encrypted, backed up, and tagged
Same flow
resources obey the same guardrails as clusters
Reversible
every resource is traceable and undoable
Questions

What teams ask about cloud resources

Can I adopt resources I already created?
Yes. Bring an existing database, bucket, or node group under management and Atmosly governs it through the same catalog and guardrails as anything it provisions — so your estate is consistent, not split between "managed" and "manual."
Are resources encrypted and backed up automatically?
By default. Encryption at rest and backups are enforced as guardrails, so a resource can't be provisioned without them unless your policy explicitly allows an exception — which is itself logged.
What happens if a request exceeds the cost cap?
It escalates instead of provisioning silently. A request within policy auto-approves; one over the cost cap or outside an allow-list routes to an approver — so cost surprises get caught at request time, not on the bill.
Does deleting a resource leave orphans?
No. Every resource is tracked with the request that created it, so teardown is clean and reversible. The Cost Intelligence core also flags idle resources and orphaned volumes, so nothing lingers unnoticed.

Provision everything from one catalog.

Connect a cluster, read-only to start. Browse the resource catalog and watch a governed request flow through the guardrails in minutes. Free, no sales call.

Browse the catalog → Book a 15-min walkthrough