AWS wellarchitected medium security documentation change
Summary
Expanded documentation on implementing model catalogs for foundation models, including governance, security controls, and maintenance procedures. Added details about AI policy documents and restructured implementation steps.
Security assessment
The changes explicitly add security-related content including 'Design access control framework' and 'Implement security controls' under governance steps. These additions directly address security considerations for model management, though no specific vulnerability is mentioned. The emphasis on tracking model access and security controls improves security posture.
Diff
diff --git a/wellarchitected/latest/generative-ai-lens/genrel04-bp02.md b/wellarchitected/latest/generative-ai-lens/genrel04-bp02.md index 598daa8ac..693d4062b 100644 --- a//wellarchitected/latest/generative-ai-lens/genrel04-bp02.md +++ b//wellarchitected/latest/generative-ai-lens/genrel04-bp02.md @@ -19 +19 @@ Model catalogs store and manage model versions. They act as a reliable store for -Model catalogs provide a centralized location to review models, model version, and model cards. Traditionally, model catalogs are meant to store model artifacts developed by customers. Foundation models are rarely developed from scratch, and as a result, foundation model catalogs should maintain first-party models, third-party models, and custom models developed from third-party models. +Model catalogs provide a centralized location to review models, model versions, and model cards. Traditionally, model catalogs are meant to store model artifacts developed by customers. Foundation models are rarely developed from scratch, and as a result, foundation model catalogs should maintain first-party models, third-party models, and custom models developed from third-party models. @@ -21 +21,3 @@ Model catalogs provide a centralized location to review models, model version, a -Customers should consider implementing a model catalog for foundation models that records and tracks model access, model versions, and model card information. Consider using the Amazon Bedrock model catalog in the AWS Management Console to track available models. Amazon Bedrock's model catalog facilitates model subscriptions to third-party models in the Amazon Bedrock Marketplace as well. Model catalogs should provide a central location for model management, particularly if there is a need to roll back to a particular model or model version. +Consider implementing a model catalog for foundation models that records and tracks model access, model versions, and model card information. Maintain a model catalog in your environment to track available models. Model catalogs should provide a central location for model management, particularly if there is a need to roll back to a particular model or model version. + +AI policy documents should provide clear details regarding the usage, maintenance, and updating of the model catalog. The AI policy document is intended to be the central authority for operational questions pertaining to AI workloads and supporting infrastructure. Keep this document up to date with the appropriate materials necessary to scale the usage of the model catalog throughout the organization. @@ -25 +27,57 @@ Customers should consider implementing a model catalog for foundation models tha - 1. Navigate to the model catalog in Amazon Bedrock. + 1. Set up catalog structure: + + * Create model classification system (by type, purpose, and provider) + + * Define model metadata schema + + * Establish versioning conventions + + * Design access control framework + + 2. Configure model tracking: + + * Record model lineage and dependencies + + * Track model versions and updates + + * Document model customizations + + * Maintain performance benchmarks + + 3. Implement model cards: + + * Define required model information + + * Document model capabilities and limitations + + * Record training data characteristics + + * Specify intended use cases and constraints + + * Include ethical considerations and biases + + 4. Establish model governance: + + * Create model approval workflows + + * Define deployment procedures + + * Set up model monitoring + + * Implement security controls + + * Track model usage and access + + 5. Create maintenance procedures: + + * Define model update process + + * Establish deprecation policies + + * Create archival procedures + + * Set up backup and recovery + + 6. Implement validation framework: + + * Create model testing procedures @@ -27 +85 @@ Customers should consider implementing a model catalog for foundation models tha - 2. Select a model from the catalog. + * Define acceptance criteria @@ -29 +87 @@ Customers should consider implementing a model catalog for foundation models tha - 3. Select the appropriate option from the list (for example, open in playground or customize). + * Set up performance benchmarking @@ -31 +89 @@ Customers should consider implementing a model catalog for foundation models tha - 4. For self-hosted models, consider the [bring your own endpoint feature](https://docs.aws.amazon.com/bedrock/latest/userguide/bedrock-marketplace-bring-your-own-endpoint.html). + * Establish quality gates @@ -38 +96 @@ Customers should consider implementing a model catalog for foundation models tha -**Related practices:** +**Related best practices:** @@ -47 +105 @@ Customers should consider implementing a model catalog for foundation models tha -**Related guides, videos, and documentation:** +**Related documents:**