Amazon Bedrock Imported Model
Does ZopNight manage Amazon Bedrock Imported Model?
Bedrock imported models bill per model copy per minute while active, plus monthly storage for the model artifacts. Copies kept warm without traffic accrue serving charges for nothing. ZopNight discovers imported models via its Bedrock provider on the 6-hour cycle, tracks serving and storage cost, and recommends utilization corrections.
Rules that fire on Amazon Bedrock Imported Model
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost tracking only. |
A Bedrock imported model is an externally trained model (for example a fine-tuned open-weights model) brought into Bedrock for serving, billed per model copy per minute when active plus storage. Imported models kept warm without traffic accrue serving charges.
Minutes of model copies
Custom Model Import prices serving in a granularity unique within Bedrock: the model copy per minute. When invocations arrive, Bedrock activates a copy of the imported model and bills per copy-minute while it stays active; sustained traffic scales additional copies, each on its own minute meter, and idle periods let copies wind down. Storage for the imported artifacts bills monthly alongside. The design lands between serverless and dedicated: cheaper than provisioned capacity for intermittent traffic, but a steady trickle of requests (one call every few minutes) can keep a copy pinned active nearly continuously, billing hours of copy-minutes for seconds of inference.
Import serving, measured
ZopNight’s Bedrock provider discovers imported models on the 6-hour cycle, tracking serving and storage cost from Cost Explorer or CUR 2.0 with utilization recommendations. The copy-minute meter rewards finding models whose active minutes vastly exceed their useful inference: the keep-alive health check that pings the model endpoint, the retry loop that never backs off, the batch process spreading requests thinly across the day when an hourly burst would let copies deactivate between rounds. Storage findings cover the imports nobody serves at all.
Open-weights enthusiasm, metered
Imported models accumulate the way fine-tuned checkpoints do everywhere: a team imports several quantizations and sizes of an open model to compare, ships one, and leaves the rest stored monthly. Version upgrades strand the previous import. And traffic assumptions go stale. A model imported for a high-volume feature that shipped behind a flag serves its trickle at copy-minute rates that on-demand catalog pricing would beat.
Imports in the console
The Bedrock console’s Imported models view lists each import with size and creation date. Invocation metrics reveal the activity shape, and the difference between bursty (efficient here) and steady-trickle (expensive here) is the whole utilization story for this meter.