Developers can use several foundation models.
Prevent an unevaluated model from reaching production.
Which mechanism is most appropriate?
Register and distribute only models whose evaluation, license, version, provider, and use limits have been checked.
Detailed explanation
Approved artifacts can be traced and used.
Approved artifacts can be traced and used.
A name does not prove approval or integrity.
A name does not prove approval or integrity.
Popularity does not prove safety, legality, or fit.
Popularity does not prove safety, legality, or fit.
An unevaluated artifact reaches production first.
An unevaluated artifact reaches production first.
Try it yourself
An example you can run in a temporary verification environment.
AWS公式AIF-C01 Domain 5.3のモデル供給網、承認、アーティファクト管理を確認する。Expected result
モデル名や人気ではなく、検証済みアーティファクトだけを利用させる仕組みを説明できる。Key points
- Model registry
- Approval
- Artifact
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.