AWS managedservices documentation change
Summary
Changed 'AWS CloudFormation templates' to 'CloudFormation templates' (removed 'AWS' branding)
Security assessment
The change is a minor terminology adjustment without altering security context. No evidence of addressing vulnerabilities or modifying security practices.
Diff
diff --git a/managedservices/latest/userguide/self-service-provisioning-section.md b/managedservices/latest/userguide/self-service-provisioning-section.md index a1225d454..e13d09a0f 100644 --- a//managedservices/latest/userguide/self-service-provisioning-section.md +++ b//managedservices/latest/userguide/self-service-provisioning-section.md @@ -7 +7 @@ -AWS Managed Services (AMS) Self-Service Provisioning (SSP) mode provides full access to native AWS service and API capabilities in AMS managed accounts. You access services through standardized, scoped down, AWS Identity and Access Management roles. AMS provides service requests and incident management. Alerting, monitoring, logging, patch, back up, and change management are your responsibility. In many cases, Self-Service Provisioning services (SSPS) are self-managed, or serverless, and don’t require management of certain operational tasks like patching. You benefit from using these services within the environment boundary defined by AMS guardrails and any IAM changes (including service linked roles, service roles, cross-account roles, or policy updates) need to be approved by AMS Operations to maintain the baseline security of the platform. You can leverage AWS CloudFormation templates to automate deployment of these services, but this isn't supported for all SSP services. +AWS Managed Services (AMS) Self-Service Provisioning (SSP) mode provides full access to native AWS service and API capabilities in AMS managed accounts. You access services through standardized, scoped down, AWS Identity and Access Management roles. AMS provides service requests and incident management. Alerting, monitoring, logging, patch, back up, and change management are your responsibility. In many cases, Self-Service Provisioning services (SSPS) are self-managed, or serverless, and don’t require management of certain operational tasks like patching. You benefit from using these services within the environment boundary defined by AMS guardrails and any IAM changes (including service linked roles, service roles, cross-account roles, or policy updates) need to be approved by AMS Operations to maintain the baseline security of the platform. You can leverage CloudFormation templates to automate deployment of these services, but this isn't supported for all SSP services.