AWS prescriptive-guidance documentation change
Summary
Restructured protocol selection guidance, added security/compliance best practices, and removed redundant sections.
Security assessment
Added explicit security recommendations (authentication, encryption, audit capabilities) and compliance requirements. Enhances security documentation but doesn't address a specific vulnerability.
Diff
diff --git a/prescriptive-guidance/latest/agentic-ai-frameworks/selecting-agentic-protocols.md b/prescriptive-guidance/latest/agentic-ai-frameworks/selecting-agentic-protocols.md index a8912732b..58d814f12 100644 --- a//prescriptive-guidance/latest/agentic-ai-frameworks/selecting-agentic-protocols.md +++ b//prescriptive-guidance/latest/agentic-ai-frameworks/selecting-agentic-protocols.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Agentic AI frameworks, protocols, and tools on AWS](introduction.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Agentic AI frameworks, platforms, protocols, and tools on AWS](introduction.html) @@ -5 +5 @@ -Enterprise protocol considerationsStartup and SMB protocol considerationsGovernment and regulated industry protocol considerations +Agentic protocol selection considerations @@ -13 +13 @@ Selecting the right agentic protocols is important for organizations looking to -## Enterprise protocol considerations +## Agentic protocol selection considerations @@ -15 +15 @@ Selecting the right agentic protocols is important for organizations looking to -Enterprises should consider the following actions: +Organizations should consider the following best practices when selecting protocols for agentic AI systems:: @@ -17 +17 @@ Enterprises should consider the following actions: - * Prioritize open protocols like MCP for strategic, long-term agent implementations. + * **Prioritize open standards** – Organizations should adopt open protocols such as the MCP to help ensure long-term interoperability, extensibility, and to reduce the risk of vendor lock-in. @@ -19 +19 @@ Enterprises should consider the following actions: - * Implement abstraction layers when using proprietary protocols to ease future migrations. + * **Balance speed and flexibility** – Startups and early adopters may begin with well-supported proprietary protocols for rapid development but should define a migration path to open standards as systems mature. @@ -21 +21 @@ Enterprises should consider the following actions: - * Participate in standards development to influence protocol evolution. + * **Implement abstraction layers** – Enterprises should implement protocol abstraction to simplify migration, enable hybrid adoption, and future-proof integration strategies. @@ -23 +23 @@ Enterprises should consider the following actions: - * Consider hybrid approaches that use open protocols for core infrastructure and proprietary protocols for specific use cases. + * **Emphasize security and compliance** – Organizations in regulated industries should select protocols with robust authentication, encryption, and audit capabilities to meet governance and compliance requirements. @@ -24,0 +25 @@ Enterprises should consider the following actions: + * **Evaluate ecosystem maturity** – All organizations should assess the health, adoption, and community support of each protocol to ensure sustainability and minimize technical debt. @@ -25,0 +27 @@ Enterprises should consider the following actions: + * **Engage in standards development** – Organizations should participate in standards bodies or open-source communities to help shape protocol evolution and influence best practices. @@ -26,0 +29 @@ Enterprises should consider the following actions: + * **Account for data sovereignty** – Government and regulated sectors should ensure protocol choices align with data residency and sovereignty requirements across deployment regions. @@ -28,26 +31 @@ Enterprises should consider the following actions: -## Startup and SMB protocol considerations - -Startups and small-to-medium (SMB) businesses should consider the following actions: - - * Balance speed and flexibility by starting with well-supported proprietary protocols for rapid development. - - * Plan migration paths to use more open standards as your needs mature. - - * Evaluate protocol adoption trends to avoid investing in declining standards. - - * Consider managed services that abstract protocol complexity. - - - - -## Government and regulated industry protocol considerations - -Government and regulated industries should consider the following actions: - - * Emphasize open standards to ensure long-term access and avoid vendor lock-in. - - * Prioritize protocols with strong security models and authentication mechanisms. - - * Consider data sovereignty implications of remote and local deployment models. - - * Document protocol decisions for compliance and governance requirements. + * **Leverage managed services** – Where possible, use managed or serverless implementations of agentic protocols to reduce operational complexity and accelerate deployment.