EC2 Auto Scaling costs

Tensor9 BYOC planning comparisons for aws::1.0.0::autoscaling::group, with backend choices shown together. Read how to think about service-adapter costs for price scope and capacity qualification, or return to additional services.

​

Autoscaling fleet allocation → Droplet Autoscale Group

Origin API: aws::1.0.0::autoscaling::group. Target backend: digitalocean::1.0.0::droplet-autoscale. 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.

​

Autoscaling fleet allocation · Allocated fleet instance-hours per month

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. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
• All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This native fleet resource comparison is separate from the Auto Scaling runtime discovery adapter and its supported operations.
• Instance-hours are priced exactly once as CPU and RAM allocation; management requests add no assumed fleet instances.
• All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
• Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.

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

• Instance disks, traffic, licenses, load balancers, spare replacement instances and metric collection.
• 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.

Planning assumptions authored: 2026-10-18. Model: plan-405f4ab266894594207619999901dc5415c89df4 / 2026-10-18.planning.1. Curve: workload-1.

​

Autoscaling fleet allocation → Instance Pool

Origin API: aws::1.0.0::autoscaling::group. Target backend: oci::1.0.0::instance-pool. 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.

​

Autoscaling fleet allocation · Allocated fleet instance-hours per month

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. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
• All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This native fleet resource comparison is separate from the Auto Scaling runtime discovery adapter and its supported operations.
• Instance-hours are priced exactly once as CPU and RAM allocation; management requests add no assumed fleet instances.
• All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
• Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.

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

• Instance disks, traffic, licenses, load balancers, spare replacement instances and metric collection.
• 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.

Planning assumptions authored: 2026-10-18. Model: plan-b9d9d674ce3cf500fa29965fbf7437beb4b8d35e / 2026-10-18.planning.1. Curve: workload-1.

​

Autoscaling fleet allocation → Managed Instance Group

Origin API: aws::1.0.0::autoscaling::group. Target backend: google::1.0.0::compute::instance-group-manager. 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.

​

Autoscaling fleet allocation · Allocated fleet instance-hours per month

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. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
• All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This native fleet resource comparison is separate from the Auto Scaling runtime discovery adapter and its supported operations.
• Instance-hours are priced exactly once as CPU and RAM allocation; management requests add no assumed fleet instances.
• All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
• Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.

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

• Instance disks, traffic, licenses, load balancers, spare replacement instances and metric collection.
• 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.

Planning assumptions authored: 2026-10-18. Model: plan-b9670e638465fc9e05fb9206b711b51ee8d7611e / 2026-10-18.planning.1. Curve: workload-1.

​

Autoscaling fleet allocation → Virtual Machine Scale Sets

Origin API: aws::1.0.0::autoscaling::group. Target backend: azure::1.0.0::vmss. 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.

​

Autoscaling fleet allocation · Allocated fleet instance-hours per month

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. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
• All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This native fleet resource comparison is separate from the Auto Scaling runtime discovery adapter and its supported operations.
• Instance-hours are priced exactly once as CPU and RAM allocation; management requests add no assumed fleet instances.
• All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
• Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.

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

• Instance disks, traffic, licenses, load balancers, spare replacement instances and metric collection.
• 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.

Planning assumptions authored: 2026-10-18. Model: plan-82812da0f423869e63eda34be31dc83ce60055ad / 2026-10-18.planning.1. Curve: workload-1.

​

Autoscaling fleet allocation → VirtualMachinePool

Origin API: aws::1.0.0::autoscaling::group. Target backend: kubevirt::1.0.0::virtual-machine-pool. 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.

​

Autoscaling fleet allocation · Allocated fleet instance-hours per month

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. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed 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 is a declared directed mapping; a planning estimate does not establish deployment or request-serving support.
• All default unit prices and capacity coefficients are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This native fleet resource comparison is separate from the Auto Scaling runtime discovery adapter and its supported operations.
• Instance-hours are priced exactly once as CPU and RAM allocation; management requests add no assumed fleet instances.
• All target rates are editable authored planning guesses, not verified current list prices, customer discounts or benchmark evidence.
• Allocated VM/fleet CPU and memory hours are explicit physical usage. Management API counts never create VM-hours.

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

• Instance disks, traffic, licenses, load balancers, spare replacement instances and metric collection.
• 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.

Planning assumptions authored: 2026-10-18. Model: plan-3ce4fd3066be8e513dee674ece91d26221463200 / 2026-10-18.planning.1. Curve: workload-1. See the service catalog for operation coverage, supported directions and backend limitations.