> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Systems Manager (SSM)

> Systems Manager (SSM) APIs with Cloud Adapter.

This page describes how Systems Manager (SSM) maps to services in the environment where the application runs, including backend choices, supported operations and service-specific behavior.

## Supported environments

* Akamai
* Azure
* Google Cloud
* OCI
* Private Kubernetes
* Scaleway

Check the operation and capability tables for the behavior your application depends on. A supported environment does not imply that every operation of the origin service is available.

## How the backends compare

Each row compares a capability of Systems Manager (SSM) with its adaptation on each backend.
A dash means this profile does not state the capability for that backend.

### Cloud Adapter

| Capability | Systems Manager (SSM) | Akamai, Private Kubernetes, and Scaleway | Azure | Google Cloud · Secret Manager | Google Cloud · Google Parameter Manager | OCI |
| - | - | - | - | - | - | - |
| API served · what your app calls | Parameter Store API | the same API, served from durable adapter state | the same API, served from durable adapter state | the same API, served from durable adapter state | the same API, served from durable adapter state | the same API, served from durable adapter state |
| Where parameters live · the backing store | AWS-managed storage | durable parameter records + Kubernetes Secrets backend copy | durable parameter records + Azure App Configuration backend copy | durable parameter records + Google Secret Manager backend copy | durable parameter records + Google Parameter Manager backend copy | durable parameter records + OCI Vault backend copy |
| Encryption at rest · SecureString handling | KMS-encrypted SecureString | all three type markers are retained; protect durable state and configure Kubernetes storage encryption. Base64 encoding does not encrypt the backend copy | String and StringList are supported; SecureString remains outside the App Configuration mapping. Direct Key Vault access is a separate application path | all three type markers are retained in durable state; Secret Manager encrypts its provider copy at rest | all three type markers are retained in durable state; Parameter Manager encrypts its provider copy at rest; sensitivity follows actual values | all three type markers are retained in durable state; the configured OCI vault key encrypts the provider copy |
| Path hierarchies · by-path reads | native | caller-scoped record queries; no per-value provider reads | caller-scoped record queries; no per-value provider reads | caller-scoped record queries; no per-value provider reads | caller-scoped record queries; no per-value provider reads | caller-scoped record queries; no per-value provider reads |
| Versions & labels · history | 100-version history + labels | only the latest value and increasing AWS version counter are retained; previous values and named labels are unsupported | numeric history is retained; the adapter owns AWS version selection. Named SSM labels remain outside this mapping | retained values and adapter-owned label references provide parameter history and named labels; native aliases do not decide AWS reads | retained values and adapter-owned label references provide parameter history and named labels; Parameter Manager has no native version aliases | - |
| API coverage | full | partial | partial | partial | partial | partial |
| Versions · history | 100-version history + labels | - | - | - | - | numeric history is retained; the adapter owns AWS version identity and selection independently of native OCI versionNumber values |
| Delete semantics · DeleteParameter | immediate delete | - | - | - | - | leaves AWS reads immediately; native secret cleanup is scheduled separately |

## On Akamai, Private Kubernetes, and Scaleway

### Kubernetes Secrets

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Consumed parameters (read-only references) | Build & deploy | Supported | Common | a parameter the stack reads but does not own is supplied by the customer during installation; that supply path is distinct from runtime parameter management |
| Filters & discovery (DescribeParameters / ParameterFilters) | Discovery | Partial | Full surface | DescribeParameters serves paginated metadata without values; complete ParameterFilters behavior is outside the documented contract |
| Change notifications | Events | Out of scope | Full surface | parameter-change events are outside this mapping |
| Batch reads (GetParameters) | Parameters | Supported | Common | reads caller-scoped parameter records and partitions found and missing names |
| Hierarchies & by-path reads (GetParametersByPath) | Parameters | Supported | Common | queries live adapter records by path, applies recursion rules, and returns paginated results; no provider value fetch per returned parameter |
| Parameter reads (GetParameter) | Parameters | Supported | Common | reads the current value, type, and AWS version from the caller-scoped durable parameter record; the backend copy is reconciled separately |
| Parameter writes & deletes | Parameters | Supported | Common | PutParameter creates or updates durable parameter state and reconciles the backend; DeleteParameter withdraws reads while backend cleanup proceeds separately |
| Parameter policies & Advanced tier | Policies | Out of scope | Most usage | parameter policies and the Advanced tier are outside the documented contract |
| Public & shared parameters | Scope | Out of scope | Full surface | AWS-published public parameters and cross-account shared parameters are outside this mapping |
| The wider Systems Manager suite | Scope | Out of scope | Full surface | Parameter Store only: remote commands, sessions, patching, state management, and documents remain out of scope |
| Custom encryption keys (KeyId) | Types | Out of scope | Most usage | custom per-parameter AWS KMS keys are unsupported; protect durable adapter state and configure the backend copy independently |
| Parameter types (String / StringList / SecureString) | Types | Supported | Common | all three type markers are retained; protect durable state and configure Kubernetes storage encryption. Base64 encoding does not encrypt the backend copy |
| Reading ciphertext (WithDecryption=false) | Types | Out of scope | Most usage | SecureString reads require WithDecryption=true; the adapter does not return AWS KMS ciphertext |
| Versions & labels | Versions | Out of scope | Most usage | only the latest value and increasing AWS version counter are retained; previous values and named labels are unsupported |

#### Requests and durable parameter state

Your application keeps its AWS SDK Parameter Store calls; with Cloud Adapter they go to the Tensor9 adapter. The adapter saves a record of each parameter: name, type, current value, version counter, description and tags. Reads use that record. A background worker reconciles the current value to Kubernetes Secrets, meaning it copies the value there and keeps the copy up to date.

`PutParameter` creates a parameter, or updates it when `Overwrite=true`. Writing an existing name with `Overwrite=false` returns `ParameterAlreadyExists`. Each write increases the AWS version counter and waits a limited time for the value to reach Kubernetes Secrets; if Kubernetes Secrets rejects the value outright, the error is returned. `DeleteParameter` removes the parameter from reads at once, and backend cleanup proceeds separately.

Direct provider edits in Kubernetes Secrets do not update the AWS parameter record and can be overwritten by the next copy.

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Kubernetes Secrets.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBLdWJlcm5ldGVzIFNlY3JldHMuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojMzM0MTU1fTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZmZmZmZmO3N0cm9rZTojY2JkNWUxIi8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwZjE3MmEiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6IzY0NzQ4YiIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZWNmZGY1O3N0cm9rZTojMDQ3ODU3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMDQ3ODU3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojNjQ3NDhiIi8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjNjQ3NDhiIj5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6I2ZmZmZmZjtzdHJva2U6I2NiZDVlMSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzBmMTcyYTsgZm9udC1zaXplOjExcHgiPkt1YmVybmV0ZXMgU2VjcmV0czwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Kubernetes Secrets.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBLdWJlcm5ldGVzIFNlY3JldHMuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojY2JkNWUxfTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMWUyOTNiO3N0cm9rZTojNDc1NTY5Ii8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICNmMWY1ZjkiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6Izk0YTNiOCIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMDY0ZTNiO3N0cm9rZTojNmVlN2I3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNmVlN2I3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojOTRhM2I4Ii8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjOTRhM2I4Ij5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6IzFlMjkzYjtzdHJva2U6IzQ3NTU2OSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogI2YxZjVmOTsgZm9udC1zaXplOjExcHgiPkt1YmVybmV0ZXMgU2VjcmV0czwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

Reads come from the adapter's records; the storage service holds a copy kept up to date in the background.

#### Batch reads, paths, and metadata

`GetParameter` and `GetParameters` read the records the caller is allowed to see. A batch read returns found and missing names separately. `GetParametersByPath` picks current records by path, follows the recursion setting, and returns pages in name order. It does not fetch each matching value from Kubernetes Secrets, so a deep path does not cost one storage-service read per parameter.

DescribeParameters returns paginated metadata, including names, types, versions and descriptions, without parameter values. Tag operations update a parameter's metadata.

#### Versions and labels

This mapping retains the latest value and its increasing version counter. Previous values and named SSM labels are unsupported. The counter records how many writes happened; it does not make old values readable. Choose a mapping that keeps history if your application needs it.

#### Storage and encryption

A Kubernetes Secret holds a copy of the current value in the customer cluster, accessed with the deployment's service account. AWS reads come from the adapter's parameter records, not from a Kubernetes Secret lookup on each request, and the version counter belongs to those records.

All three parameter type markers are kept. Kubernetes Secret values are base64-encoded, and base64 is not encryption. Configure Kubernetes access control and storage encryption, and protect the adapter's saved state and backups. This option keeps everything inside the customer cluster, including in disconnected deployments.

#### Limitations

Where this differs from Parameter Store

* **Custom KMS keys, parameter policies and the Advanced tier are not supported.** A per-parameter KMS key, parameter policies and Advanced-tier parameters are rejected.
* **SecureString reads behave differently: they need decryption.** Reading AWS ciphertext with `WithDecryption=false` is not supported. Where the mapping supports SecureString, read it with `WithDecryption=true`.
* **Public, shared and change-event parameters are not supported.** AWS-published public parameters, parameters shared from another account, and parameter-change events are outside this mapping.
* **Full `ParameterFilters` behavior is not supported.** `DescribeParameters` lists metadata, but complete `ParameterFilters` behavior is outside the documented scope.
* **Systems Manager features beyond Parameter Store are not supported.** Run Command, Session Manager, patching, State Manager and documents are outside this mapping.

#### Other considerations

**Before switching the application.** Load values through the Parameter Store API, and check reads, overwrites and deletion. Existing AWS values and history in Kubernetes Secrets are not imported automatically. Deployment can also set the stack's own literal values from the release. Parameters the stack only reads are supplied by the customer during installation, which is separate from managing parameters at runtime.

**Operating it.** Protect and back up the adapter's saved state as well as Kubernetes Secrets. The storage service, access permissions, the background copy and the availability of the adapter's state all affect operation.

**Performance figures.** Historical direct-proxy measurements describe their recorded request path; they do not establish Max latency, throughput, or per-read provider charges.

#### Example monthly charges

This Tensor9 Cloud Adapter scenario estimates service charges for the named origin and target services. Adapter hosting and commercial Tensor9 fees need separate allocations. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method and what the estimates include.

##### SSM Parameter Store · Standard read requests

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard read requests. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/944ba40fc69dff1a09917b010fbcb1121e1f68a64ad2174d410658e68613e454-light.svg)

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/19f9419b2a6f0a3cd5d685853dde305eecb851b3ad838f19d732e21189dc32af-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard read requests (operations/s) | Systems Manager (SSM) | Target scenario | Kubernetes Secret | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 0 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 1 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 1 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 10 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 10 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 100 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 100 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 1,000 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 1,000 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 10,000 | 0.00 | Kubernetes Secret (one copy) | 1,144.34 | 1,144.34 |
| 10,000 | 0.00 | Kubernetes Secret (two copies) | 2,288.68 | 2,288.68 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 operations/s to 32 vCPU, 128 GiB memory and 100 GiB SSD at 10,000 operations/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Kubernetes Secret (one copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Kubernetes Secret (one copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Kubernetes Secret (one copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Kubernetes Secret (one copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Kubernetes Secret (one copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Kubernetes Secret (one copy) | Representative value size | 1,024 | bytes |
| Kubernetes Secret (one copy) | Versions retained in adapter state | 10 | versions/object |
| Kubernetes Secret (one copy) | Provider revisions retained per logical object | 2 | versions/object |
| Kubernetes Secret (one copy) | Physical record / payload storage | 1.5 | multiplier |
| Kubernetes Secret (one copy) | Provider reconciliation checks | 30 | checks/object-month |
| Kubernetes Secret (one copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Kubernetes Secret (one copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Kubernetes Secret (one copy) | Values per standard read request | 1 | parameters/request |
| Kubernetes Secret (one copy) | Paid interactions that read values | 1 | fraction |
| Kubernetes Secret (one copy) | Target price guess · read | 0 | USD/read |
| Kubernetes Secret (one copy) | Target price guess · write | 0 | USD/write |
| Kubernetes Secret (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Kubernetes Secret (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Kubernetes Secret (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Kubernetes Secret (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Kubernetes Secret (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Kubernetes Secret (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Kubernetes Secret (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Kubernetes Secret (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Kubernetes Secret (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Kubernetes Secret (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Kubernetes Secret (one copy) | Target price guess · input token | 0 | USD/input token |
| Kubernetes Secret (one copy) | Target price guess · output token | 0 | USD/output token |
| Kubernetes Secret (one copy) | Target monthly base charge | 0 | USD/month |
| Kubernetes Secret (one copy) | Approximate target service minimum | 0 | USD/month |
| Kubernetes Secret (one copy) | Minimum primary CPU | 2 | vCPU |
| Kubernetes Secret (one copy) | Minimum primary RAM | 8 | GiB |
| Kubernetes Secret (one copy) | Minimum primary disk | 100 | GiB |
| Kubernetes Secret (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Kubernetes Secret (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Kubernetes Secret (one copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Kubernetes Secret (one copy) | Planning peak / mean work | 2 | multiplier |
| Kubernetes Secret (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Kubernetes Secret (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Kubernetes Secret (one copy) | Planning disk utilization | 0.8 | fraction |
| Kubernetes Secret (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Kubernetes Secret (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Kubernetes Secret (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Kubernetes Secret (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Kubernetes Secret (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Kubernetes Secret (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Kubernetes Secret (two copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Kubernetes Secret (two copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Kubernetes Secret (two copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Kubernetes Secret (two copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Kubernetes Secret (two copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Kubernetes Secret (two copies) | Representative value size | 1,024 | bytes |
| Kubernetes Secret (two copies) | Versions retained in adapter state | 10 | versions/object |
| Kubernetes Secret (two copies) | Provider revisions retained per logical object | 2 | versions/object |
| Kubernetes Secret (two copies) | Physical record / payload storage | 1.5 | multiplier |
| Kubernetes Secret (two copies) | Provider reconciliation checks | 30 | checks/object-month |
| Kubernetes Secret (two copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Kubernetes Secret (two copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Kubernetes Secret (two copies) | Values per standard read request | 1 | parameters/request |
| Kubernetes Secret (two copies) | Paid interactions that read values | 1 | fraction |
| Kubernetes Secret (two copies) | Target price guess · read | 0 | USD/read |
| Kubernetes Secret (two copies) | Target price guess · write | 0 | USD/write |
| Kubernetes Secret (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Kubernetes Secret (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Kubernetes Secret (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Kubernetes Secret (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Kubernetes Secret (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Kubernetes Secret (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Kubernetes Secret (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Kubernetes Secret (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Kubernetes Secret (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Kubernetes Secret (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Kubernetes Secret (two copies) | Target price guess · input token | 0 | USD/input token |
| Kubernetes Secret (two copies) | Target price guess · output token | 0 | USD/output token |
| Kubernetes Secret (two copies) | Target monthly base charge | 0 | USD/month |
| Kubernetes Secret (two copies) | Approximate target service minimum | 0 | USD/month |
| Kubernetes Secret (two copies) | Minimum primary CPU | 2 | vCPU |
| Kubernetes Secret (two copies) | Minimum primary RAM | 8 | GiB |
| Kubernetes Secret (two copies) | Minimum primary disk | 100 | GiB |
| Kubernetes Secret (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Kubernetes Secret (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Kubernetes Secret (two copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Kubernetes Secret (two copies) | Planning peak / mean work | 2 | multiplier |
| Kubernetes Secret (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Kubernetes Secret (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Kubernetes Secret (two copies) | Planning disk utilization | 0.8 | fraction |
| Kubernetes Secret (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Kubernetes Secret (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Kubernetes Secret (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Kubernetes Secret (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Kubernetes Secret (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Kubernetes Secret (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Self-hosted target: Tensor9-built Parameter Store service; no vendor charge. Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor charge: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-c9e30a21ca59da8a1b0b6ec5bb0dd3d3105fa347` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

##### SSM Parameter Store · Standard parameters

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard parameters. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/a3214973949469fa96b98d402528fa4913b72948de878f712fc1ab9e4c96e32b-light.svg)

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/77646c7701eeb54858c07377a6f7b9b04b1dc459ed2ae585d68ccebc725d1ee8-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard parameters (parameters) | Systems Manager (SSM) | Target scenario | Kubernetes Secret | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 0 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 10 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 10 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 100 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 100 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 1,000 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 1,000 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 10,000 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 10,000 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |
| 100,000 | 0.00 | Kubernetes Secret (one copy) | 80.90 | 80.90 |
| 100,000 | 0.00 | Kubernetes Secret (two copies) | 161.79 | 161.79 |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD at every sample.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Kubernetes Secret (one copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Kubernetes Secret (one copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Kubernetes Secret (one copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Kubernetes Secret (one copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Kubernetes Secret (one copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Kubernetes Secret (one copy) | Representative value size | 1,024 | bytes |
| Kubernetes Secret (one copy) | Versions retained in adapter state | 10 | versions/object |
| Kubernetes Secret (one copy) | Provider revisions retained per logical object | 2 | versions/object |
| Kubernetes Secret (one copy) | Physical record / payload storage | 1.5 | multiplier |
| Kubernetes Secret (one copy) | Provider reconciliation checks | 30 | checks/object-month |
| Kubernetes Secret (one copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Kubernetes Secret (one copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Kubernetes Secret (one copy) | Values per standard read request | 1 | parameters/request |
| Kubernetes Secret (one copy) | Paid interactions that read values | 1 | fraction |
| Kubernetes Secret (one copy) | Target price guess · read | 0 | USD/read |
| Kubernetes Secret (one copy) | Target price guess · write | 0 | USD/write |
| Kubernetes Secret (one copy) | Target price guess · provider operation | 0 | USD/provider operation |
| Kubernetes Secret (one copy) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Kubernetes Secret (one copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Kubernetes Secret (one copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Kubernetes Secret (one copy) | Target list price · network GiB | 0.12 | USD/network GiB |
| Kubernetes Secret (one copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Kubernetes Secret (one copy) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Kubernetes Secret (one copy) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Kubernetes Secret (one copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Kubernetes Secret (one copy) | Target price guess · resource-month | 0 | USD/resource-month |
| Kubernetes Secret (one copy) | Target price guess · input token | 0 | USD/input token |
| Kubernetes Secret (one copy) | Target price guess · output token | 0 | USD/output token |
| Kubernetes Secret (one copy) | Target monthly base charge | 0 | USD/month |
| Kubernetes Secret (one copy) | Approximate target service minimum | 0 | USD/month |
| Kubernetes Secret (one copy) | Minimum primary CPU | 2 | vCPU |
| Kubernetes Secret (one copy) | Minimum primary RAM | 8 | GiB |
| Kubernetes Secret (one copy) | Minimum primary disk | 100 | GiB |
| Kubernetes Secret (one copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Kubernetes Secret (one copy) | Allocated share of provisioned cost | 1 | fraction |
| Kubernetes Secret (one copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Kubernetes Secret (one copy) | Planning peak / mean work | 2 | multiplier |
| Kubernetes Secret (one copy) | Planning primary CPU utilization | 0.7 | fraction |
| Kubernetes Secret (one copy) | Resident state reserved in RAM | 0.1 | fraction |
| Kubernetes Secret (one copy) | Planning disk utilization | 0.8 | fraction |
| Kubernetes Secret (one copy) | Maintenance and log disk reserve | 20 | GiB |
| Kubernetes Secret (one copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Kubernetes Secret (one copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Kubernetes Secret (one copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Kubernetes Secret (one copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Kubernetes Secret (one copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Kubernetes Secret (two copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Kubernetes Secret (two copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Kubernetes Secret (two copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Kubernetes Secret (two copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Kubernetes Secret (two copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Kubernetes Secret (two copies) | Representative value size | 1,024 | bytes |
| Kubernetes Secret (two copies) | Versions retained in adapter state | 10 | versions/object |
| Kubernetes Secret (two copies) | Provider revisions retained per logical object | 2 | versions/object |
| Kubernetes Secret (two copies) | Physical record / payload storage | 1.5 | multiplier |
| Kubernetes Secret (two copies) | Provider reconciliation checks | 30 | checks/object-month |
| Kubernetes Secret (two copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Kubernetes Secret (two copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Kubernetes Secret (two copies) | Values per standard read request | 1 | parameters/request |
| Kubernetes Secret (two copies) | Paid interactions that read values | 1 | fraction |
| Kubernetes Secret (two copies) | Target price guess · read | 0 | USD/read |
| Kubernetes Secret (two copies) | Target price guess · write | 0 | USD/write |
| Kubernetes Secret (two copies) | Target price guess · provider operation | 0 | USD/provider operation |
| Kubernetes Secret (two copies) | Target list price · GiB-month | 0.1 | USD/GiB-month |
| Kubernetes Secret (two copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Kubernetes Secret (two copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Kubernetes Secret (two copies) | Target list price · network GiB | 0.12 | USD/network GiB |
| Kubernetes Secret (two copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Kubernetes Secret (two copies) | Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Kubernetes Secret (two copies) | Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Kubernetes Secret (two copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Kubernetes Secret (two copies) | Target price guess · resource-month | 0 | USD/resource-month |
| Kubernetes Secret (two copies) | Target price guess · input token | 0 | USD/input token |
| Kubernetes Secret (two copies) | Target price guess · output token | 0 | USD/output token |
| Kubernetes Secret (two copies) | Target monthly base charge | 0 | USD/month |
| Kubernetes Secret (two copies) | Approximate target service minimum | 0 | USD/month |
| Kubernetes Secret (two copies) | Minimum primary CPU | 2 | vCPU |
| Kubernetes Secret (two copies) | Minimum primary RAM | 8 | GiB |
| Kubernetes Secret (two copies) | Minimum primary disk | 100 | GiB |
| Kubernetes Secret (two copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Kubernetes Secret (two copies) | Allocated share of provisioned cost | 1 | fraction |
| Kubernetes Secret (two copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Kubernetes Secret (two copies) | Planning peak / mean work | 2 | multiplier |
| Kubernetes Secret (two copies) | Planning primary CPU utilization | 0.7 | fraction |
| Kubernetes Secret (two copies) | Resident state reserved in RAM | 0.1 | fraction |
| Kubernetes Secret (two copies) | Planning disk utilization | 0.8 | fraction |
| Kubernetes Secret (two copies) | Maintenance and log disk reserve | 20 | GiB |
| Kubernetes Secret (two copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Kubernetes Secret (two copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Kubernetes Secret (two copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Kubernetes Secret (two copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Kubernetes Secret (two copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Self-hosted target: Tensor9-built Parameter Store service; no vendor charge. Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor charge: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Compute Engine general-purpose machine pricing: [https://cloud.google.com/products/compute/pricing/general-purpose](https://cloud.google.com/products/compute/pricing/general-purpose)
* Disk and image pricing: [https://cloud.google.com/compute/disks-image-pricing](https://cloud.google.com/compute/disks-image-pricing)
* Network pricing: [https://cloud.google.com/vpc/network-pricing](https://cloud.google.com/vpc/network-pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-c9e30a21ca59da8a1b0b6ec5bb0dd3d3105fa347` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

**SSM Parameter Store → Kubernetes Secrets: Authored native-usage planning example.** Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts.

Scenario source region: us-east-1. Scenario target region: us-central1. Currency: USD.

| Monthly component | USD |
| - | -: |
| Origin: Standard parameter inventory | 0.00 |
| Origin: Advanced parameter inventory | 0.00 |
| Origin: Standard-throughput read API calls | 0.00 |
| Origin: Paid parameter interactions | 0.00 |
| Origin: Standard-throughput parameter mutations | 0.00 |
| Target: Provisioned primary CPU | 46.15 |
| Target: Provisioned primary RAM | 24.74 |
| Target: Provisioned primary disk | 10.00 |
| Target: Selected billable network | 0.00 |
| Target: Independent provisioned resources | 0.00 |
| Target: Independent managed resources | 0.00 |
| **Origin service subtotal** | **0.00** |
| **Target service subtotal** | **80.90** |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD for this scenario.

Unestimated components: Adapter hosting, Tensor9 fees. A modeled adapted total and savings require these costs.

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

**Scenario assumptions**

| Input | Value | Unit |
| - | -: | - |
| Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Representative value size | 1,024 | bytes |
| Versions retained in adapter state | 10 | versions/object |
| Provider revisions retained per logical object | 2 | versions/object |
| Physical record / payload storage | 1.5 | multiplier |
| Provider reconciliation checks | 30 | checks/object-month |
| Provider calls per current-value mutation | 2 | operations/mutation |
| Provider reconciliation retry multiplier | 1.1 | multiplier |
| Values per standard read request | 1 | parameters/request |
| Paid interactions that read values | 1 | fraction |
| Target price guess · read | 0 | USD/read |
| Target price guess · write | 0 | USD/write |
| Target price guess · provider operation | 0 | USD/provider operation |
| Target list price · GiB-month | 0.1 | USD/GiB-month |
| Target price guess · published GiB | 0 | USD/published GiB |
| Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Target list price · network GiB | 0.12 | USD/network GiB |
| Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Target list price · vCPU-hour | 0.031611 | USD/vCPU-hour |
| Target list price · GiB-hour | 0.004237 | USD/GiB-hour |
| Target price guess · resource-hour | 0 | USD/resource-hour |
| Target price guess · resource-month | 0 | USD/resource-month |
| Target price guess · input token | 0 | USD/input token |
| Target price guess · output token | 0 | USD/output token |
| Target monthly base charge | 0 | USD/month |
| Approximate target service minimum | 0 | USD/month |
| Minimum primary CPU | 2 | vCPU |
| Minimum primary RAM | 8 | GiB |
| Minimum primary disk | 100 | GiB |
| Additional full-price standby copy | 0 | 0 or 1 |
| Allocated share of provisioned cost | 1 | fraction |
| Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Planning peak / mean work | 2 | multiplier |
| Planning primary CPU utilization | 0.7 | fraction |
| Resident state reserved in RAM | 0.1 | fraction |
| Planning disk utilization | 0.8 | fraction |
| Maintenance and log disk reserve | 20 | GiB |
| Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Dependent object sink write price guess | 0.000005 | USD/write |
| Standard parameter inventory | 1,000 | parameter-month |
| Advanced parameter inventory | 0 | parameter-month |
| Standard-throughput read API calls | 1,000,000 | requests |
| Paid parameter interactions | 0 | parameter-interactions |
| Standard-throughput parameter mutations | 10,000 | requests |

* Translated reads: 1,000,000 operations.

* Translated writes: 10,000 operations.

* Translated resident physical data: 0.0143 GiB-month.

* Native provider operations: 55,000 operations.

* Published payload: 0 GiB.

* Delivered payload: 0 GiB.

* Allocated execution CPU: 0 vCPU-hour.

* Allocated execution RAM: 0 GiB-hour.

* Independent resource allocation: 0 resource-hour.

* Independent inventory: 2,000 resource-month.

* Input tokens: 0 tokens.

* Output tokens: 0 tokens.

* Billable network: 0 GiB.

* Dependent object sink retained data: 0 GiB-month.

* Dependent object sink writes: 0 writes.

* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.

* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.

* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.

* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.

* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.

* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.

* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.

* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.

* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.

* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.

* Self-hosted target: Tensor9-built Parameter Store service; no vendor charge. Selected CPU, RAM and physical disk allocation grow with workload; no per-operation price is assumed. No vendor charge: the target runs on the customer's Kubernetes nodes, so CPU, RAM and disk bill at the Kubernetes node reference rates, Compute Engine N2 in us-central1 (USD 0.031611/vCPU-hour, 0.004237/GiB-hour) with pd-balanced disk (0.10/GiB-month) and Premium Tier egress. The cost-optimized E2 series lists 0.02181159/vCPU-hour and 0.00292353/GiB-hour; AWS m6i/r6i and Azure D2s v5/E2s v5 both decompose to 0.033/vCPU-hour and 0.00375/GiB-hour. Requested CPU and RAM are billed; node bin-packing waste, system reservations and the cluster control-plane fee are not.

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.

* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.

* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.

* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.

* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.

* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).

* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.

* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.

* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

List prices read: 2026-10-22. Model: `plan-c9e30a21ca59da8a1b0b6ec5bb0dd3d3105fa347` / `2026-10-22.planning.2`. Scenario: `planning-example`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Compute Engine general-purpose machine pricing](https://cloud.google.com/products/compute/pricing/general-purpose), [Disk and image pricing](https://cloud.google.com/compute/disks-image-pricing), [Network pricing](https://cloud.google.com/vpc/network-pricing).

## On Azure

### Azure App Configuration

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Consumed parameters (read-only references) | Build & deploy | Supported | Common | a parameter the stack reads but does not own is supplied by the customer during installation; that supply path is distinct from runtime parameter management |
| Filters & discovery (DescribeParameters / ParameterFilters) | Discovery | Partial | Full surface | DescribeParameters serves paginated metadata without values; complete ParameterFilters behavior is outside the documented contract |
| Change notifications | Events | Out of scope | Full surface | parameter-change events are outside this mapping |
| Batch reads (GetParameters) | Parameters | Supported | Common | reads caller-scoped parameter records and partitions found and missing names |
| Hierarchies & by-path reads (GetParametersByPath) | Parameters | Supported | Common | queries live adapter records by path, applies recursion rules, and returns paginated results; no provider value fetch per returned parameter |
| Parameter reads (GetParameter) | Parameters | Supported | Common | reads the current value, type, and AWS version from the caller-scoped durable parameter record; the backend copy is reconciled separately |
| Parameter writes & deletes | Parameters | Supported | Common | PutParameter creates or updates durable parameter state and reconciles the backend; DeleteParameter withdraws reads while backend cleanup proceeds separately |
| Parameter policies & Advanced tier | Policies | Out of scope | Most usage | parameter policies and the Advanced tier are outside the documented contract |
| Public & shared parameters | Scope | Out of scope | Full surface | AWS-published public parameters and cross-account shared parameters are outside this mapping |
| The wider Systems Manager suite | Scope | Out of scope | Full surface | Parameter Store only: remote commands, sessions, patching, state management, and documents remain out of scope |
| Custom encryption keys (KeyId) | Types | Out of scope | Most usage | custom per-parameter AWS KMS keys are unsupported; protect durable adapter state and configure the backend copy independently |
| Parameter types (String / StringList / SecureString) | Types | Partial | Common | String and StringList are supported; SecureString remains outside the App Configuration mapping. Direct Key Vault access is a separate application path |
| Reading ciphertext (WithDecryption=false) | Types | Out of scope | Most usage | SecureString reads require WithDecryption=true; the adapter does not return AWS KMS ciphertext |
| Versions & labels | Versions | Partial | Most usage | numeric history is retained; the adapter owns AWS version selection. Named SSM labels remain outside this mapping |

#### Requests and durable parameter state

Your application keeps its AWS SDK Parameter Store calls; with Cloud Adapter they go to the Tensor9 adapter. The adapter saves a record of each parameter: name, type, current value, version counter, description and tags. Reads use that record. A background worker reconciles the current value to Azure App Configuration, meaning it copies the value there and keeps the copy up to date.

`PutParameter` creates a parameter, or updates it when `Overwrite=true`. Writing an existing name with `Overwrite=false` returns `ParameterAlreadyExists`. Each write increases the AWS version counter and waits a limited time for the value to reach Azure App Configuration; if Azure App Configuration rejects the value outright, the error is returned. `DeleteParameter` removes the parameter from reads at once, and backend cleanup proceeds separately.

Direct provider edits in Azure App Configuration do not update the AWS parameter record and can be overwritten by the next copy.

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Azure App Configuration.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBBenVyZSBBcHAgQ29uZmlndXJhdGlvbi4iPjxzdHlsZT50ZXh0e2ZvbnQtZmFtaWx5OkludGVyLC1hcHBsZS1zeXN0ZW0sQmxpbmtNYWNTeXN0ZW1Gb250LCdTZWdvZSBVSScsUm9ib3RvLCdIZWx2ZXRpY2EgTmV1ZScsQXJpYWwsc2Fucy1zZXJpZjtmaWxsOiMzMzQxNTV9PC9zdHlsZT4KPHJlY3QgeD0iMTQiIHk9IjY1IiB3aWR0aD0iMTU1IiBoZWlnaHQ9Ijc4IiByeD0iMTIiIHN0eWxlPSJmaWxsOiNmZmZmZmY7c3Ryb2tlOiNjYmQ1ZTEiLz4KPHRleHQgeD0iOTEiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzBmMTcyYSI+WW91ciBhcHBsaWNhdGlvbjwvdGV4dD4KPHRleHQgeD0iOTEiIHk9IjExNiIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2NDc0OGIiPlBhcmFtZXRlciBTdG9yZSBTREs8L3RleHQ+CjxwYXRoIGQ9Ik0xNjksMTA0IEgyNDQgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojNjQ3NDhiIi8+CjxyZWN0IHg9IjI1MCIgeT0iMzgiIHdpZHRoPSIyODIiIGhlaWdodD0iMTMwIiByeD0iMTIiIHN0eWxlPSJmaWxsOiNlY2ZkZjU7c3Ryb2tlOiMwNDc4NTciLz4KPHRleHQgeD0iMzkxIiB5PSI2OSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDcwMCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPkR1cmFibGUgcGFyYW1ldGVyIHJlY29yZDwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSI5NCIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2NDc0OGIiPk5hbWUsIHR5cGUsIHZhbHVlLCB2ZXJzaW9uPC90ZXh0Pgo8dGV4dCB4PSIzOTEiIHk9IjExNSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2NDc0OGIiPkRlc2NyaXB0aW9uIGFuZCB0YWdzPC90ZXh0Pgo8dGV4dCB4PSIzOTEiIHk9IjE0MSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDEwLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzA0Nzg1NyI+UmVhZHMgYW5kIHdyaXRlcyB1c2UgdGhpczwvdGV4dD4KPHBhdGggZD0iTTUzMiwxMDQgSDYwMyBsLTksLTUgbTksNSBsLTksNSIgZmlsbD0ibm9uZSIgc3Ryb2tlLXdpZHRoPSIyIiBzdHlsZT0ic3Ryb2tlOiM2NDc0OGIiLz4KPHRleHQgeD0iNTY3IiB5PSI4NiIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDEwcHggJ1NGIE1vbm8nLCB1aS1tb25vc3BhY2UsICdKZXRCcmFpbnMgTW9ubycsIE1lbmxvLCBtb25vc3BhY2U7IGZpbGw6ICM2NDc0OGIiPnJlY29uY2lsZTwvdGV4dD4KPHJlY3QgeD0iNjA5IiB5PSI2NSIgd2lkdGg9IjIxMyIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZmZmZmZmO3N0cm9rZTojY2JkNWUxIi8+Cjx0ZXh0IHg9IjcxNSIgeT0iOTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA2NTAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMGYxNzJhOyBmb250LXNpemU6MTFweCI+QXp1cmUgQXBwIENvbmZpZ3VyYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjcxNSIgeT0iMTE2IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzY0NzQ4YiI+SG9sZHMgYSBjb3B5PC90ZXh0Pgo8L3N2Zz4=)

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Azure App Configuration.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBBenVyZSBBcHAgQ29uZmlndXJhdGlvbi4iPjxzdHlsZT50ZXh0e2ZvbnQtZmFtaWx5OkludGVyLC1hcHBsZS1zeXN0ZW0sQmxpbmtNYWNTeXN0ZW1Gb250LCdTZWdvZSBVSScsUm9ib3RvLCdIZWx2ZXRpY2EgTmV1ZScsQXJpYWwsc2Fucy1zZXJpZjtmaWxsOiNjYmQ1ZTF9PC9zdHlsZT4KPHJlY3QgeD0iMTQiIHk9IjY1IiB3aWR0aD0iMTU1IiBoZWlnaHQ9Ijc4IiByeD0iMTIiIHN0eWxlPSJmaWxsOiMxZTI5M2I7c3Ryb2tlOiM0NzU1NjkiLz4KPHRleHQgeD0iOTEiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogI2YxZjVmOSI+WW91ciBhcHBsaWNhdGlvbjwvdGV4dD4KPHRleHQgeD0iOTEiIHk9IjExNiIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM5NGEzYjgiPlBhcmFtZXRlciBTdG9yZSBTREs8L3RleHQ+CjxwYXRoIGQ9Ik0xNjksMTA0IEgyNDQgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojOTRhM2I4Ii8+CjxyZWN0IHg9IjI1MCIgeT0iMzgiIHdpZHRoPSIyODIiIGhlaWdodD0iMTMwIiByeD0iMTIiIHN0eWxlPSJmaWxsOiMwNjRlM2I7c3Ryb2tlOiM2ZWU3YjciLz4KPHRleHQgeD0iMzkxIiB5PSI2OSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDcwMCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPkR1cmFibGUgcGFyYW1ldGVyIHJlY29yZDwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSI5NCIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM5NGEzYjgiPk5hbWUsIHR5cGUsIHZhbHVlLCB2ZXJzaW9uPC90ZXh0Pgo8dGV4dCB4PSIzOTEiIHk9IjExNSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDExcHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM5NGEzYjgiPkRlc2NyaXB0aW9uIGFuZCB0YWdzPC90ZXh0Pgo8dGV4dCB4PSIzOTEiIHk9IjE0MSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDEwLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzZlZTdiNyI+UmVhZHMgYW5kIHdyaXRlcyB1c2UgdGhpczwvdGV4dD4KPHBhdGggZD0iTTUzMiwxMDQgSDYwMyBsLTksLTUgbTksNSBsLTksNSIgZmlsbD0ibm9uZSIgc3Ryb2tlLXdpZHRoPSIyIiBzdHlsZT0ic3Ryb2tlOiM5NGEzYjgiLz4KPHRleHQgeD0iNTY3IiB5PSI4NiIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDEwcHggJ1NGIE1vbm8nLCB1aS1tb25vc3BhY2UsICdKZXRCcmFpbnMgTW9ubycsIE1lbmxvLCBtb25vc3BhY2U7IGZpbGw6ICM5NGEzYjgiPnJlY29uY2lsZTwvdGV4dD4KPHJlY3QgeD0iNjA5IiB5PSI2NSIgd2lkdGg9IjIxMyIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMWUyOTNiO3N0cm9rZTojNDc1NTY5Ii8+Cjx0ZXh0IHg9IjcxNSIgeT0iOTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA2NTAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjZjFmNWY5OyBmb250LXNpemU6MTFweCI+QXp1cmUgQXBwIENvbmZpZ3VyYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjcxNSIgeT0iMTE2IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogMTFweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzk0YTNiOCI+SG9sZHMgYSBjb3B5PC90ZXh0Pgo8L3N2Zz4=)

Reads come from the adapter's records; the storage service holds a copy kept up to date in the background.

#### Batch reads, paths, and metadata

`GetParameter` and `GetParameters` read the records the caller is allowed to see. A batch read returns found and missing names separately. `GetParametersByPath` picks current records by path, follows the recursion setting, and returns pages in name order. It does not fetch each matching value from Azure App Configuration, so a deep path does not cost one storage-service read per parameter.

DescribeParameters returns paginated metadata, including names, types, versions and descriptions, without parameter values. Tag operations update a parameter's metadata.

#### Versions and labels

This mapping retains numeric parameter versions; named SSM version labels are unsupported. App Configuration labels can hold earlier versions of the copy, but they are not SSM labels. The adapter owns the AWS version counter and selection, so the highest App Configuration label never decides what a read returns.

#### Storage and encryption

Azure App Configuration holds a copy of the value in the customer's store, accessed with the deployment's managed identity. Its key prefixes and labels organize that copy. GetParametersByPath searches the adapter's records; it does not run a prefix query against App Configuration.

String and StringList are supported. SecureString is not supported on this App Configuration mapping, and encrypting the store does not add it. Using Azure Key Vault directly is a separate option that needs application changes. Protect the adapter's state and the encrypted App Configuration store.

#### Limitations

Where this differs from Parameter Store

* **Custom KMS keys, parameter policies and the Advanced tier are not supported.** A per-parameter KMS key, parameter policies and Advanced-tier parameters are rejected.
* **SecureString reads behave differently: they need decryption.** Reading AWS ciphertext with `WithDecryption=false` is not supported. Where the mapping supports SecureString, read it with `WithDecryption=true`.
* **Public, shared and change-event parameters are not supported.** AWS-published public parameters, parameters shared from another account, and parameter-change events are outside this mapping.
* **Full `ParameterFilters` behavior is not supported.** `DescribeParameters` lists metadata, but complete `ParameterFilters` behavior is outside the documented scope.
* **Systems Manager features beyond Parameter Store are not supported.** Run Command, Session Manager, patching, State Manager and documents are outside this mapping.

#### Other considerations

**Before switching the application.** Load values through the Parameter Store API, and check reads, overwrites and deletion. Existing AWS values and history in Azure App Configuration are not imported automatically. Deployment can also set the stack's own literal values from the release. Parameters the stack only reads are supplied by the customer during installation, which is separate from managing parameters at runtime.

**Operating it.** Protect and back up the adapter's saved state as well as Azure App Configuration. The storage service, access permissions, the background copy and the availability of the adapter's state all affect operation.

**Performance figures.** Historical direct-proxy measurements describe their recorded request path; they do not establish Max latency, throughput, or per-read provider charges.

#### Example monthly charges

This Tensor9 Cloud Adapter scenario estimates service charges for the named origin and target services. Adapter hosting and commercial Tensor9 fees need separate allocations. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method and what the estimates include.

##### SSM Parameter Store · Standard read requests

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard read requests. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: eastus; currency: USD.

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/ac651429220058dce7420f7245e9960e2b938a23ead573e55691fc704a0bfd7f-light.svg)

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/d7f5dbcfd584bdd46335d24a044391e95e5ad95d90a79c672add4b152a5fc39f-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard read requests (operations/s) | Systems Manager (SSM) | Target scenario | Azure App Configuration | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 0 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 1 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 1 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 10 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 10 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 100 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 100 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 1,000 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 1,000 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 10,000 | 0.00 | Azure App Configuration (one staging copy) | 74,635.85 | 74,635.85 |
| 10,000 | 0.00 | Azure App Configuration (two staging copies) | 76,271.70 | 76,271.70 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 operations/s to 32 vCPU, 128 GiB memory and 100 GiB SSD at 10,000 operations/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure App Configuration (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Azure App Configuration (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Azure App Configuration (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Azure App Configuration (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Azure App Configuration (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Azure App Configuration (one staging copy) | Representative value size | 1,024 | bytes |
| Azure App Configuration (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Azure App Configuration (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Azure App Configuration (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Azure App Configuration (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Azure App Configuration (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Azure App Configuration (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Azure App Configuration (one staging copy) | Values per standard read request | 1 | parameters/request |
| Azure App Configuration (one staging copy) | Paid interactions that read values | 1 | fraction |
| Azure App Configuration (one staging copy) | Target price guess · read | 0 | USD/read |
| Azure App Configuration (one staging copy) | Target price guess · write | 0 | USD/write |
| Azure App Configuration (one staging copy) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Azure App Configuration (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure App Configuration (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure App Configuration (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure App Configuration (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure App Configuration (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure App Configuration (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure App Configuration (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure App Configuration (one staging copy) | Target list price · resource-month | 36.5 | USD/resource-month |
| Azure App Configuration (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Azure App Configuration (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Azure App Configuration (one staging copy) | Included before billing · provider operation | 6,083,340 | provider operation |
| Azure App Configuration (one staging copy) | Target monthly base charge | 0 | USD/month |
| Azure App Configuration (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Azure App Configuration (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Azure App Configuration (one staging copy) | Minimum primary RAM | 8 | GiB |
| Azure App Configuration (one staging copy) | Minimum primary disk | 100 | GiB |
| Azure App Configuration (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure App Configuration (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Azure App Configuration (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Azure App Configuration (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Azure App Configuration (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Azure App Configuration (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Azure App Configuration (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Azure App Configuration (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Azure App Configuration (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure App Configuration (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure App Configuration (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Azure App Configuration (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Azure App Configuration (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Azure App Configuration (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Azure App Configuration (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Azure App Configuration (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Azure App Configuration (two staging copies) | Representative value size | 1,024 | bytes |
| Azure App Configuration (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Azure App Configuration (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Azure App Configuration (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Azure App Configuration (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Azure App Configuration (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Azure App Configuration (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Azure App Configuration (two staging copies) | Values per standard read request | 1 | parameters/request |
| Azure App Configuration (two staging copies) | Paid interactions that read values | 1 | fraction |
| Azure App Configuration (two staging copies) | Target price guess · read | 0 | USD/read |
| Azure App Configuration (two staging copies) | Target price guess · write | 0 | USD/write |
| Azure App Configuration (two staging copies) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Azure App Configuration (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure App Configuration (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure App Configuration (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure App Configuration (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure App Configuration (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure App Configuration (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure App Configuration (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure App Configuration (two staging copies) | Target list price · resource-month | 36.5 | USD/resource-month |
| Azure App Configuration (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Azure App Configuration (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Azure App Configuration (two staging copies) | Included before billing · provider operation | 6,083,340 | provider operation |
| Azure App Configuration (two staging copies) | Target monthly base charge | 0 | USD/month |
| Azure App Configuration (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Azure App Configuration (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Azure App Configuration (two staging copies) | Minimum primary RAM | 8 | GiB |
| Azure App Configuration (two staging copies) | Minimum primary disk | 100 | GiB |
| Azure App Configuration (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Azure App Configuration (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Azure App Configuration (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Azure App Configuration (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Azure App Configuration (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Azure App Configuration (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Azure App Configuration (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Azure App Configuration (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Azure App Configuration (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure App Configuration (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure App Configuration (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Each Standard configuration store bills USD 1.20/day (36.50 for a 730-hour month) and includes 200,000 requests a day; only overage requests bill. The included 200,000 x 30.4167 days = 6,083,340 requests are one store's monthly allowance; raise it when storeCount is above one. Each store includes 1 GB of storage. Free (USD 0) and Developer (0.12/day) stores are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* Azure App Configuration pricing: [https://azure.microsoft.com/en-us/pricing/details/app-configuration/](https://azure.microsoft.com/en-us/pricing/details/app-configuration/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-bea878d9f12ef87e1c7850166ff352935ca15b1e` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Azure App Configuration pricing](https://azure.microsoft.com/en-us/pricing/details/app-configuration/).

##### SSM Parameter Store · Standard parameters

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard parameters. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: eastus; currency: USD.

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/6666651f2a1a6b287fcf29f3422505248e75f1970b90fa5cc28ce4173ca970d1-light.svg)

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/d9345829ffc6ec56c4cd9d29d95175784541983fb2f0c93efedbf31088919064-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard parameters (parameters) | Systems Manager (SSM) | Target scenario | Azure App Configuration | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Azure App Configuration (one staging copy) | 118.18 | 118.18 |
| 0 | 0.00 | Azure App Configuration (two staging copies) | 236.36 | 236.36 |
| 10 | 0.00 | Azure App Configuration (one staging copy) | 848.18 | 848.18 |
| 10 | 0.00 | Azure App Configuration (two staging copies) | 966.36 | 966.36 |
| 100 | 0.00 | Azure App Configuration (one staging copy) | 7,418.18 | 7,418.18 |
| 100 | 0.00 | Azure App Configuration (two staging copies) | 7,536.36 | 7,536.36 |
| 1,000 | 0.00 | Azure App Configuration (one staging copy) | 73,118.18 | 73,118.18 |
| 1,000 | 0.00 | Azure App Configuration (two staging copies) | 73,236.36 | 73,236.36 |
| 10,000 | 0.00 | Azure App Configuration (one staging copy) | 730,118.18 | 730,118.18 |
| 10,000 | 0.00 | Azure App Configuration (two staging copies) | 730,236.36 | 730,236.36 |
| 100,000 | 0.00 | Azure App Configuration (one staging copy) | 7,300,118.18 | 7,300,118.18 |
| 100,000 | 0.00 | Azure App Configuration (two staging copies) | 7,300,236.36 | 7,300,236.36 |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD at every sample.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Azure App Configuration (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Azure App Configuration (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Azure App Configuration (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Azure App Configuration (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Azure App Configuration (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Azure App Configuration (one staging copy) | Representative value size | 1,024 | bytes |
| Azure App Configuration (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Azure App Configuration (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Azure App Configuration (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Azure App Configuration (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Azure App Configuration (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Azure App Configuration (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Azure App Configuration (one staging copy) | Values per standard read request | 1 | parameters/request |
| Azure App Configuration (one staging copy) | Paid interactions that read values | 1 | fraction |
| Azure App Configuration (one staging copy) | Target price guess · read | 0 | USD/read |
| Azure App Configuration (one staging copy) | Target price guess · write | 0 | USD/write |
| Azure App Configuration (one staging copy) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Azure App Configuration (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure App Configuration (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure App Configuration (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure App Configuration (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure App Configuration (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure App Configuration (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure App Configuration (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure App Configuration (one staging copy) | Target list price · resource-month | 36.5 | USD/resource-month |
| Azure App Configuration (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Azure App Configuration (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Azure App Configuration (one staging copy) | Included before billing · provider operation | 6,083,340 | provider operation |
| Azure App Configuration (one staging copy) | Target monthly base charge | 0 | USD/month |
| Azure App Configuration (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Azure App Configuration (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Azure App Configuration (one staging copy) | Minimum primary RAM | 8 | GiB |
| Azure App Configuration (one staging copy) | Minimum primary disk | 100 | GiB |
| Azure App Configuration (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Azure App Configuration (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Azure App Configuration (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Azure App Configuration (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Azure App Configuration (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Azure App Configuration (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Azure App Configuration (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Azure App Configuration (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Azure App Configuration (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure App Configuration (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure App Configuration (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure App Configuration (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Azure App Configuration (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Azure App Configuration (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Azure App Configuration (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Azure App Configuration (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Azure App Configuration (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Azure App Configuration (two staging copies) | Representative value size | 1,024 | bytes |
| Azure App Configuration (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Azure App Configuration (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Azure App Configuration (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Azure App Configuration (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Azure App Configuration (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Azure App Configuration (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Azure App Configuration (two staging copies) | Values per standard read request | 1 | parameters/request |
| Azure App Configuration (two staging copies) | Paid interactions that read values | 1 | fraction |
| Azure App Configuration (two staging copies) | Target price guess · read | 0 | USD/read |
| Azure App Configuration (two staging copies) | Target price guess · write | 0 | USD/write |
| Azure App Configuration (two staging copies) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Azure App Configuration (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Azure App Configuration (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Azure App Configuration (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Azure App Configuration (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Azure App Configuration (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Azure App Configuration (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Azure App Configuration (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Azure App Configuration (two staging copies) | Target list price · resource-month | 36.5 | USD/resource-month |
| Azure App Configuration (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Azure App Configuration (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Azure App Configuration (two staging copies) | Included before billing · provider operation | 6,083,340 | provider operation |
| Azure App Configuration (two staging copies) | Target monthly base charge | 0 | USD/month |
| Azure App Configuration (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Azure App Configuration (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Azure App Configuration (two staging copies) | Minimum primary RAM | 8 | GiB |
| Azure App Configuration (two staging copies) | Minimum primary disk | 100 | GiB |
| Azure App Configuration (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Azure App Configuration (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Azure App Configuration (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Azure App Configuration (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Azure App Configuration (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Azure App Configuration (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Azure App Configuration (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Azure App Configuration (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Azure App Configuration (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Azure App Configuration (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Azure App Configuration (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Azure App Configuration (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → eastus, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Each Standard configuration store bills USD 1.20/day (36.50 for a 730-hour month) and includes 200,000 requests a day; only overage requests bill. The included 200,000 x 30.4167 days = 6,083,340 requests are one store's monthly allowance; raise it when storeCount is above one. Each store includes 1 GB of storage. Free (USD 0) and Developer (0.12/day) stores are not selected.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Azure Retail Prices API: [https://prices.azure.com/api/retail/prices](https://prices.azure.com/api/retail/prices)
* Azure App Configuration pricing: [https://azure.microsoft.com/en-us/pricing/details/app-configuration/](https://azure.microsoft.com/en-us/pricing/details/app-configuration/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-bea878d9f12ef87e1c7850166ff352935ca15b1e` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Azure App Configuration pricing](https://azure.microsoft.com/en-us/pricing/details/app-configuration/).

**SSM Parameter Store → Azure App Configuration: Authored native-usage planning example.** Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts.

Scenario source region: us-east-1. Scenario target region: eastus. Currency: USD.

| Monthly component | USD |
| - | -: |
| Origin: Standard parameter inventory | 0.00 |
| Origin: Advanced parameter inventory | 0.00 |
| Origin: Standard-throughput read API calls | 0.00 |
| Origin: Paid parameter interactions | 0.00 |
| Origin: Standard-throughput parameter mutations | 0.00 |
| Target: Target retained physical data | 0.00 |
| Target: Additional broker replica storage | 0.00 |
| Target: Target native provider operations after 6083340 included | 0.00 |
| Target: Execution or worker CPU | 0.00 |
| Target: Execution or worker RAM | 0.00 |
| Target: Selected billable network | 0.00 |
| Target: Independent native resources | 0.00 |
| Target: Independent native resources | 73,000.00 |
| Target: Durable staging CPU | 60.30 |
| Target: Durable staging RAM | 40.88 |
| Target: Durable staging disk | 17.00 |
| **Origin service subtotal** | **0.00** |
| **Target service subtotal** | **73,118.18** |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD for this scenario.

Unestimated components: Adapter hosting, Tensor9 fees. A modeled adapted total and savings require these costs.

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

**Scenario assumptions**

| Input | Value | Unit |
| - | -: | - |
| Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Representative value size | 1,024 | bytes |
| Versions retained in adapter state | 10 | versions/object |
| Provider revisions retained per logical object | 2 | versions/object |
| Physical record / payload storage | 1.5 | multiplier |
| Provider reconciliation checks | 30 | checks/object-month |
| Provider calls per current-value mutation | 2 | operations/mutation |
| Provider reconciliation retry multiplier | 1.1 | multiplier |
| Values per standard read request | 1 | parameters/request |
| Paid interactions that read values | 1 | fraction |
| Target price guess · read | 0 | USD/read |
| Target price guess · write | 0 | USD/write |
| Target list price · provider operation | 0.000006 | USD/provider operation |
| Target price guess · GiB-month | 0 | USD/GiB-month |
| Target price guess · published GiB | 0 | USD/published GiB |
| Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Target price guess · network GiB | 0 | USD/network GiB |
| Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Target price guess · resource-hour | 0 | USD/resource-hour |
| Target list price · resource-month | 36.5 | USD/resource-month |
| Target price guess · input token | 0 | USD/input token |
| Target price guess · output token | 0 | USD/output token |
| Included before billing · provider operation | 6,083,340 | provider operation |
| Target monthly base charge | 0 | USD/month |
| Approximate target service minimum | 0 | USD/month |
| Minimum primary CPU | 2 | vCPU |
| Minimum primary RAM | 8 | GiB |
| Minimum primary disk | 100 | GiB |
| Additional full-price standby copy | 0 | 0 or 1 |
| Allocated share of provisioned cost | 1 | fraction |
| Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Planning peak / mean work | 2 | multiplier |
| Planning primary CPU utilization | 0.7 | fraction |
| Resident state reserved in RAM | 0.1 | fraction |
| Planning disk utilization | 0.8 | fraction |
| Maintenance and log disk reserve | 20 | GiB |
| Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Dependent object sink write price guess | 0.000005 | USD/write |
| Standard parameter inventory | 1,000 | parameter-month |
| Advanced parameter inventory | 0 | parameter-month |
| Standard-throughput read API calls | 1,000,000 | requests |
| Paid parameter interactions | 0 | parameter-interactions |
| Standard-throughput parameter mutations | 10,000 | requests |

* Translated reads: 1,000,000 operations.

* Translated writes: 10,000 operations.

* Translated resident physical data: 0.0143 GiB-month.

* Native provider operations: 55,000 operations.

* Published payload: 0 GiB.

* Delivered payload: 0 GiB.

* Allocated execution CPU: 0 vCPU-hour.

* Allocated execution RAM: 0 GiB-hour.

* Independent resource allocation: 0 resource-hour.

* Independent inventory: 2,000 resource-month.

* Input tokens: 0 tokens.

* Output tokens: 0 tokens.

* Billable network: 0 GiB.

* Dependent object sink retained data: 0 GiB-month.

* Dependent object sink writes: 0 writes.

* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.

* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.

* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.

* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.

* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.

* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.

* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.

* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.

* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.

* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.

* Each Standard configuration store bills USD 1.20/day (36.50 for a 730-hour month) and includes 200,000 requests a day; only overage requests bill. The included 200,000 x 30.4167 days = 6,083,340 requests are one store's monthly allowance; raise it when storeCount is above one. Each store includes 1 GB of storage. Free (USD 0) and Developer (0.12/day) stores are not selected.

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.

* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.

* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.

* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.

* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.

* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).

* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.

* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.

* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

List prices read: 2026-10-22. Model: `plan-bea878d9f12ef87e1c7850166ff352935ca15b1e` / `2026-10-22.planning.2`. Scenario: `planning-example`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Azure Retail Prices API](https://prices.azure.com/api/retail/prices), [Azure App Configuration pricing](https://azure.microsoft.com/en-us/pricing/details/app-configuration/).

## On Google Cloud

### Secret Manager

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Consumed parameters (read-only references) | Build & deploy | Supported | Common | a parameter the stack reads but does not own is supplied by the customer during installation; that supply path is distinct from runtime parameter management |
| Filters & discovery (DescribeParameters / ParameterFilters) | Discovery | Partial | Full surface | DescribeParameters serves paginated metadata without values; complete ParameterFilters behavior is outside the documented contract |
| Change notifications | Events | Out of scope | Full surface | parameter-change events are outside this mapping |
| Batch reads (GetParameters) | Parameters | Supported | Common | reads caller-scoped parameter records and partitions found and missing names |
| Hierarchies & by-path reads (GetParametersByPath) | Parameters | Supported | Common | queries live adapter records by path, applies recursion rules, and returns paginated results; no provider value fetch per returned parameter |
| Parameter reads (GetParameter) | Parameters | Supported | Common | reads the current value, type, and AWS version from the caller-scoped durable parameter record; the backend copy is reconciled separately |
| Parameter writes & deletes | Parameters | Supported | Common | PutParameter creates or updates durable parameter state and reconciles the backend; DeleteParameter withdraws reads while backend cleanup proceeds separately |
| Parameter policies & Advanced tier | Policies | Out of scope | Most usage | parameter policies and the Advanced tier are outside the documented contract |
| Public & shared parameters | Scope | Out of scope | Full surface | AWS-published public parameters and cross-account shared parameters are outside this mapping |
| The wider Systems Manager suite | Scope | Out of scope | Full surface | Parameter Store only: remote commands, sessions, patching, state management, and documents remain out of scope |
| Custom encryption keys (KeyId) | Types | Out of scope | Most usage | custom per-parameter AWS KMS keys are unsupported; protect durable adapter state and configure the backend copy independently |
| Parameter types (String / StringList / SecureString) | Types | Supported | Common | all three type markers are retained in durable state; Secret Manager encrypts its provider copy at rest |
| Reading ciphertext (WithDecryption=false) | Types | Out of scope | Most usage | SecureString reads require WithDecryption=true; the adapter does not return AWS KMS ciphertext |
| Versions & labels | Versions | Supported | Most usage | retained values and adapter-owned label references provide parameter history and named labels; native aliases do not decide AWS reads |

#### Requests and durable parameter state

Your application keeps its AWS SDK Parameter Store calls; with Cloud Adapter they go to the Tensor9 adapter. The adapter saves a record of each parameter: name, type, current value, version counter, description and tags. Reads use that record. A background worker reconciles the current value to Google Secret Manager, meaning it copies the value there and keeps the copy up to date.

`PutParameter` creates a parameter, or updates it when `Overwrite=true`. Writing an existing name with `Overwrite=false` returns `ParameterAlreadyExists`. Each write increases the AWS version counter and waits a limited time for the value to reach Google Secret Manager; if Google Secret Manager rejects the value outright, the error is returned. `DeleteParameter` removes the parameter from reads at once, and backend cleanup proceeds separately.

Direct provider edits in Google Secret Manager do not update the AWS parameter record and can be overwritten by the next copy.

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Google Secret Manager.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBHb29nbGUgU2VjcmV0IE1hbmFnZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojMzM0MTU1fTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZmZmZmZmO3N0cm9rZTojY2JkNWUxIi8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwZjE3MmEiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6IzY0NzQ4YiIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZWNmZGY1O3N0cm9rZTojMDQ3ODU3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMDQ3ODU3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojNjQ3NDhiIi8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjNjQ3NDhiIj5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6I2ZmZmZmZjtzdHJva2U6I2NiZDVlMSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzBmMTcyYTsgZm9udC1zaXplOjExcHgiPkdvb2dsZSBTZWNyZXQgTWFuYWdlcjwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Google Secret Manager.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBHb29nbGUgU2VjcmV0IE1hbmFnZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojY2JkNWUxfTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMWUyOTNiO3N0cm9rZTojNDc1NTY5Ii8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICNmMWY1ZjkiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6Izk0YTNiOCIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMDY0ZTNiO3N0cm9rZTojNmVlN2I3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNmVlN2I3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojOTRhM2I4Ii8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjOTRhM2I4Ij5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6IzFlMjkzYjtzdHJva2U6IzQ3NTU2OSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogI2YxZjVmOTsgZm9udC1zaXplOjExcHgiPkdvb2dsZSBTZWNyZXQgTWFuYWdlcjwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

Reads come from the adapter's records; the storage service holds a copy kept up to date in the background.

#### Batch reads, paths, and metadata

`GetParameter` and `GetParameters` read the records the caller is allowed to see. A batch read returns found and missing names separately. `GetParametersByPath` picks current records by path, follows the recursion setting, and returns pages in name order. It does not fetch each matching value from Google Secret Manager, so a deep path does not cost one storage-service read per parameter.

DescribeParameters returns paginated metadata, including names, types, versions and descriptions, without parameter values. Tag operations update a parameter's metadata.

#### Versions and labels

This mapping retains parameter history and named SSM labels. The adapter keeps the earlier values and the label-to-version references that GetParameterHistory, LabelParameterVersion, and version-qualified reads need. Moving a Secret Manager alias directly does not move an SSM label.

#### Storage and encryption

Google Secret Manager holds a copy of the current value in the customer's project, accessed with Google workload identity. Its own versions and aliases describe that copy only; AWS reads and version selection are handled by the adapter.

All three parameter types are supported. Secret Manager encrypts its copy at rest. Protect the adapter's saved parameter state and its backups as well as the Secret Manager copy. Storing an ordinary String as a secret does not make its contents any less sensitive.

#### Limitations

Where this differs from Parameter Store

* **Custom KMS keys, parameter policies and the Advanced tier are not supported.** A per-parameter KMS key, parameter policies and Advanced-tier parameters are rejected.
* **SecureString reads behave differently: they need decryption.** Reading AWS ciphertext with `WithDecryption=false` is not supported. Where the mapping supports SecureString, read it with `WithDecryption=true`.
* **Public, shared and change-event parameters are not supported.** AWS-published public parameters, parameters shared from another account, and parameter-change events are outside this mapping.
* **Full `ParameterFilters` behavior is not supported.** `DescribeParameters` lists metadata, but complete `ParameterFilters` behavior is outside the documented scope.
* **Systems Manager features beyond Parameter Store are not supported.** Run Command, Session Manager, patching, State Manager and documents are outside this mapping.

#### Other considerations

**Before switching the application.** Load values through the Parameter Store API, and check reads, overwrites and deletion. Existing AWS values and history in Google Secret Manager are not imported automatically. Deployment can also set the stack's own literal values from the release. Parameters the stack only reads are supplied by the customer during installation, which is separate from managing parameters at runtime.

**Operating it.** Protect and back up the adapter's saved state as well as Google Secret Manager. The storage service, access permissions, the background copy and the availability of the adapter's state all affect operation.

**Performance figures.** Historical direct-proxy measurements describe their recorded request path; they do not establish Max latency, throughput, or per-read provider charges.

#### Example monthly charges

This Tensor9 Cloud Adapter scenario estimates service charges for the named origin and target services. Adapter hosting and commercial Tensor9 fees need separate allocations. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method and what the estimates include.

##### SSM Parameter Store · Standard read requests

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard read requests. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/c68a82040d16dc2ef4dd7d234dae58dab9097d5b54d5beb35039c76557e4dcd9-light.svg)

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/503a838554a486dca0dfe2a2ac0bf6a16056f1fad6f0594793958a2e06f8ee34-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard read requests (operations/s) | Systems Manager (SSM) | Target scenario | Secret Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 0 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 1 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 1 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 10 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 10 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 100 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 100 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 1,000 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 1,000 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 10,000 | 0.00 | Secret Manager (one staging copy) | 1,756.01 | 1,756.01 |
| 10,000 | 0.00 | Secret Manager (two staging copies) | 3,391.86 | 3,391.86 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 operations/s to 32 vCPU, 128 GiB memory and 100 GiB SSD at 10,000 operations/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Secret Manager (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Secret Manager (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Secret Manager (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Secret Manager (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Secret Manager (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Secret Manager (one staging copy) | Representative value size | 1,024 | bytes |
| Secret Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Secret Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Secret Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Secret Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Secret Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secret Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secret Manager (one staging copy) | Values per standard read request | 1 | parameters/request |
| Secret Manager (one staging copy) | Paid interactions that read values | 1 | fraction |
| Secret Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Secret Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Secret Manager (one staging copy) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Secret Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secret Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Secret Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secret Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Secret Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secret Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secret Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secret Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secret Manager (one staging copy) | Target list price · resource-month | 0.06 | USD/resource-month |
| Secret Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Secret Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Secret Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Secret Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Secret Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Secret Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Secret Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Secret Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Secret Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Secret Manager (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Secret Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Secret Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Secret Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Secret Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Secret Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Secret Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secret Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secret Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secret Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secret Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Secret Manager (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Secret Manager (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Secret Manager (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Secret Manager (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Secret Manager (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Secret Manager (two staging copies) | Representative value size | 1,024 | bytes |
| Secret Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Secret Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Secret Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Secret Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Secret Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secret Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secret Manager (two staging copies) | Values per standard read request | 1 | parameters/request |
| Secret Manager (two staging copies) | Paid interactions that read values | 1 | fraction |
| Secret Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Secret Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Secret Manager (two staging copies) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Secret Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secret Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Secret Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secret Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Secret Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secret Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secret Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secret Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secret Manager (two staging copies) | Target list price · resource-month | 0.06 | USD/resource-month |
| Secret Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Secret Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Secret Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Secret Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Secret Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Secret Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Secret Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Secret Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Secret Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Secret Manager (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Secret Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Secret Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Secret Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Secret Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Secret Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Secret Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secret Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secret Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secret Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secret Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Monthly resource quantity is retained active provider versions, independent of logical source objects; access operations are separate from local adapter reads, and management operations are free. The account-wide free tier (6 versions, 10,000 accesses a month) is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-3bea5aaf7f762bd82d5da337677696dfad4c50a5` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing).

##### SSM Parameter Store · Standard parameters

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard parameters. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/72ea071e5b5a88a8c28e3e3606ad46494d35b1d4c72dbe2ba0f79cdeaeac94c5-light.svg)

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/ff39ba14bb6b902e4128a51bcb785896ccbd47bb85dc975bdfc3989ecdaab5e2-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard parameters (parameters) | Systems Manager (SSM) | Target scenario | Secret Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Secret Manager (one staging copy) | 118.24 | 118.24 |
| 0 | 0.00 | Secret Manager (two staging copies) | 236.42 | 236.42 |
| 10 | 0.00 | Secret Manager (one staging copy) | 119.44 | 119.44 |
| 10 | 0.00 | Secret Manager (two staging copies) | 237.62 | 237.62 |
| 100 | 0.00 | Secret Manager (one staging copy) | 130.25 | 130.25 |
| 100 | 0.00 | Secret Manager (two staging copies) | 248.43 | 248.43 |
| 1,000 | 0.00 | Secret Manager (one staging copy) | 238.34 | 238.34 |
| 1,000 | 0.00 | Secret Manager (two staging copies) | 356.52 | 356.52 |
| 10,000 | 0.00 | Secret Manager (one staging copy) | 1,319.23 | 1,319.23 |
| 10,000 | 0.00 | Secret Manager (two staging copies) | 1,437.41 | 1,437.41 |
| 100,000 | 0.00 | Secret Manager (one staging copy) | 12,128.14 | 12,128.14 |
| 100,000 | 0.00 | Secret Manager (two staging copies) | 12,246.32 | 12,246.32 |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD at every sample.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Secret Manager (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Secret Manager (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Secret Manager (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Secret Manager (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Secret Manager (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Secret Manager (one staging copy) | Representative value size | 1,024 | bytes |
| Secret Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Secret Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Secret Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Secret Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Secret Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secret Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secret Manager (one staging copy) | Values per standard read request | 1 | parameters/request |
| Secret Manager (one staging copy) | Paid interactions that read values | 1 | fraction |
| Secret Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Secret Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Secret Manager (one staging copy) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Secret Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secret Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Secret Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secret Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Secret Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secret Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secret Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secret Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secret Manager (one staging copy) | Target list price · resource-month | 0.06 | USD/resource-month |
| Secret Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Secret Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Secret Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Secret Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Secret Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Secret Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Secret Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Secret Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Secret Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Secret Manager (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Secret Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Secret Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Secret Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Secret Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Secret Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Secret Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secret Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secret Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secret Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secret Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Secret Manager (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Secret Manager (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Secret Manager (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Secret Manager (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Secret Manager (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Secret Manager (two staging copies) | Representative value size | 1,024 | bytes |
| Secret Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Secret Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Secret Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Secret Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Secret Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Secret Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Secret Manager (two staging copies) | Values per standard read request | 1 | parameters/request |
| Secret Manager (two staging copies) | Paid interactions that read values | 1 | fraction |
| Secret Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Secret Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Secret Manager (two staging copies) | Target list price · provider operation | 0.000003 | USD/provider operation |
| Secret Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Secret Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Secret Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Secret Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Secret Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Secret Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Secret Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Secret Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Secret Manager (two staging copies) | Target list price · resource-month | 0.06 | USD/resource-month |
| Secret Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Secret Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Secret Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Secret Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Secret Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Secret Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Secret Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Secret Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Secret Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Secret Manager (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Secret Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Secret Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Secret Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Secret Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Secret Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Secret Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Secret Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Secret Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Secret Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Secret Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Monthly resource quantity is retained active provider versions, independent of logical source objects; access operations are separate from local adapter reads, and management operations are free. The account-wide free tier (6 versions, 10,000 accesses a month) is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Secret Manager pricing: [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-3bea5aaf7f762bd82d5da337677696dfad4c50a5` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing).

**SSM Parameter Store → Secret Manager: Authored native-usage planning example.** Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts.

Scenario source region: us-east-1. Scenario target region: us-central1. Currency: USD.

| Monthly component | USD |
| - | -: |
| Origin: Standard parameter inventory | 0.00 |
| Origin: Advanced parameter inventory | 0.00 |
| Origin: Standard-throughput read API calls | 0.00 |
| Origin: Paid parameter interactions | 0.00 |
| Origin: Standard-throughput parameter mutations | 0.00 |
| Target: Target native provider operations | 0.17 |
| Target: Execution or worker CPU | 0.00 |
| Target: Execution or worker RAM | 0.00 |
| Target: Selected billable network | 0.00 |
| Target: Independent native resources | 0.00 |
| Target: Independent native resources | 120.00 |
| Target: Durable staging CPU | 60.30 |
| Target: Durable staging RAM | 40.88 |
| Target: Durable staging disk | 17.00 |
| **Origin service subtotal** | **0.00** |
| **Target service subtotal** | **238.34** |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD for this scenario.

Unestimated components: Adapter hosting, Tensor9 fees. A modeled adapted total and savings require these costs.

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

**Scenario assumptions**

| Input | Value | Unit |
| - | -: | - |
| Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Representative value size | 1,024 | bytes |
| Versions retained in adapter state | 10 | versions/object |
| Provider revisions retained per logical object | 2 | versions/object |
| Physical record / payload storage | 1.5 | multiplier |
| Provider reconciliation checks | 30 | checks/object-month |
| Provider calls per current-value mutation | 2 | operations/mutation |
| Provider reconciliation retry multiplier | 1.1 | multiplier |
| Values per standard read request | 1 | parameters/request |
| Paid interactions that read values | 1 | fraction |
| Target price guess · read | 0 | USD/read |
| Target price guess · write | 0 | USD/write |
| Target list price · provider operation | 0.000003 | USD/provider operation |
| Target price guess · GiB-month | 0 | USD/GiB-month |
| Target price guess · published GiB | 0 | USD/published GiB |
| Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Target price guess · network GiB | 0 | USD/network GiB |
| Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Target price guess · resource-hour | 0 | USD/resource-hour |
| Target list price · resource-month | 0.06 | USD/resource-month |
| Target price guess · input token | 0 | USD/input token |
| Target price guess · output token | 0 | USD/output token |
| Target monthly base charge | 0 | USD/month |
| Approximate target service minimum | 0 | USD/month |
| Minimum primary CPU | 2 | vCPU |
| Minimum primary RAM | 8 | GiB |
| Minimum primary disk | 100 | GiB |
| Additional full-price standby copy | 0 | 0 or 1 |
| Allocated share of provisioned cost | 1 | fraction |
| Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Planning peak / mean work | 2 | multiplier |
| Planning primary CPU utilization | 0.7 | fraction |
| Resident state reserved in RAM | 0.1 | fraction |
| Planning disk utilization | 0.8 | fraction |
| Maintenance and log disk reserve | 20 | GiB |
| Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Dependent object sink write price guess | 0.000005 | USD/write |
| Standard parameter inventory | 1,000 | parameter-month |
| Advanced parameter inventory | 0 | parameter-month |
| Standard-throughput read API calls | 1,000,000 | requests |
| Paid parameter interactions | 0 | parameter-interactions |
| Standard-throughput parameter mutations | 10,000 | requests |

* Translated reads: 1,000,000 operations.

* Translated writes: 10,000 operations.

* Translated resident physical data: 0.0143 GiB-month.

* Native provider operations: 55,000 operations.

* Published payload: 0 GiB.

* Delivered payload: 0 GiB.

* Allocated execution CPU: 0 vCPU-hour.

* Allocated execution RAM: 0 GiB-hour.

* Independent resource allocation: 0 resource-hour.

* Independent inventory: 2,000 resource-month.

* Input tokens: 0 tokens.

* Output tokens: 0 tokens.

* Billable network: 0 GiB.

* Dependent object sink retained data: 0 GiB-month.

* Dependent object sink writes: 0 writes.

* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.

* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.

* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.

* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.

* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.

* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.

* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.

* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.

* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.

* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.

* Monthly resource quantity is retained active provider versions, independent of logical source objects; access operations are separate from local adapter reads, and management operations are free. The account-wide free tier (6 versions, 10,000 accesses a month) is not applied.

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.

* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.

* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.

* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.

* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.

* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).

* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.

* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.

* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

List prices read: 2026-10-22. Model: `plan-3bea5aaf7f762bd82d5da337677696dfad4c50a5` / `2026-10-22.planning.2`. Scenario: `planning-example`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing](https://cloud.google.com/secret-manager/pricing).

### Google Parameter Manager

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Consumed parameters (read-only references) | Build & deploy | Supported | Common | a parameter the stack reads but does not own is supplied by the customer during installation; that supply path is distinct from runtime parameter management |
| Filters & discovery (DescribeParameters / ParameterFilters) | Discovery | Partial | Full surface | DescribeParameters serves paginated metadata without values; complete ParameterFilters behavior is outside the documented contract |
| Change notifications | Events | Out of scope | Full surface | parameter-change events are outside this mapping |
| Batch reads (GetParameters) | Parameters | Supported | Common | reads caller-scoped parameter records and partitions found and missing names |
| Hierarchies & by-path reads (GetParametersByPath) | Parameters | Supported | Common | queries live adapter records by path, applies recursion rules, and returns paginated results; no provider value fetch per returned parameter |
| Parameter reads (GetParameter) | Parameters | Supported | Common | reads the current value, type, and AWS version from the caller-scoped durable parameter record; the backend copy is reconciled separately |
| Parameter writes & deletes | Parameters | Supported | Common | PutParameter creates or updates durable parameter state and reconciles the backend; DeleteParameter withdraws reads while backend cleanup proceeds separately |
| Parameter policies & Advanced tier | Policies | Out of scope | Most usage | parameter policies and the Advanced tier are outside the documented contract |
| Public & shared parameters | Scope | Out of scope | Full surface | AWS-published public parameters and cross-account shared parameters are outside this mapping |
| The wider Systems Manager suite | Scope | Out of scope | Full surface | Parameter Store only: remote commands, sessions, patching, state management, and documents remain out of scope |
| Custom encryption keys (KeyId) | Types | Out of scope | Most usage | custom per-parameter AWS KMS keys are unsupported; protect durable adapter state and configure the backend copy independently |
| Parameter types (String / StringList / SecureString) | Types | Supported | Common | all three type markers are retained in durable state; Parameter Manager encrypts its provider copy at rest; sensitivity follows actual values |
| Reading ciphertext (WithDecryption=false) | Types | Out of scope | Most usage | SecureString reads require WithDecryption=true; the adapter does not return AWS KMS ciphertext |
| Versions & labels | Versions | Supported | Most usage | retained values and adapter-owned label references provide parameter history and named labels; Parameter Manager has no native version aliases |

#### Requests and durable parameter state

Your application keeps its AWS SDK Parameter Store calls; with Cloud Adapter they go to the Tensor9 adapter. The adapter saves a record of each parameter: name, type, current value, version counter, description and tags. Reads use that record. A background worker reconciles the current value to Google Parameter Manager, meaning it copies the value there and keeps the copy up to date.

`PutParameter` creates a parameter, or updates it when `Overwrite=true`. Writing an existing name with `Overwrite=false` returns `ParameterAlreadyExists`. Each write increases the AWS version counter and waits a limited time for the value to reach Google Parameter Manager; if Google Parameter Manager rejects the value outright, the error is returned. `DeleteParameter` removes the parameter from reads at once, and backend cleanup proceeds separately.

Direct provider edits in Google Parameter Manager do not update the AWS parameter record and can be overwritten by the next copy.

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Google Parameter Manager.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBHb29nbGUgUGFyYW1ldGVyIE1hbmFnZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojMzM0MTU1fTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZmZmZmZmO3N0cm9rZTojY2JkNWUxIi8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwZjE3MmEiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6IzY0NzQ4YiIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZWNmZGY1O3N0cm9rZTojMDQ3ODU3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMDQ3ODU3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojNjQ3NDhiIi8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjNjQ3NDhiIj5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6I2ZmZmZmZjtzdHJva2U6I2NiZDVlMSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzBmMTcyYTsgZm9udC1zaXplOjExcHgiPkdvb2dsZSBQYXJhbWV0ZXIgTWFuYWdlcjwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to Google Parameter Manager.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBHb29nbGUgUGFyYW1ldGVyIE1hbmFnZXIuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojY2JkNWUxfTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMWUyOTNiO3N0cm9rZTojNDc1NTY5Ii8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICNmMWY1ZjkiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6Izk0YTNiOCIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMDY0ZTNiO3N0cm9rZTojNmVlN2I3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNmVlN2I3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojOTRhM2I4Ii8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjOTRhM2I4Ij5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6IzFlMjkzYjtzdHJva2U6IzQ3NTU2OSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogI2YxZjVmOTsgZm9udC1zaXplOjExcHgiPkdvb2dsZSBQYXJhbWV0ZXIgTWFuYWdlcjwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

Reads come from the adapter's records; the storage service holds a copy kept up to date in the background.

#### Batch reads, paths, and metadata

`GetParameter` and `GetParameters` read the records the caller is allowed to see. A batch read returns found and missing names separately. `GetParametersByPath` picks current records by path, follows the recursion setting, and returns pages in name order. It does not fetch each matching value from Google Parameter Manager, so a deep path does not cost one storage-service read per parameter.

DescribeParameters returns paginated metadata, including names, types, versions and descriptions, without parameter values. Tag operations update a parameter's metadata.

#### Versions and labels

This mapping retains parameter history and named SSM labels. The adapter keeps earlier values and label-to-version references for GetParameterHistory, LabelParameterVersion, and version-qualified reads. Parameter Manager has no version aliases of its own, and reads never just pick its highest version.

#### Storage and encryption

Google Parameter Manager holds a copy of the parameter value in the customer's project, accessed with Google workload identity. Parameter Manager resources and their versions are only that copy; the adapter keeps the AWS parameter name, current version and read behavior.

All three parameter types are supported. Parameter Manager encrypts its copy at rest. Protect the adapter's saved state and its backups too. Parameter Manager resources can hold sensitive values, so choose access controls by what they contain, not by the service's name.

#### Limitations

Where this differs from Parameter Store

* **Custom KMS keys, parameter policies and the Advanced tier are not supported.** A per-parameter KMS key, parameter policies and Advanced-tier parameters are rejected.
* **SecureString reads behave differently: they need decryption.** Reading AWS ciphertext with `WithDecryption=false` is not supported. Where the mapping supports SecureString, read it with `WithDecryption=true`.
* **Public, shared and change-event parameters are not supported.** AWS-published public parameters, parameters shared from another account, and parameter-change events are outside this mapping.
* **Full `ParameterFilters` behavior is not supported.** `DescribeParameters` lists metadata, but complete `ParameterFilters` behavior is outside the documented scope.
* **Systems Manager features beyond Parameter Store are not supported.** Run Command, Session Manager, patching, State Manager and documents are outside this mapping.

#### Other considerations

**Before switching the application.** Load values through the Parameter Store API, and check reads, overwrites and deletion. Existing AWS values and history in Google Parameter Manager are not imported automatically. Deployment can also set the stack's own literal values from the release. Parameters the stack only reads are supplied by the customer during installation, which is separate from managing parameters at runtime.

**Operating it.** Protect and back up the adapter's saved state as well as Google Parameter Manager. The storage service, access permissions, the background copy and the availability of the adapter's state all affect operation.

**Performance figures.** Historical direct-proxy measurements describe their recorded request path; they do not establish Max latency, throughput, or per-read provider charges.

#### Example monthly charges

This Tensor9 Cloud Adapter scenario estimates service charges for the named origin and target services. Adapter hosting and commercial Tensor9 fees need separate allocations. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method and what the estimates include.

##### SSM Parameter Store · Standard read requests

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard read requests. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/4fb96d290d23f5814d8a097a4a3fb0c9304d9569eab261b2de0d9eb394ff4270-light.svg)

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/cb078f3b7554bc08ef8fa1e18f26921e5f1fff1d38a2b07fa508f12d2f39be98-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard read requests (operations/s) | Systems Manager (SSM) | Target scenario | Parameter Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 0 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 1 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 1 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 10 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 10 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 100 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 100 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 1,000 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 1,000 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 10,000 | 0.00 | Parameter Manager (one staging copy) | 1,836.18 | 1,836.18 |
| 10,000 | 0.00 | Parameter Manager (two staging copies) | 3,472.03 | 3,472.03 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 operations/s to 32 vCPU, 128 GiB memory and 100 GiB SSD at 10,000 operations/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Parameter Manager (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Parameter Manager (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Parameter Manager (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Parameter Manager (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Parameter Manager (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Parameter Manager (one staging copy) | Representative value size | 1,024 | bytes |
| Parameter Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Parameter Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Parameter Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Parameter Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Parameter Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Parameter Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Parameter Manager (one staging copy) | Values per standard read request | 1 | parameters/request |
| Parameter Manager (one staging copy) | Paid interactions that read values | 1 | fraction |
| Parameter Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Parameter Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Parameter Manager (one staging copy) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Parameter Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Parameter Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Parameter Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Parameter Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Parameter Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Parameter Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Parameter Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Parameter Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Parameter Manager (one staging copy) | Target list price · resource-month | 0.1 | USD/resource-month |
| Parameter Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Parameter Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Parameter Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Parameter Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Parameter Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Parameter Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Parameter Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Parameter Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Parameter Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Parameter Manager (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Parameter Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Parameter Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Parameter Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Parameter Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Parameter Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Parameter Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Parameter Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Parameter Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Parameter Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Parameter Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Parameter Manager (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Parameter Manager (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Parameter Manager (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Parameter Manager (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Parameter Manager (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Parameter Manager (two staging copies) | Representative value size | 1,024 | bytes |
| Parameter Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Parameter Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Parameter Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Parameter Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Parameter Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Parameter Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Parameter Manager (two staging copies) | Values per standard read request | 1 | parameters/request |
| Parameter Manager (two staging copies) | Paid interactions that read values | 1 | fraction |
| Parameter Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Parameter Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Parameter Manager (two staging copies) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Parameter Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Parameter Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Parameter Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Parameter Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Parameter Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Parameter Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Parameter Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Parameter Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Parameter Manager (two staging copies) | Target list price · resource-month | 0.1 | USD/resource-month |
| Parameter Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Parameter Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Parameter Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Parameter Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Parameter Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Parameter Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Parameter Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Parameter Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Parameter Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Parameter Manager (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Parameter Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Parameter Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Parameter Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Parameter Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Parameter Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Parameter Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Parameter Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Parameter Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Parameter Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Parameter Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Monthly resource quantity is retained parameter versions; get and render calls are access operations and management operations are free. The account-wide free tier (6 versions, 10,000 operations a month) is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Secret Manager pricing (Parameter Manager section): [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-a17979490370f05e38868d643e884b5a5628ef05` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing (Parameter Manager section)](https://cloud.google.com/secret-manager/pricing).

##### SSM Parameter Store · Standard parameters

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard parameters. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-central1; currency: USD.

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/134d466400de7a668aac135a85fc56e0ff665eafa5ccb89c3809f25fb44abd09-light.svg)

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/574f2b4d72558853e969b541184348677b61d5531295536f455e0abf51018a26-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard parameters (parameters) | Systems Manager (SSM) | Target scenario | Parameter Manager | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | Parameter Manager (one staging copy) | 118.31 | 118.31 |
| 0 | 0.00 | Parameter Manager (two staging copies) | 236.49 | 236.49 |
| 10 | 0.00 | Parameter Manager (one staging copy) | 120.31 | 120.31 |
| 10 | 0.00 | Parameter Manager (two staging copies) | 238.49 | 238.49 |
| 100 | 0.00 | Parameter Manager (one staging copy) | 138.33 | 138.33 |
| 100 | 0.00 | Parameter Manager (two staging copies) | 256.51 | 256.51 |
| 1,000 | 0.00 | Parameter Manager (one staging copy) | 318.51 | 318.51 |
| 1,000 | 0.00 | Parameter Manager (two staging copies) | 436.69 | 436.69 |
| 10,000 | 0.00 | Parameter Manager (one staging copy) | 2,120.29 | 2,120.29 |
| 10,000 | 0.00 | Parameter Manager (two staging copies) | 2,238.47 | 2,238.47 |
| 100,000 | 0.00 | Parameter Manager (one staging copy) | 20,138.11 | 20,138.11 |
| 100,000 | 0.00 | Parameter Manager (two staging copies) | 20,256.29 | 20,256.29 |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD at every sample.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| Parameter Manager (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Parameter Manager (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Parameter Manager (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Parameter Manager (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Parameter Manager (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Parameter Manager (one staging copy) | Representative value size | 1,024 | bytes |
| Parameter Manager (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| Parameter Manager (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| Parameter Manager (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| Parameter Manager (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| Parameter Manager (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| Parameter Manager (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Parameter Manager (one staging copy) | Values per standard read request | 1 | parameters/request |
| Parameter Manager (one staging copy) | Paid interactions that read values | 1 | fraction |
| Parameter Manager (one staging copy) | Target price guess · read | 0 | USD/read |
| Parameter Manager (one staging copy) | Target price guess · write | 0 | USD/write |
| Parameter Manager (one staging copy) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Parameter Manager (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Parameter Manager (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| Parameter Manager (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Parameter Manager (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| Parameter Manager (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Parameter Manager (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Parameter Manager (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Parameter Manager (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Parameter Manager (one staging copy) | Target list price · resource-month | 0.1 | USD/resource-month |
| Parameter Manager (one staging copy) | Target price guess · input token | 0 | USD/input token |
| Parameter Manager (one staging copy) | Target price guess · output token | 0 | USD/output token |
| Parameter Manager (one staging copy) | Target monthly base charge | 0 | USD/month |
| Parameter Manager (one staging copy) | Approximate target service minimum | 0 | USD/month |
| Parameter Manager (one staging copy) | Minimum primary CPU | 2 | vCPU |
| Parameter Manager (one staging copy) | Minimum primary RAM | 8 | GiB |
| Parameter Manager (one staging copy) | Minimum primary disk | 100 | GiB |
| Parameter Manager (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| Parameter Manager (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| Parameter Manager (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Parameter Manager (one staging copy) | Planning peak / mean work | 2 | multiplier |
| Parameter Manager (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| Parameter Manager (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| Parameter Manager (one staging copy) | Planning disk utilization | 0.8 | fraction |
| Parameter Manager (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| Parameter Manager (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Parameter Manager (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Parameter Manager (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Parameter Manager (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Parameter Manager (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| Parameter Manager (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Parameter Manager (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Parameter Manager (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Parameter Manager (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Parameter Manager (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Parameter Manager (two staging copies) | Representative value size | 1,024 | bytes |
| Parameter Manager (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| Parameter Manager (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| Parameter Manager (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| Parameter Manager (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| Parameter Manager (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| Parameter Manager (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| Parameter Manager (two staging copies) | Values per standard read request | 1 | parameters/request |
| Parameter Manager (two staging copies) | Paid interactions that read values | 1 | fraction |
| Parameter Manager (two staging copies) | Target price guess · read | 0 | USD/read |
| Parameter Manager (two staging copies) | Target price guess · write | 0 | USD/write |
| Parameter Manager (two staging copies) | Target list price · provider operation | 0.000006 | USD/provider operation |
| Parameter Manager (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| Parameter Manager (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| Parameter Manager (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Parameter Manager (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| Parameter Manager (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Parameter Manager (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Parameter Manager (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Parameter Manager (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| Parameter Manager (two staging copies) | Target list price · resource-month | 0.1 | USD/resource-month |
| Parameter Manager (two staging copies) | Target price guess · input token | 0 | USD/input token |
| Parameter Manager (two staging copies) | Target price guess · output token | 0 | USD/output token |
| Parameter Manager (two staging copies) | Target monthly base charge | 0 | USD/month |
| Parameter Manager (two staging copies) | Approximate target service minimum | 0 | USD/month |
| Parameter Manager (two staging copies) | Minimum primary CPU | 2 | vCPU |
| Parameter Manager (two staging copies) | Minimum primary RAM | 8 | GiB |
| Parameter Manager (two staging copies) | Minimum primary disk | 100 | GiB |
| Parameter Manager (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| Parameter Manager (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| Parameter Manager (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Parameter Manager (two staging copies) | Planning peak / mean work | 2 | multiplier |
| Parameter Manager (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| Parameter Manager (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| Parameter Manager (two staging copies) | Planning disk utilization | 0.8 | fraction |
| Parameter Manager (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| Parameter Manager (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Parameter Manager (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Parameter Manager (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Parameter Manager (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Parameter Manager (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-central1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* Monthly resource quantity is retained parameter versions; get and render calls are access operations and management operations are free. The account-wide free tier (6 versions, 10,000 operations a month) is not applied.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* Secret Manager pricing (Parameter Manager section): [https://cloud.google.com/secret-manager/pricing](https://cloud.google.com/secret-manager/pricing)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-a17979490370f05e38868d643e884b5a5628ef05` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing (Parameter Manager section)](https://cloud.google.com/secret-manager/pricing).

**SSM Parameter Store → Google Parameter Manager: Authored native-usage planning example.** Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts.

Scenario source region: us-east-1. Scenario target region: us-central1. Currency: USD.

| Monthly component | USD |
| - | -: |
| Origin: Standard parameter inventory | 0.00 |
| Origin: Advanced parameter inventory | 0.00 |
| Origin: Standard-throughput read API calls | 0.00 |
| Origin: Paid parameter interactions | 0.00 |
| Origin: Standard-throughput parameter mutations | 0.00 |
| Target: Target native provider operations | 0.33 |
| Target: Execution or worker CPU | 0.00 |
| Target: Execution or worker RAM | 0.00 |
| Target: Selected billable network | 0.00 |
| Target: Independent native resources | 0.00 |
| Target: Independent native resources | 200.00 |
| Target: Durable staging CPU | 60.30 |
| Target: Durable staging RAM | 40.88 |
| Target: Durable staging disk | 17.00 |
| **Origin service subtotal** | **0.00** |
| **Target service subtotal** | **318.51** |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD for this scenario.

Unestimated components: Adapter hosting, Tensor9 fees. A modeled adapted total and savings require these costs.

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

**Scenario assumptions**

| Input | Value | Unit |
| - | -: | - |
| Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Representative value size | 1,024 | bytes |
| Versions retained in adapter state | 10 | versions/object |
| Provider revisions retained per logical object | 2 | versions/object |
| Physical record / payload storage | 1.5 | multiplier |
| Provider reconciliation checks | 30 | checks/object-month |
| Provider calls per current-value mutation | 2 | operations/mutation |
| Provider reconciliation retry multiplier | 1.1 | multiplier |
| Values per standard read request | 1 | parameters/request |
| Paid interactions that read values | 1 | fraction |
| Target price guess · read | 0 | USD/read |
| Target price guess · write | 0 | USD/write |
| Target list price · provider operation | 0.000006 | USD/provider operation |
| Target price guess · GiB-month | 0 | USD/GiB-month |
| Target price guess · published GiB | 0 | USD/published GiB |
| Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Target price guess · network GiB | 0 | USD/network GiB |
| Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Target price guess · resource-hour | 0 | USD/resource-hour |
| Target list price · resource-month | 0.1 | USD/resource-month |
| Target price guess · input token | 0 | USD/input token |
| Target price guess · output token | 0 | USD/output token |
| Target monthly base charge | 0 | USD/month |
| Approximate target service minimum | 0 | USD/month |
| Minimum primary CPU | 2 | vCPU |
| Minimum primary RAM | 8 | GiB |
| Minimum primary disk | 100 | GiB |
| Additional full-price standby copy | 0 | 0 or 1 |
| Allocated share of provisioned cost | 1 | fraction |
| Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Planning peak / mean work | 2 | multiplier |
| Planning primary CPU utilization | 0.7 | fraction |
| Resident state reserved in RAM | 0.1 | fraction |
| Planning disk utilization | 0.8 | fraction |
| Maintenance and log disk reserve | 20 | GiB |
| Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Dependent object sink write price guess | 0.000005 | USD/write |
| Standard parameter inventory | 1,000 | parameter-month |
| Advanced parameter inventory | 0 | parameter-month |
| Standard-throughput read API calls | 1,000,000 | requests |
| Paid parameter interactions | 0 | parameter-interactions |
| Standard-throughput parameter mutations | 10,000 | requests |

* Translated reads: 1,000,000 operations.

* Translated writes: 10,000 operations.

* Translated resident physical data: 0.0143 GiB-month.

* Native provider operations: 55,000 operations.

* Published payload: 0 GiB.

* Delivered payload: 0 GiB.

* Allocated execution CPU: 0 vCPU-hour.

* Allocated execution RAM: 0 GiB-hour.

* Independent resource allocation: 0 resource-hour.

* Independent inventory: 2,000 resource-month.

* Input tokens: 0 tokens.

* Output tokens: 0 tokens.

* Billable network: 0 GiB.

* Dependent object sink retained data: 0 GiB-month.

* Dependent object sink writes: 0 writes.

* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.

* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.

* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.

* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.

* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.

* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.

* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.

* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.

* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.

* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.

* Monthly resource quantity is retained parameter versions; get and render calls are access operations and management operations are free. The account-wide free tier (6 versions, 10,000 operations a month) is not applied.

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.

* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.

* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.

* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.

* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.

* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).

* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.

* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.

* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

List prices read: 2026-10-22. Model: `plan-a17979490370f05e38868d643e884b5a5628ef05` / `2026-10-22.planning.2`. Scenario: `planning-example`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [Secret Manager pricing (Parameter Manager section)](https://cloud.google.com/secret-manager/pricing).

## On OCI

### OCI Vault

| Operation | Area | Support | Depth | Notes |
| - | - | - | - | - |
| Consumed parameters (read-only references) | Build & deploy | Supported | Common | a parameter the stack reads but does not own is supplied by the customer during installation; that supply path is distinct from runtime parameter management |
| Filters & discovery (DescribeParameters / ParameterFilters) | Discovery | Partial | Full surface | DescribeParameters serves paginated metadata without values; complete ParameterFilters behavior is outside the documented contract |
| Change notifications | Events | Out of scope | Full surface | parameter-change events are outside this mapping |
| Batch reads (GetParameters) | Parameters | Supported | Common | reads caller-scoped parameter records and partitions found and missing names |
| Hierarchies & by-path reads (GetParametersByPath) | Parameters | Supported | Common | queries live adapter records by path, applies recursion rules, and returns paginated results; no provider value fetch per returned parameter |
| Parameter reads (GetParameter) | Parameters | Supported | Common | reads the current value, type, and AWS version from the caller-scoped durable parameter record; the backend copy is reconciled separately |
| Parameter writes & deletes | Parameters | Supported | Common | PutParameter creates or updates durable parameter state and reconciles the backend; DeleteParameter withdraws reads while backend cleanup proceeds separately |
| Parameter policies & Advanced tier | Policies | Out of scope | Most usage | parameter policies and the Advanced tier are outside the documented contract |
| Public & shared parameters | Scope | Out of scope | Full surface | AWS-published public parameters and cross-account shared parameters are outside this mapping |
| The wider Systems Manager suite | Scope | Out of scope | Full surface | Parameter Store only: remote commands, sessions, patching, state management, and documents remain out of scope |
| Custom encryption keys (KeyId) | Types | Out of scope | Most usage | custom per-parameter AWS KMS keys are unsupported; protect durable adapter state and configure the backend copy independently |
| Parameter types (String / StringList / SecureString) | Types | Supported | Common | all three type markers are retained in durable state; the configured OCI vault key encrypts the provider copy |
| Reading ciphertext (WithDecryption=false) | Types | Out of scope | Most usage | SecureString reads require WithDecryption=true; the adapter does not return AWS KMS ciphertext |
| Move-only version labels | Versions | Out of scope | Most usage | named SSM labels are outside this mapping; native OCI stages do not define the AWS contract |
| Versions | Versions | Supported | Most usage | numeric history is retained; the adapter owns AWS version identity and selection independently of native OCI versionNumber values |

#### Requests and durable parameter state

Your application keeps its AWS SDK Parameter Store calls; with Cloud Adapter they go to the Tensor9 adapter. The adapter saves a record of each parameter: name, type, current value, version counter, description and tags. Reads use that record. A background worker reconciles the current value to OCI Vault, meaning it copies the value there and keeps the copy up to date.

`PutParameter` creates a parameter, or updates it when `Overwrite=true`. Writing an existing name with `Overwrite=false` returns `ParameterAlreadyExists`. Each write increases the AWS version counter and waits a limited time for the value to reach OCI Vault; if OCI Vault rejects the value outright, the error is returned. `DeleteParameter` removes the parameter from reads at once, and backend cleanup proceeds separately.

Direct provider edits in OCI Vault do not update the AWS parameter record and can be overwritten by the next copy.

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to OCI Vault.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBPQ0kgVmF1bHQuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojMzM0MTU1fTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZmZmZmZmO3N0cm9rZTojY2JkNWUxIi8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwZjE3MmEiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6IzY0NzQ4YiIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojZWNmZGY1O3N0cm9rZTojMDQ3ODU3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjMDQ3ODU3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICMwNDc4NTciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojNjQ3NDhiIi8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjNjQ3NDhiIj5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6I2ZmZmZmZjtzdHJva2U6I2NiZDVlMSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogIzBmMTcyYTsgZm9udC1zaXplOjExcHgiPk9DSSBWYXVsdDwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNjQ3NDhiIj5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

![Your application's Parameter Store requests read and write the adapter's saved parameter records. A background worker reconciles the current value to OCI Vault.](data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI4MzYiIGhlaWdodD0iMjEwIiB2aWV3Qm94PSIwIDAgODM2IDIxMCIgcm9sZT0iaW1nIiBhcmlhLWxhYmVsPSJZb3VyIGFwcGxpY2F0aW9uJ3MgUGFyYW1ldGVyIFN0b3JlIHJlcXVlc3RzIHJlYWQgYW5kIHdyaXRlIHRoZSBhZGFwdGVyJ3Mgc2F2ZWQgcGFyYW1ldGVyIHJlY29yZHMuIEEgYmFja2dyb3VuZCB3b3JrZXIgcmVjb25jaWxlcyB0aGUgY3VycmVudCB2YWx1ZSB0byBPQ0kgVmF1bHQuIj48c3R5bGU+dGV4dHtmb250LWZhbWlseTpJbnRlciwtYXBwbGUtc3lzdGVtLEJsaW5rTWFjU3lzdGVtRm9udCwnU2Vnb2UgVUknLFJvYm90bywnSGVsdmV0aWNhIE5ldWUnLEFyaWFsLHNhbnMtc2VyaWY7ZmlsbDojY2JkNWUxfTwvc3R5bGU+CjxyZWN0IHg9IjE0IiB5PSI2NSIgd2lkdGg9IjE1NSIgaGVpZ2h0PSI3OCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMWUyOTNiO3N0cm9rZTojNDc1NTY5Ii8+Cjx0ZXh0IHg9IjkxIiB5PSI5NSIgdGV4dC1hbmNob3I9Im1pZGRsZSIgc3R5bGU9ImZvbnQ6IDY1MCAxMy41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICNmMWY1ZjkiPllvdXIgYXBwbGljYXRpb248L3RleHQ+Cjx0ZXh0IHg9IjkxIiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5QYXJhbWV0ZXIgU3RvcmUgU0RLPC90ZXh0Pgo8cGF0aCBkPSJNMTY5LDEwNCBIMjQ0IGwtOSwtNSBtOSw1IGwtOSw1IiBmaWxsPSJub25lIiBzdHJva2Utd2lkdGg9IjIiIHN0eWxlPSJzdHJva2U6Izk0YTNiOCIvPgo8cmVjdCB4PSIyNTAiIHk9IjM4IiB3aWR0aD0iMjgyIiBoZWlnaHQ9IjEzMCIgcng9IjEyIiBzdHlsZT0iZmlsbDojMDY0ZTNiO3N0cm9rZTojNmVlN2I3Ii8+Cjx0ZXh0IHg9IjM5MSIgeT0iNjkiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiA3MDAgMTMuNXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjNmVlN2I3Ij5EdXJhYmxlIHBhcmFtZXRlciByZWNvcmQ8L3RleHQ+Cjx0ZXh0IHg9IjM5MSIgeT0iOTQiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5OYW1lLCB0eXBlLCB2YWx1ZSwgdmVyc2lvbjwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxMTUiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5EZXNjcmlwdGlvbiBhbmQgdGFnczwvdGV4dD4KPHRleHQgeD0iMzkxIiB5PSIxNDEiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMC41cHggSW50ZXIsIHNhbnMtc2VyaWY7IGZpbGw6ICM2ZWU3YjciPlJlYWRzIGFuZCB3cml0ZXMgdXNlIHRoaXM8L3RleHQ+CjxwYXRoIGQ9Ik01MzIsMTA0IEg2MDMgbC05LC01IG05LDUgbC05LDUiIGZpbGw9Im5vbmUiIHN0cm9rZS13aWR0aD0iMiIgc3R5bGU9InN0cm9rZTojOTRhM2I4Ii8+Cjx0ZXh0IHg9IjU2NyIgeT0iODYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMHB4ICdTRiBNb25vJywgdWktbW9ub3NwYWNlLCAnSmV0QnJhaW5zIE1vbm8nLCBNZW5sbywgbW9ub3NwYWNlOyBmaWxsOiAjOTRhM2I4Ij5yZWNvbmNpbGU8L3RleHQ+CjxyZWN0IHg9IjYwOSIgeT0iNjUiIHdpZHRoPSIyMTMiIGhlaWdodD0iNzgiIHJ4PSIxMiIgc3R5bGU9ImZpbGw6IzFlMjkzYjtzdHJva2U6IzQ3NTU2OSIvPgo8dGV4dCB4PSI3MTUiIHk9Ijk1IiB0ZXh0LWFuY2hvcj0ibWlkZGxlIiBzdHlsZT0iZm9udDogNjUwIDEzLjVweCBJbnRlciwgc2Fucy1zZXJpZjsgZmlsbDogI2YxZjVmOTsgZm9udC1zaXplOjExcHgiPk9DSSBWYXVsdDwvdGV4dD4KPHRleHQgeD0iNzE1IiB5PSIxMTYiIHRleHQtYW5jaG9yPSJtaWRkbGUiIHN0eWxlPSJmb250OiAxMXB4IEludGVyLCBzYW5zLXNlcmlmOyBmaWxsOiAjOTRhM2I4Ij5Ib2xkcyBhIGNvcHk8L3RleHQ+Cjwvc3ZnPg==)

Reads come from the adapter's records; the storage service holds a copy kept up to date in the background.

#### Batch reads, paths, and metadata

`GetParameter` and `GetParameters` read the records the caller is allowed to see. A batch read returns found and missing names separately. `GetParametersByPath` picks current records by path, follows the recursion setting, and returns pages in name order. It does not fetch each matching value from OCI Vault, so a deep path does not cost one storage-service read per parameter.

DescribeParameters returns paginated metadata, including names, types, versions and descriptions, without parameter values. Tag operations update a parameter's metadata.

#### Versions and labels

This mapping retains numeric parameter versions; named SSM labels are not supported. OCI stores versions of the copy, while the adapter maintains AWS version identity and selection. A vault versionNumber never bypasses the parameter record.

#### Storage and encryption

OCI Vault holds a copy of each value as a secret, including ordinary String configuration. You configure the vault, compartment, encryption key, and resource-principal access to manage and read secrets. The vault's own secret versions describe the copy; the adapter keeps the AWS parameter record and serves reads from it.

All three parameter types use the configured vault key for the copy. OCI schedules the final deletion of a secret, so that cleanup can finish after the parameter is no longer readable through AWS. When a parameter name is reused while OCI still keeps the old vault secret, the two must be reconciled without mixing the old secret's version sequence into the new AWS parameter's versions. Protect the adapter's saved state and backups as well as the vault.

#### Limitations

Where this differs from Parameter Store

* **Custom KMS keys, parameter policies and the Advanced tier are not supported.** A per-parameter KMS key, parameter policies and Advanced-tier parameters are rejected.
* **SecureString reads behave differently: they need decryption.** Reading AWS ciphertext with `WithDecryption=false` is not supported. Where the mapping supports SecureString, read it with `WithDecryption=true`.
* **Public, shared and change-event parameters are not supported.** AWS-published public parameters, parameters shared from another account, and parameter-change events are outside this mapping.
* **Full `ParameterFilters` behavior is not supported.** `DescribeParameters` lists metadata, but complete `ParameterFilters` behavior is outside the documented scope.
* **Systems Manager features beyond Parameter Store are not supported.** Run Command, Session Manager, patching, State Manager and documents are outside this mapping.

#### Other considerations

**Before switching the application.** Load values through the Parameter Store API, and check reads, overwrites and deletion. Existing AWS values and history in OCI Vault are not imported automatically. Deployment can also set the stack's own literal values from the release. Parameters the stack only reads are supplied by the customer during installation, which is separate from managing parameters at runtime.

**Operating it.** Protect and back up the adapter's saved state as well as OCI Vault. The storage service, access permissions, the background copy and the availability of the adapter's state all affect operation.

**Performance figures.** Historical direct-proxy measurements describe their recorded request path; they do not establish Max latency, throughput, or per-read provider charges.

#### Example monthly charges

This Tensor9 Cloud Adapter scenario estimates service charges for the named origin and target services. Adapter hosting and commercial Tensor9 fees need separate allocations. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method and what the estimates include.

##### SSM Parameter Store · Standard read requests

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard read requests. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1; currency: USD.

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/7927e226e0e47b177109f0d9876cf61c8cff54a1c49665ab4e4a4ed334c9f5ef-light.svg)

![SSM Parameter Store · Standard read requests: monthly service charges by Standard read requests. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/4d36e2bed8355b45d5cf388b0cbf7e1e88e2ec202add00fae000b5800a472b8d-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard read requests (operations/s) | Systems Manager (SSM) | Target scenario | OCI Vault | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 0 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 1 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 1 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 10 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 10 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 100 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 100 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 1,000 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 1,000 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 10,000 | 0.00 | OCI Vault (one staging copy) | 1,635.85 | 1,635.85 |
| 10,000 | 0.00 | OCI Vault (two staging copies) | 3,271.70 | 3,271.70 |

Estimated allocation, not benchmark calibrated: sized from 2 vCPU, 8 GiB memory and 100 GiB SSD at 0 operations/s to 32 vCPU, 128 GiB memory and 100 GiB SSD at 10,000 operations/s.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI Vault (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| OCI Vault (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| OCI Vault (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| OCI Vault (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| OCI Vault (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| OCI Vault (one staging copy) | Representative value size | 1,024 | bytes |
| OCI Vault (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| OCI Vault (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| OCI Vault (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| OCI Vault (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| OCI Vault (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| OCI Vault (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| OCI Vault (one staging copy) | Values per standard read request | 1 | parameters/request |
| OCI Vault (one staging copy) | Paid interactions that read values | 1 | fraction |
| OCI Vault (one staging copy) | Target price guess · read | 0 | USD/read |
| OCI Vault (one staging copy) | Target price guess · write | 0 | USD/write |
| OCI Vault (one staging copy) | Target list price · provider operation | 0 | USD/provider operation |
| OCI Vault (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| OCI Vault (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| OCI Vault (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI Vault (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| OCI Vault (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI Vault (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI Vault (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI Vault (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI Vault (one staging copy) | Target list price · resource-month | 0 | USD/resource-month |
| OCI Vault (one staging copy) | Target price guess · input token | 0 | USD/input token |
| OCI Vault (one staging copy) | Target price guess · output token | 0 | USD/output token |
| OCI Vault (one staging copy) | Target monthly base charge | 0 | USD/month |
| OCI Vault (one staging copy) | Approximate target service minimum | 0 | USD/month |
| OCI Vault (one staging copy) | Minimum primary CPU | 2 | vCPU |
| OCI Vault (one staging copy) | Minimum primary RAM | 8 | GiB |
| OCI Vault (one staging copy) | Minimum primary disk | 100 | GiB |
| OCI Vault (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| OCI Vault (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| OCI Vault (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| OCI Vault (one staging copy) | Planning peak / mean work | 2 | multiplier |
| OCI Vault (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| OCI Vault (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| OCI Vault (one staging copy) | Planning disk utilization | 0.8 | fraction |
| OCI Vault (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| OCI Vault (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI Vault (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI Vault (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI Vault (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI Vault (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| OCI Vault (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| OCI Vault (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| OCI Vault (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| OCI Vault (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| OCI Vault (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| OCI Vault (two staging copies) | Representative value size | 1,024 | bytes |
| OCI Vault (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| OCI Vault (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| OCI Vault (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| OCI Vault (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| OCI Vault (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| OCI Vault (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| OCI Vault (two staging copies) | Values per standard read request | 1 | parameters/request |
| OCI Vault (two staging copies) | Paid interactions that read values | 1 | fraction |
| OCI Vault (two staging copies) | Target price guess · read | 0 | USD/read |
| OCI Vault (two staging copies) | Target price guess · write | 0 | USD/write |
| OCI Vault (two staging copies) | Target list price · provider operation | 0 | USD/provider operation |
| OCI Vault (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| OCI Vault (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| OCI Vault (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI Vault (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| OCI Vault (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI Vault (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI Vault (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI Vault (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI Vault (two staging copies) | Target list price · resource-month | 0 | USD/resource-month |
| OCI Vault (two staging copies) | Target price guess · input token | 0 | USD/input token |
| OCI Vault (two staging copies) | Target price guess · output token | 0 | USD/output token |
| OCI Vault (two staging copies) | Target monthly base charge | 0 | USD/month |
| OCI Vault (two staging copies) | Approximate target service minimum | 0 | USD/month |
| OCI Vault (two staging copies) | Minimum primary CPU | 2 | vCPU |
| OCI Vault (two staging copies) | Minimum primary RAM | 8 | GiB |
| OCI Vault (two staging copies) | Minimum primary disk | 100 | GiB |
| OCI Vault (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| OCI Vault (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| OCI Vault (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| OCI Vault (two staging copies) | Planning peak / mean work | 2 | multiplier |
| OCI Vault (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| OCI Vault (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| OCI Vault (two staging copies) | Planning disk utilization | 0.8 | fraction |
| OCI Vault (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| OCI Vault (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI Vault (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI Vault (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI Vault (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI Vault (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Monthly operation quantity varies with this steady average rate; stored inventory and other meters retain their defaults. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-ashburn-1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* OCI Secret Management has no charge for secret versions or retrieval; only an HSM-protected protecting key above 20 versions or a private vault (USD 3.724/hour) would bill, and the default software-protected key is free.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* OCI Secret Management: [https://www.oracle.com/security/cloud-security/secrets/](https://www.oracle.com/security/cloud-security/secrets/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-f1d938dac22a5be9a1ea14f9d47946ed474017a3` / `2026-10-22.planning.2`. Curve: `workload-1`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [OCI Secret Management](https://www.oracle.com/security/cloud-security/secrets/).

##### SSM Parameter Store · Standard parameters

Feature: SSM Parameter Store.

Estimated monthly service charges by Standard parameters. Adapter hosting and Tensor9 fees are excluded. Source: us-east-1; target: us-ashburn-1; currency: USD.

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/1eafa9ce0edb2672290f76a2a12cc54fb4f29a5772b7b565f589aa75bd013c99-light.svg)

![SSM Parameter Store · Standard parameters: monthly service charges by Standard parameters. Exact values are in the following table.](https://docs.tensor9.com/images/cloud-adapter-early-access/diagrams/service-cost/3e9b32d2c92f67e6f84ce465fa933359a3865446370e71201073443381e729f7-dark.svg)

Comparison pills describe all sampled scale points; amounts beside each service are for the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples.

Sampled monthly charges in USD, rounded to cents. Difference means target minus origin; a positive difference means the target costs more.

| Standard parameters (parameters) | Systems Manager (SSM) | Target scenario | OCI Vault | Difference |
| -: | -: | - | -: | -: |
| 0 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 0 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 10 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 10 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 100 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 100 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 1,000 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 1,000 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 10,000 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 10,000 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |
| 100,000 | 0.00 | OCI Vault (one staging copy) | 118.18 | 118.18 |
| 100,000 | 0.00 | OCI Vault (two staging copies) | 236.36 | 236.36 |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD at every sample.

**Curve assumptions**

| Target scenario | Assumption | Value | Unit |
| - | - | -: | - |
| OCI Vault (one staging copy) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| OCI Vault (one staging copy) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| OCI Vault (one staging copy) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| OCI Vault (one staging copy) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| OCI Vault (one staging copy) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| OCI Vault (one staging copy) | Representative value size | 1,024 | bytes |
| OCI Vault (one staging copy) | Versions retained in adapter state | 10 | versions/object |
| OCI Vault (one staging copy) | Provider revisions retained per logical object | 2 | versions/object |
| OCI Vault (one staging copy) | Physical record / payload storage | 1.5 | multiplier |
| OCI Vault (one staging copy) | Provider reconciliation checks | 30 | checks/object-month |
| OCI Vault (one staging copy) | Provider calls per current-value mutation | 2 | operations/mutation |
| OCI Vault (one staging copy) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| OCI Vault (one staging copy) | Values per standard read request | 1 | parameters/request |
| OCI Vault (one staging copy) | Paid interactions that read values | 1 | fraction |
| OCI Vault (one staging copy) | Target price guess · read | 0 | USD/read |
| OCI Vault (one staging copy) | Target price guess · write | 0 | USD/write |
| OCI Vault (one staging copy) | Target list price · provider operation | 0 | USD/provider operation |
| OCI Vault (one staging copy) | Target price guess · GiB-month | 0 | USD/GiB-month |
| OCI Vault (one staging copy) | Target price guess · published GiB | 0 | USD/published GiB |
| OCI Vault (one staging copy) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI Vault (one staging copy) | Target price guess · network GiB | 0 | USD/network GiB |
| OCI Vault (one staging copy) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI Vault (one staging copy) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI Vault (one staging copy) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI Vault (one staging copy) | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI Vault (one staging copy) | Target list price · resource-month | 0 | USD/resource-month |
| OCI Vault (one staging copy) | Target price guess · input token | 0 | USD/input token |
| OCI Vault (one staging copy) | Target price guess · output token | 0 | USD/output token |
| OCI Vault (one staging copy) | Target monthly base charge | 0 | USD/month |
| OCI Vault (one staging copy) | Approximate target service minimum | 0 | USD/month |
| OCI Vault (one staging copy) | Minimum primary CPU | 2 | vCPU |
| OCI Vault (one staging copy) | Minimum primary RAM | 8 | GiB |
| OCI Vault (one staging copy) | Minimum primary disk | 100 | GiB |
| OCI Vault (one staging copy) | Additional full-price standby copy | 0 | 0 or 1 |
| OCI Vault (one staging copy) | Allocated share of provisioned cost | 1 | fraction |
| OCI Vault (one staging copy) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| OCI Vault (one staging copy) | Planning peak / mean work | 2 | multiplier |
| OCI Vault (one staging copy) | Planning primary CPU utilization | 0.7 | fraction |
| OCI Vault (one staging copy) | Resident state reserved in RAM | 0.1 | fraction |
| OCI Vault (one staging copy) | Planning disk utilization | 0.8 | fraction |
| OCI Vault (one staging copy) | Maintenance and log disk reserve | 20 | GiB |
| OCI Vault (one staging copy) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI Vault (one staging copy) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI Vault (one staging copy) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI Vault (one staging copy) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI Vault (one staging copy) | Dependent object sink write price guess | 0.000005 | USD/write |
| OCI Vault (two staging copies) | Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| OCI Vault (two staging copies) | Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| OCI Vault (two staging copies) | Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| OCI Vault (two staging copies) | Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| OCI Vault (two staging copies) | Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| OCI Vault (two staging copies) | Representative value size | 1,024 | bytes |
| OCI Vault (two staging copies) | Versions retained in adapter state | 10 | versions/object |
| OCI Vault (two staging copies) | Provider revisions retained per logical object | 2 | versions/object |
| OCI Vault (two staging copies) | Physical record / payload storage | 1.5 | multiplier |
| OCI Vault (two staging copies) | Provider reconciliation checks | 30 | checks/object-month |
| OCI Vault (two staging copies) | Provider calls per current-value mutation | 2 | operations/mutation |
| OCI Vault (two staging copies) | Provider reconciliation retry multiplier | 1.1 | multiplier |
| OCI Vault (two staging copies) | Values per standard read request | 1 | parameters/request |
| OCI Vault (two staging copies) | Paid interactions that read values | 1 | fraction |
| OCI Vault (two staging copies) | Target price guess · read | 0 | USD/read |
| OCI Vault (two staging copies) | Target price guess · write | 0 | USD/write |
| OCI Vault (two staging copies) | Target list price · provider operation | 0 | USD/provider operation |
| OCI Vault (two staging copies) | Target price guess · GiB-month | 0 | USD/GiB-month |
| OCI Vault (two staging copies) | Target price guess · published GiB | 0 | USD/published GiB |
| OCI Vault (two staging copies) | Target price guess · delivered GiB | 0 | USD/delivered GiB |
| OCI Vault (two staging copies) | Target price guess · network GiB | 0 | USD/network GiB |
| OCI Vault (two staging copies) | Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| OCI Vault (two staging copies) | Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| OCI Vault (two staging copies) | Target price guess · GiB-hour | 0 | USD/GiB-hour |
| OCI Vault (two staging copies) | Target price guess · resource-hour | 0 | USD/resource-hour |
| OCI Vault (two staging copies) | Target list price · resource-month | 0 | USD/resource-month |
| OCI Vault (two staging copies) | Target price guess · input token | 0 | USD/input token |
| OCI Vault (two staging copies) | Target price guess · output token | 0 | USD/output token |
| OCI Vault (two staging copies) | Target monthly base charge | 0 | USD/month |
| OCI Vault (two staging copies) | Approximate target service minimum | 0 | USD/month |
| OCI Vault (two staging copies) | Minimum primary CPU | 2 | vCPU |
| OCI Vault (two staging copies) | Minimum primary RAM | 8 | GiB |
| OCI Vault (two staging copies) | Minimum primary disk | 100 | GiB |
| OCI Vault (two staging copies) | Additional full-price standby copy | 1 | 0 or 1 |
| OCI Vault (two staging copies) | Allocated share of provisioned cost | 1 | fraction |
| OCI Vault (two staging copies) | Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| OCI Vault (two staging copies) | Planning peak / mean work | 2 | multiplier |
| OCI Vault (two staging copies) | Planning primary CPU utilization | 0.7 | fraction |
| OCI Vault (two staging copies) | Resident state reserved in RAM | 0.1 | fraction |
| OCI Vault (two staging copies) | Planning disk utilization | 0.8 | fraction |
| OCI Vault (two staging copies) | Maintenance and log disk reserve | 20 | GiB |
| OCI Vault (two staging copies) | Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| OCI Vault (two staging copies) | Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| OCI Vault (two staging copies) | Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| OCI Vault (two staging copies) | Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| OCI Vault (two staging copies) | Dependent object sink write price guess | 0.000005 | USD/write |

* Inventory varies independently of monthly reads and mutations. Retention remains an explicit planning assumption. Other native meters and workload assumptions retain their explicitly displayed default quantities. Workload translation and capacity assumptions are not benchmark measurements.
* Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts. Rates as of 2026-10-22: us-east-1 → us-ashburn-1, USD/month.
* Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
* Samples of explicit prices are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
* Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve's workload note.
* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.
* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.
* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.
* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.
* OCI Secret Management has no charge for secret versions or retrieval; only an HSM-protected protecting key above 20 versions or a private vault (USD 3.724/hour) would bill, and the default software-protected key is free.
* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.
* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.
* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.
* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.
* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.
* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).
* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.
* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.
* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
* AWS Systems Manager pricing: [https://aws.amazon.com/systems-manager/pricing/](https://aws.amazon.com/systems-manager/pricing/)
* AWS Price List API, AWSSystemsManager offer: [https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json)
* OCI Secret Management: [https://www.oracle.com/security/cloud-security/secrets/](https://www.oracle.com/security/cloud-security/secrets/)

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: `plan-f1d938dac22a5be9a1ea14f9d47946ed474017a3` / `2026-10-22.planning.2`. Curve: `workload-2`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [OCI Secret Management](https://www.oracle.com/security/cloud-security/secrets/).

**SSM Parameter Store → OCI Vault: Authored native-usage planning example.** Native monthly usage priced at the cited provider list prices; listed target allowances apply where present, excluding invoice credits, taxes and negotiated discounts.

Scenario source region: us-east-1. Scenario target region: us-ashburn-1. Currency: USD.

| Monthly component | USD |
| - | -: |
| Origin: Standard parameter inventory | 0.00 |
| Origin: Advanced parameter inventory | 0.00 |
| Origin: Standard-throughput read API calls | 0.00 |
| Origin: Paid parameter interactions | 0.00 |
| Origin: Standard-throughput parameter mutations | 0.00 |
| Target: Target native provider operations | 0.00 |
| Target: Execution or worker CPU | 0.00 |
| Target: Execution or worker RAM | 0.00 |
| Target: Selected billable network | 0.00 |
| Target: Independent native resources | 0.00 |
| Target: Independent native resources | 0.00 |
| Target: Durable staging CPU | 60.30 |
| Target: Durable staging RAM | 40.88 |
| Target: Durable staging disk | 17.00 |
| **Origin service subtotal** | **0.00** |
| **Target service subtotal** | **118.18** |

Estimated allocation, not benchmark calibrated: sized at 2 vCPU, 8 GiB memory and 100 GiB SSD for this scenario.

Unestimated components: Adapter hosting, Tensor9 fees. A modeled adapted total and savings require these costs.

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied.

Excluded costs and workload features:

* Free allowances, committed discounts, credits, taxes and negotiated rates.
* Commercial Tensor9 fees and operations labor unless entered separately.
* Systems Manager sessions, Run Command, patching, automation, secure-string custom-key calls and physical regional replicas.
* Taxes, discounts, credits and free-tier allowances not explicitly listed by this model.
* Unmodeled dependent services, task execution and operations outside the selected workload family.

**Scenario assumptions**

| Input | Value | Unit |
| - | -: | - |
| Origin list price · Standard parameter inventory | 0 | USD/parameter-month |
| Origin list price · Advanced parameter inventory | 0.05 | USD/parameter-month |
| Origin list price · Standard-throughput read API calls | 0 | USD/requests |
| Origin list price · Paid parameter interactions | 0.000005 | USD/parameter-interactions |
| Origin list price · Standard-throughput parameter mutations | 0 | USD/requests |
| Representative value size | 1,024 | bytes |
| Versions retained in adapter state | 10 | versions/object |
| Provider revisions retained per logical object | 2 | versions/object |
| Physical record / payload storage | 1.5 | multiplier |
| Provider reconciliation checks | 30 | checks/object-month |
| Provider calls per current-value mutation | 2 | operations/mutation |
| Provider reconciliation retry multiplier | 1.1 | multiplier |
| Values per standard read request | 1 | parameters/request |
| Paid interactions that read values | 1 | fraction |
| Target price guess · read | 0 | USD/read |
| Target price guess · write | 0 | USD/write |
| Target list price · provider operation | 0 | USD/provider operation |
| Target price guess · GiB-month | 0 | USD/GiB-month |
| Target price guess · published GiB | 0 | USD/published GiB |
| Target price guess · delivered GiB | 0 | USD/delivered GiB |
| Target price guess · network GiB | 0 | USD/network GiB |
| Target price guess · replica GiB-month | 0 | USD/replica GiB-month |
| Target price guess · vCPU-hour | 0 | USD/vCPU-hour |
| Target price guess · GiB-hour | 0 | USD/GiB-hour |
| Target price guess · resource-hour | 0 | USD/resource-hour |
| Target list price · resource-month | 0 | USD/resource-month |
| Target price guess · input token | 0 | USD/input token |
| Target price guess · output token | 0 | USD/output token |
| Target monthly base charge | 0 | USD/month |
| Approximate target service minimum | 0 | USD/month |
| Minimum primary CPU | 2 | vCPU |
| Minimum primary RAM | 8 | GiB |
| Minimum primary disk | 100 | GiB |
| Additional full-price standby copy | 0 | 0 or 1 |
| Allocated share of provisioned cost | 1 | fraction |
| Read/write work per vCPU-second | 1,500 | operations/vCPU-second |
| Planning peak / mean work | 2 | multiplier |
| Planning primary CPU utilization | 0.7 | fraction |
| Resident state reserved in RAM | 0.1 | fraction |
| Planning disk utilization | 0.8 | fraction |
| Maintenance and log disk reserve | 20 | GiB |
| Staging database CPU unit-price guess | 0.0413 | USD/vCPU-hour |
| Staging database RAM unit-price guess | 0.007 | USD/GiB-hour |
| Staging database disk unit-price guess | 0.17 | USD/GiB-month |
| Dependent object sink storage price guess | 0.023 | USD/GiB-month |
| Dependent object sink write price guess | 0.000005 | USD/write |
| Standard parameter inventory | 1,000 | parameter-month |
| Advanced parameter inventory | 0 | parameter-month |
| Standard-throughput read API calls | 1,000,000 | requests |
| Paid parameter interactions | 0 | parameter-interactions |
| Standard-throughput parameter mutations | 10,000 | requests |

* Translated reads: 1,000,000 operations.

* Translated writes: 10,000 operations.

* Translated resident physical data: 0.0143 GiB-month.

* Native provider operations: 55,000 operations.

* Published payload: 0 GiB.

* Delivered payload: 0 GiB.

* Allocated execution CPU: 0 vCPU-hour.

* Allocated execution RAM: 0 GiB-hour.

* Independent resource allocation: 0 resource-hour.

* Independent inventory: 2,000 resource-month.

* Input tokens: 0 tokens.

* Output tokens: 0 tokens.

* Billable network: 0 GiB.

* Dependent object sink retained data: 0 GiB-month.

* Dependent object sink writes: 0 writes.

* Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.

* Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.

* Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.

* Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.

* A declared adapter mapping and cost model do not establish implementation availability or service equivalence.

* This is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.

* Origin unit prices are cited provider list prices. Retention, amplification, and capacity coefficients are authored planning guesses; they are editable, not measured capacity.

* Application reads use durable adapter records. Managed operations estimate independent backend reconciliation, not a provider secret-access charge on every application read.

* Only Parameter Store is represented. A paid advanced source meter does not imply support for advanced parameter policies on the selected backend.

* Parameter history is stored in durable ParameterFacet records; the provider copy is maintained independently.

* OCI Secret Management has no charge for secret versions or retrieval; only an HSM-protected protecting key above 20 versions or a private vault (USD 3.724/hour) would bill, and the default software-protected key is free.

* Row-store throughput (capacityOpsPerVcpuSecond, default 1500) is measured-by-tensor9 as a lower bound: the DynamoDB adapter on Cloud SQL db-custom-2-7680 (2 vCPU, PostgreSQL 16, us-west1) served 2,974 ops/s of YCSB-A at 16 threads without recorded saturation (src/main/kotlin/t9/prime/equiv/generated/eval/CloudsqlPostgresqlYcsbAT16GoYcsbV1\_0\_0.kt). Published CPU-bound pgbench reaches 3,101 read-write transactions and 20,289 point reads per vCPU-second (AWS z1d.2xlarge, PostgreSQL 14.5), so actual capacity is likely higher. Reads and writes share one coefficient: at the same adapter version, read-only YCSB-C was not faster than 50%-update YCSB-A.

* Log-broker throughput (capacityStreamMiBPerVcpuSecond 20 at 0.5 utilization, 4 GiB RAM per vCPU) is provider-documented by Google Managed Service for Apache Kafka sizing ([https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size](https://docs.cloud.google.com/managed-service-for-apache-kafka/docs/plan-cluster-size)): write-equivalent bytes are replicated writes plus a quarter of reads. Producer batches below 10 KB lower per-CPU throughput; that penalty is not modeled.

* Disk utilization 0.8 is provider-documented headroom below Cloud SQL automatic storage increase, which triggers near 91-95% full ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)). The 20 GiB reserve exceeds PostgreSQL's 1 GB default max\_wal\_size; the remainder of that reserve is unmeasured.

* CPU tiers double from 2 vCPUs to the target's largest node at 4 GiB per vCPU; each target's documented largest node bounds CPU, RAM, RAM per vCPU and disk, and the durable staging database uses Cloud SQL Enterprise (96 vCPU, 6.5 GiB per vCPU, 624 GiB, 64 TiB). Targets billed per capacity unit or throughput unit are sized by their backend instead.

* No public evidence: peak/mean work (2) and the RAM working-set fraction (0.1). Proposed measurements: the p99 one-minute rate over the monthly mean from customer CloudWatch metrics; the buffer hit ratio while stepping RAM under a fixed YCSB-B load.

* Node bounds: Cloud SQL Enterprise allows 1-96 vCPUs at 0.9-6.5 GB per vCPU and up to 64 TB with a dedicated vCPU ([https://docs.cloud.google.com/sql/docs/postgres/instance-settings](https://docs.cloud.google.com/sql/docs/postgres/instance-settings)).

* Stored GiB already includes the origin family's physical footprint assumptions; no second storage amplification is applied.

* The operations/vCPU coefficient supplies the compute requirement alongside explicit resource-hour minima.

* Copies and allocation fractions change cost only; they do not increase modeled primary capacity.

List prices read: 2026-10-22. Model: `plan-f1d938dac22a5be9a1ea14f9d47946ed474017a3` / `2026-10-22.planning.2`. Scenario: `planning-example`.

Sources: [AWS Systems Manager pricing](https://aws.amazon.com/systems-manager/pricing/), [AWS Price List API, AWSSystemsManager offer](https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSSystemsManager/current/us-east-1/index.json), [OCI Secret Management](https://www.oracle.com/security/cloud-security/secrets/).

## Costs

Estimated monthly service charges for each backend with a published cost model, at one sampled workload from that model's cost curve. Adapter hosting and Tensor9 fees are excluded. [How Tensor9 estimates costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/overview.md) explains the method, what the estimates include and how to read their qualifications.

| Backend | Sampled workload | Price basis | Origin USD/month | Backend USD/month | Difference | Mapping |
| - | - | - | -: | -: | -: | - |
| Azure App Configuration | Standard read requests: 100 operations/s; one staging copy | Cited list prices, 2026-10-22 | 0.00 | 73,118.18 | +73,118.18 | Service adapter |
| Kubernetes Secret | Standard read requests: 100 operations/s; one copy | Cited list prices, 2026-10-22 | 0.00 | 80.90 | +80.90 | Service adapter |
| OCI Vault | Standard read requests: 100 operations/s; one staging copy | Cited list prices, 2026-10-22 | 0.00 | 118.18 | +118.18 | Service adapter |
| Parameter Manager | Standard read requests: 100 operations/s; one staging copy | Cited list prices, 2026-10-22 | 0.00 | 318.51 | +318.51 | Service adapter |
| Secret Manager | Standard read requests: 100 operations/s; one staging copy | Cited list prices, 2026-10-22 | 0.00 | 238.34 | +238.34 | Service adapter |

Difference means backend minus origin; a positive difference means the backend costs more. Workloads and target configurations differ by model, so compare each row's difference at its stated workload rather than charges across rows.
Cost curves across workload sizes, with every assumption and exclusion: [Systems Manager (SSM) costs](https://docs.tensor9.com/cloud-adapter-early-access/costs/additional-services/aws-ssm).

## Service level agreements

> [!WARNING]
>
> These tables show Tensor9's standard service levels and adapters whose standard terms are still being defined. Your signed agreement determines the SLAs, covered adapters and operations, limits, remedies and support terms that apply to your deployment.

Listed terms cover requests sent through this service adapter. They do not cover direct connections to the target service or replace the cloud provider's own SLA. Each origin-to-target pair has its own terms or an explicit pending status.

See the [SLA tables](https://docs.tensor9.com/cloud-adapter-early-access/support/service-adapter-slas.md), [measurement rules](https://docs.tensor9.com/cloud-adapter-early-access/support/service-levels.md), and [scaling conditions](https://docs.tensor9.com/cloud-adapter-early-access/support/scaling-and-limits.md).

### Systems Manager (SSM) to Azure App Configuration

| SLA | Service level | What is covered | Conditions |
| - | - | - | - |
| Point parameter reads adapter-added latency | +3 ms monthly p99 | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory` | Value at most 64 KiB; one named parameter and version. GetParameterHistory requires exactly one retained version, not a one-entry page from a longer history. |
| Bounded batch and path reads adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DescribeParameters`, `GetParameters`, `GetParametersByPath` | at most 50 requested or returned parameters and at most 1 MiB total values. |
| Parameter and version mutation adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | One parameter, at most 64 KiB value, at most 100 retained versions/labels. DeleteParameters covers a one-name batch; larger batches require a separately agreed budget. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory`, `DescribeParameters`, `GetParameters`, `GetParametersByPath`, `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |

**Adapter-added latency.** A + prefix marks time added by the adapter, not the total time your application waits. Total request time includes adapter processing, backend service time and network time. The backend provider's SLA applies independently. Only separately measured target-service wait may be subtracted, and only when your agreement permits it; internal metadata, coordination and retry processing still count. For one request, 12 ms of adapter processing plus 90 ms waiting for the backend means at least 102 ms total. This example does not add monthly p99 values.

**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.

**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.

**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

#### What this adapter does

Parameter reads are adapter lookups plus AWS-shape conversion; writes validate names, types, encryption choices and version transitions before committing durable adapter state. Reconciliation to azure::1.0.0::app-configuration is asynchronous unless the directed profile explicitly states otherwise, so provider execution is not hidden inside the proposed fabric latency.

#### How the latency targets were chosen

**Point parameter reads: +3 ms monthly p99 (adapter-added).** `GetParameter`, `GetParameterHistory`. Local lookup, authorization and AWS response conversion.

**Bounded batch and path reads: +10 ms monthly p99 (adapter-added).** `DescribeParameters`, `GetParameters`, `GetParametersByPath`. Bounded fan-out/page assembly without provider execution.

**Parameter and version mutation: +10 ms monthly p99 (adapter-added).** `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter`. Validation and serialized durable mutation per parameter.

Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

#### What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.

For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

#### Endpoint reachability and request failures

The endpoint-reachability target measures adapter health checks. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures remain Tensor9's responsibility even when the target is healthy.

Correctness and data-integrity requirements apply to every supported request. Endpoint reachability does not measure request correctness or grant an allowance for incorrect results.

#### Scaling and target-service capacity

Independent parameter names shard naturally. Path and discovery calls are bounded page operations and must be qualified with a fixed returned-entry and examined-entry limit. Hot-name writes, version-label moves and encryption-key use are measured separately from broad read traffic; no target-store quota is represented as adapter capacity.

Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

#### Data and behavior guarantees

Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access.

#### Example and diagnosis

An application reads ten parameters while a deployment updates one unrelated name. The batch-read target covers the adapter's lookup and response assembly for those ten names. The write target covers validation and durable version creation; later target reconciliation is observable separately and cannot rewrite the version returned to the caller.

Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

### Systems Manager (SSM) to Google Parameter Manager

| SLA | Service level | What is covered | Conditions |
| - | - | - | - |
| Point parameter reads adapter-added latency | +3 ms monthly p99 | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory` | Value at most 64 KiB; one named parameter and version. GetParameterHistory requires exactly one retained version, not a one-entry page from a longer history. |
| Bounded batch and path reads adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DescribeParameters`, `GetParameters`, `GetParametersByPath` | at most 50 requested or returned parameters and at most 1 MiB total values. |
| Parameter and version mutation adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | One parameter, at most 64 KiB value, at most 100 retained versions/labels. DeleteParameters covers a one-name batch; larger batches require a separately agreed budget. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory`, `DescribeParameters`, `GetParameters`, `GetParametersByPath`, `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |

**Adapter-added latency.** A + prefix marks time added by the adapter, not the total time your application waits. Total request time includes adapter processing, backend service time and network time. The backend provider's SLA applies independently. Only separately measured target-service wait may be subtracted, and only when your agreement permits it; internal metadata, coordination and retry processing still count. For one request, 12 ms of adapter processing plus 90 ms waiting for the backend means at least 102 ms total. This example does not add monthly p99 values.

**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.

**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.

**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

#### What this adapter does

Parameter reads are adapter lookups plus AWS-shape conversion; writes validate names, types, encryption choices and version transitions before committing durable adapter state. Reconciliation to google::1.0.0::parameter-manager is asynchronous unless the directed profile explicitly states otherwise, so provider execution is not hidden inside the proposed fabric latency.

#### How the latency targets were chosen

**Point parameter reads: +3 ms monthly p99 (adapter-added).** `GetParameter`, `GetParameterHistory`. Local lookup, authorization and AWS response conversion.

**Bounded batch and path reads: +10 ms monthly p99 (adapter-added).** `DescribeParameters`, `GetParameters`, `GetParametersByPath`. Bounded fan-out/page assembly without provider execution.

**Parameter and version mutation: +10 ms monthly p99 (adapter-added).** `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter`. Validation and serialized durable mutation per parameter.

Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

#### What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.

For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

#### Endpoint reachability and request failures

The endpoint-reachability target measures adapter health checks. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures remain Tensor9's responsibility even when the target is healthy.

Correctness and data-integrity requirements apply to every supported request. Endpoint reachability does not measure request correctness or grant an allowance for incorrect results.

#### Scaling and target-service capacity

Independent parameter names shard naturally. Path and discovery calls are bounded page operations and must be qualified with a fixed returned-entry and examined-entry limit. Hot-name writes, version-label moves and encryption-key use are measured separately from broad read traffic; no target-store quota is represented as adapter capacity.

Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

#### Data and behavior guarantees

Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access.

#### Example and diagnosis

An application reads ten parameters while a deployment updates one unrelated name. The batch-read target covers the adapter's lookup and response assembly for those ten names. The write target covers validation and durable version creation; later target reconciliation is observable separately and cannot rewrite the version returned to the caller.

Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

### Systems Manager (SSM) to Secret Manager

| SLA | Service level | What is covered | Conditions |
| - | - | - | - |
| Point parameter reads adapter-added latency | +3 ms monthly p99 | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory` | Value at most 64 KiB; one named parameter and version. GetParameterHistory requires exactly one retained version, not a one-entry page from a longer history. |
| Bounded batch and path reads adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DescribeParameters`, `GetParameters`, `GetParametersByPath` | at most 50 requested or returned parameters and at most 1 MiB total values. |
| Parameter and version mutation adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | One parameter, at most 64 KiB value, at most 100 retained versions/labels. DeleteParameters covers a one-name batch; larger batches require a separately agreed budget. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory`, `DescribeParameters`, `GetParameters`, `GetParametersByPath`, `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter` | Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |

**Adapter-added latency.** A + prefix marks time added by the adapter, not the total time your application waits. Total request time includes adapter processing, backend service time and network time. The backend provider's SLA applies independently. Only separately measured target-service wait may be subtracted, and only when your agreement permits it; internal metadata, coordination and retry processing still count. For one request, 12 ms of adapter processing plus 90 ms waiting for the backend means at least 102 ms total. This example does not add monthly p99 values.

**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.

**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.

**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

#### What this adapter does

Parameter reads are adapter lookups plus AWS-shape conversion; writes validate names, types, encryption choices and version transitions before committing durable adapter state. Reconciliation to google::1.0.0::secret-manager is asynchronous unless the directed profile explicitly states otherwise, so provider execution is not hidden inside the proposed fabric latency.

#### How the latency targets were chosen

**Point parameter reads: +3 ms monthly p99 (adapter-added).** `GetParameter`, `GetParameterHistory`. Local lookup, authorization and AWS response conversion.

**Bounded batch and path reads: +10 ms monthly p99 (adapter-added).** `DescribeParameters`, `GetParameters`, `GetParametersByPath`. Bounded fan-out/page assembly without provider execution.

**Parameter and version mutation: +10 ms monthly p99 (adapter-added).** `DeleteParameter`, `DeleteParameters`, `LabelParameterVersion`, `PutParameter`. Validation and serialized durable mutation per parameter.

Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

#### What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.

For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

#### Endpoint reachability and request failures

The endpoint-reachability target measures adapter health checks. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures remain Tensor9's responsibility even when the target is healthy.

Correctness and data-integrity requirements apply to every supported request. Endpoint reachability does not measure request correctness or grant an allowance for incorrect results.

#### Scaling and target-service capacity

Independent parameter names shard naturally. Path and discovery calls are bounded page operations and must be qualified with a fixed returned-entry and examined-entry limit. Hot-name writes, version-label moves and encryption-key use are measured separately from broad read traffic; no target-store quota is represented as adapter capacity.

Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

#### Data and behavior guarantees

Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access.

#### Example and diagnosis

An application reads ten parameters while a deployment updates one unrelated name. The batch-read target covers the adapter's lookup and response assembly for those ten names. The write target covers validation and durable version creation; later target reconciliation is observable separately and cannot rewrite the version returned to the caller.

Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

### Systems Manager (SSM) to OCI Vault

| SLA | Service level | What is covered | Conditions |
| - | - | - | - |
| Point parameter reads adapter-added latency | +3 ms monthly p99 | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory` | Value at most 64 KiB; one named parameter and version. GetParameterHistory requires exactly one retained version, not a one-entry page from a longer history. |
| Bounded batch and path reads adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DescribeParameters`, `GetParameters`, `GetParametersByPath` | at most 50 requested or returned parameters and at most 1 MiB total values. |
| Parameter and version mutation adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DeleteParameter`, `DeleteParameters`, `PutParameter` | One parameter, at most 64 KiB value, at most 100 retained versions/labels. DeleteParameters covers a one-name batch; larger batches require a separately agreed budget. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::ssm`: `GetParameter`, `GetParameterHistory`, `DescribeParameters`, `GetParameters`, `GetParametersByPath`, `DeleteParameter`, `DeleteParameters`, `PutParameter` | Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |

**Adapter-added latency.** A + prefix marks time added by the adapter, not the total time your application waits. Total request time includes adapter processing, backend service time and network time. The backend provider's SLA applies independently. Only separately measured target-service wait may be subtracted, and only when your agreement permits it; internal metadata, coordination and retry processing still count. For one request, 12 ms of adapter processing plus 90 ms waiting for the backend means at least 102 ms total. This example does not add monthly p99 values.

**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.

**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.

**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

#### What this adapter does

Parameter reads are adapter lookups plus AWS-shape conversion; writes validate names, types, encryption choices and version transitions before committing durable adapter state. Reconciliation to oci::1.0.0::vault is asynchronous unless the directed profile explicitly states otherwise, so provider execution is not hidden inside the proposed fabric latency.

#### How the latency targets were chosen

**Point parameter reads: +3 ms monthly p99 (adapter-added).** `GetParameter`, `GetParameterHistory`. Local lookup, authorization and AWS response conversion.

**Bounded batch and path reads: +10 ms monthly p99 (adapter-added).** `DescribeParameters`, `GetParameters`, `GetParametersByPath`. Bounded fan-out/page assembly without provider execution.

**Parameter and version mutation: +10 ms monthly p99 (adapter-added).** `DeleteParameter`, `DeleteParameters`, `PutParameter`. Validation and serialized durable mutation per parameter.

Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

#### What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.

For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

#### Endpoint reachability and request failures

The endpoint-reachability target measures adapter health checks. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures remain Tensor9's responsibility even when the target is healthy.

Correctness and data-integrity requirements apply to every supported request. Endpoint reachability does not measure request correctness or grant an allowance for incorrect results.

#### Scaling and target-service capacity

Independent parameter names shard naturally. Path and discovery calls are bounded page operations and must be qualified with a fixed returned-entry and examined-entry limit. Hot-name writes, version-label moves and encryption-key use are measured separately from broad read traffic; no target-store quota is represented as adapter capacity.

Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

#### Data and behavior guarantees

Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access.

#### Example and diagnosis

An application reads ten parameters while a deployment updates one unrelated name. The batch-read target covers the adapter's lookup and response assembly for those ten names. The write target covers validation and durable version creation; later target reconciliation is observable separately and cannot rewrite the version returned to the caller.

Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

### Systems Manager (SSM) to Kubernetes Secrets

| SLA | Service level | What is covered | Conditions |
| - | - | - | - |
| Point parameter reads adapter-added latency | +3 ms monthly p99 | `aws::1.0.0::ssm`: `GetParameter` | Value at most 64 KiB; one named parameter and version. GetParameterHistory requires exactly one retained version, not a one-entry page from a longer history. |
| Bounded batch and path reads adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DescribeParameters`, `GetParameters`, `GetParametersByPath` | at most 50 requested or returned parameters and at most 1 MiB total values. |
| Parameter and version mutation adapter-added latency | +10 ms monthly p99 | `aws::1.0.0::ssm`: `DeleteParameter`, `DeleteParameters`, `PutParameter` | One parameter, at most 64 KiB value, at most 100 retained versions/labels. DeleteParameters covers a one-name batch; larger batches require a separately agreed budget. |
| Documented adapter behavior | Preserve the supported behavior documented for this adapter | `aws::1.0.0::ssm`: `GetParameter`, `DescribeParameters`, `GetParameters`, `GetParametersByPath`, `DeleteParameter`, `DeleteParameters`, `PutParameter` | Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access. |
| Endpoint reachability | 99.9% per calendar month | Adapter endpoint reachability | The agreed production deployment has healthy target connectivity and receives a valid adapter health probe. This measures the adapter endpoint, not the target provider's service. |
| Adapter autoscaling and limits | Automatic scaling within the workload and deployment limits in your agreement | Adapter behavior across requests | Your agreement states the maximum request rate, burst size, request and response sizes, concurrency, and target calls per request. Tensor9 maintains adapter capacity inside that envelope. Target-service quotas and capacity are separate. |

**Adapter-added latency.** A + prefix marks time added by the adapter, not the total time your application waits. Total request time includes adapter processing, backend service time and network time. The backend provider's SLA applies independently. Only separately measured target-service wait may be subtracted, and only when your agreement permits it; internal metadata, coordination and retry processing still count. For one request, 12 ms of adapter processing plus 90 ms waiting for the backend means at least 102 ms total. This example does not add monthly p99 values.

**What Tensor9 covers.** These service levels cover the adapter between the origin API and target API. They do not replace the target provider's SLA.

**How latency is counted.** Adapter work, including metadata and coordination, counts. Only separately measured permitted target waits are excluded.

**Which terms apply.** Your signed agreement names the covered operations, workload limits, remedies, and final service levels for your deployment.

#### What this adapter does

Parameter reads are adapter lookups plus AWS-shape conversion; writes validate names, types, encryption choices and version transitions before committing durable adapter state. Reconciliation to tensor9::1.0.0::emu::aws/1.0.0/ssm::kube is asynchronous unless the directed profile explicitly states otherwise, so provider execution is not hidden inside the proposed fabric latency.

#### How the latency targets were chosen

**Point parameter reads: +3 ms monthly p99 (adapter-added).** `GetParameter`. Local lookup, authorization and AWS response conversion.

**Bounded batch and path reads: +10 ms monthly p99 (adapter-added).** `DescribeParameters`, `GetParameters`, `GetParametersByPath`. Bounded fan-out/page assembly without provider execution.

**Parameter and version mutation: +10 ms monthly p99 (adapter-added).** `DeleteParameter`, `DeleteParameters`, `PutParameter`. Validation and serialized durable mutation per parameter.

Your signed agreement sets the terms for your deployment. A target does not add an operation or option that the compatibility tables mark unavailable.

#### What counts toward latency

For a request-response row, measure from the agreed ingress boundary to dispatch of the complete response. A row that explicitly names a first response chunk ends at that chunk; its number does not cover the rest of the stream. A long-poll row names the intentional wait and when adapter delay starts. Include parsing, authorization, admission, translation, serialization, adapter-owned storage and coordination, retries and response handling. Subtract only separately measured target-workload waits and external network segments allowed by the measurement rules. The adapter's own response handling and dispatch remain covered. A database used for adapter metadata is still adapter work, even if a cloud provider hosts it.

For concurrent calls, exclude the union of permitted wait intervals, not the sum of overlapping spans. Calculate each request's adapter duration first, then the monthly p99. Do not subtract one service's p99 from another's. Known adapter timeouts are over-budget samples; failed or incomplete requests cannot disappear to improve the percentile. Missing measurements do not become zero latency. An SDK call span alone does not prove how much of its duration can be excluded.

#### Endpoint reachability and request failures

The endpoint-reachability target measures adapter health checks. Correctly forwarding a target quota or permission error is different from producing that error because the adapter sent the wrong request. Adapter-caused failures remain Tensor9's responsibility even when the target is healthy.

Correctness and data-integrity requirements apply to every supported request. Endpoint reachability does not measure request correctness or grant an allowance for incorrect results.

#### Scaling and target-service capacity

Independent parameter names shard naturally. Path and discovery calls are bounded page operations and must be qualified with a fixed returned-entry and examined-entry limit. Hot-name writes, version-label moves and encryption-key use are measured separately from broad read traffic; no target-store quota is represented as adapter capacity.

Tell Tensor9 the expected steady rate, bursts, concurrency, payload sizes and operation mix. Tensor9 sizes and scales the adapter for the agreed load; you choose and monitor the target service's capacity with Tensor9's help. A latency budget is not a requests-per-second rating. Larger requests and higher rates need explicit terms, not silent inheritance of a small-request SLA.

#### Data and behavior guarantees

Successful writes preserve value bytes, type, version and label ownership. SecureString never falls back to plaintext, WithDecryption=false retains ciphertext semantics where supported, and unsupported Advanced-tier policies or public/shared parameters fail explicitly rather than widening access.

#### Example and diagnosis

An application reads ten parameters while a deployment updates one unrelated name. The batch-read target covers the adapter's lookup and response assembly for those ten names. The write target covers validation and durable version creation; later target reconciliation is observable separately and cannot rewrite the version returned to the caller.

Use `tensor9 explain` and the documented explain headers to understand the selected adapter and its behavior. Correlate available request diagnostics with the target provider's latency, throttling and capacity metrics. An explain report helps diagnose a request; it is not by itself a qualified SLA timing measurement. Share the operation, request shape, timestamps and request identifiers with support, with credentials and customer payloads removed.

## Install and run

The documentation and SLAs are public. Downloading and running the Cloud Adapter binary requires an entitled customer account. Set `T9_API_KEY` as described in [Install and Authenticate](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/install-and-authenticate.md), then list the adapters your account may use with this origin:

```sh theme={null}
tensor9 adapt svc list \
  -origin aws::1.0.0::ssm
```

The result is limited to directed mappings for this origin that your account is entitled to use. Use a returned backend identifier when configuring the adapter or investigating a request.

Request binary access from [hello@tensor9.com](mailto:hello@tensor9.com) if your account does not yet include this direction.

## Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application's endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

## Configure, tune and debug

Start with [setup](https://docs.tensor9.com/cloud-adapter-early-access/getting-started/overview.md) and [configuration](https://docs.tensor9.com/cloud-adapter-early-access/configuration/overview.md). Use [tuning](https://docs.tensor9.com/cloud-adapter-early-access/tuning/overview.md) to understand supported request tags, [debugging](https://docs.tensor9.com/cloud-adapter-early-access/debugging/overview.md) to investigate a request, and [High Fidelity Cloud Emulators](https://docs.tensor9.com/cloud-adapter-early-access/local-testing/overview.md) to validate a bounded reproduction.

For requests that go through an entitled service adapter, use [tensor9 explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/explain.md) and [x-t9-explain](https://docs.tensor9.com/cloud-adapter-early-access/debugging/response-headers.md) to inspect the selected mapping.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.