azure::1.0.0::mysql::flexible, with backend choices shown together. Read how to think about service-adapter costs for price scope and capacity qualification, or return to additional services.
Azure MySQL Flexible Server → Cloud SQL for MySQL
Origin API:azure::1.0.0::mysql::flexible. Target backend: google::1.0.0::cloudsql::mysql.
Planning estimate with editable assumptions. Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions.
Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
Azure MySQL Flexible Server · Primary allocated compute
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- CPU allocation does not imply an achieved transaction rate. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-e57f7ffe0ebc14b9a56d6bfe1599e4ef0c1ee6f2 / 2026-10-18.planning.1. Curve: workload-1.
Azure MySQL Flexible Server · Stored data
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Request meters remain at their independently authored defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-e57f7ffe0ebc14b9a56d6bfe1599e4ef0c1ee6f2 / 2026-10-18.planning.1. Curve: workload-2.
Azure MySQL Flexible Server · Database writes
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Source compute and stored data remain independent; a throughput view needs explicit workload inputs. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-e57f7ffe0ebc14b9a56d6bfe1599e4ef0c1ee6f2 / 2026-10-18.planning.1. Curve: workload-3.
Azure MySQL Flexible Server → RDS MySQL
Origin API:azure::1.0.0::mysql::flexible. Target backend: aws::1.0.0::rds::mysql.
Planning estimate with editable assumptions. Unit rates, workload amplification and capacity assumptions are educated guesses awaiting verification. The displayed amounts are planning estimates, not verified provider list-price quotes or benchmark-qualified capacity. Region names identify the authored scenario assumptions.
Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.
Azure MySQL Flexible Server · Primary allocated compute
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- CPU allocation does not imply an achieved transaction rate. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-5ad440e5920796f270acdf637ebd19abecf853f5 / 2026-10-18.planning.1. Curve: workload-1.
Azure MySQL Flexible Server · Stored data
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Request meters remain at their independently authored defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-5ad440e5920796f270acdf637ebd19abecf853f5 / 2026-10-18.planning.1. Curve: workload-2.
Azure MySQL Flexible Server · Database writes
Planning estimate with editable assumptions. These authored unit rates and capacity assumptions require provider-price verification and representative benchmarks. They do not constitute verified list-price quotes or evidence that an adapter is available. Estimated monthly service charges from native source usage; no calculator input is required. Adapter hosting and Tensor9 fees are excluded. Source: Explicit source planning region; target: Explicit target planning region; currency: USD.
Estimated allocation from planning assumptions; not benchmark calibrated.
The sizing policy grows compute with translated work and peak headroom, memory with compute and working set, and disk with resident working state and reserve. Monthly usage is distinct from resident data; each workload’s assumptions define the translation. HA changes pricing, not this policy’s throughput estimate. Unpriced workloads exceed the policy’s configuration range; no silent vertical cap or automatic sharding is assumed.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Source compute and stored data remain independent; a throughput view needs explicit workload inputs. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
- Planning estimate · editable authored rates and sizing assumptions dated 2026-10-18; not verified provider prices. Explicit source planning region → Explicit target planning region, 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.
- Explicit tariff samples 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.
- Editable authored planning guesses, not verified provider tariffs, 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 exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
- Authored planning assumptions, not measured adapter capacity. Editable origin rates are illustrative tariff profiles, before free allowances and discounts.
- A cost scenario does not establish backend availability, protocol fidelity or production readiness. Registry serving status remains independent.
- Provisioned compute and RAM are carried as resource-hours; operations are independently authored. Database size cannot be inferred from dollars alone.
- Aurora/AlloyDB, MySQL/PostgreSQL and proxied targets retain their distinct backend contracts. HA, replicas and proxy allocations must be selected explicitly.
- All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
- Named provisioned target: selected CPU, RAM and physical disk allocation grow with workload. No additional per-database-operation price is assumed. Managed service premiums and dedicated accelerator/model-fit requirements need explicit qualification.
- Authored operation throughput, peak and working-set assumptions are not benchmark-calibrated.
- Stored GiB already includes the origin family’s physical footprint assumptions; no second storage amplification is applied.
- The workload family already selected resource-hours; the generic operations/vCPU coefficient is not applied again.
- Copies and allocation fractions change cost only; they do not increase modeled primary capacity.
- Additional network transfer, backups, KMS, one-time migration and operational labor unless an explicit meter includes them.
- Destination application execution and separately billed downstream services; supply those allocations separately.
- Aurora per-IO, serverless-capacity, backup and proxy tariffs; reserved/committed-use purchase options.
- Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
- Unmodeled dependent services, task execution and operations outside the selected workload family.
plan-5ad440e5920796f270acdf637ebd19abecf853f5 / 2026-10-18.planning.1. Curve: workload-3.
See the service catalog for operation coverage, supported directions and backend limitations.