AWS Security ChangesHomeSearch

AWS managedservices: AMS transition: endpoint security options reordered, EPS offboarding clarified

Service: managedservices · 2026-10-24 · Documentation medium

File: managedservices/latest/userguide/transition-to-accelerate.md

Summary

Rewrites the endpoint security section of the AMS-to-Accelerate transition guide: AMS now removes Trend Micro agents and offboards the EPS/DSM stack by default (no customer action), renames Option 1 to 'Use your own endpoint security solution (default)' and Option 2 to 'Continue with Trend Micro Vision One (SaaS)', and adds a link to the new 'Connecting a new VPC to the shared Transit Gateway' page for cross-account networking.

Security assessment

The change documents that endpoint protection (Trend Micro EPS/DSM) is removed by default during migration and that the customer assumes full ownership of the endpoint security agent lifecycle, plus adds guidance for re-establishing shared Transit Gateway connectivity. This is security-adjacent operational guidance (endpoint protection and network connectivity) rather than a fix for a specific vulnerability, so it is not tied to a concrete incident.

Evidence

+By default, AMS removes the Trend Micro agents from your instances and offboards the EPS stack during the transition. You select, deploy, and manage an endpoint security solution of your choice.

Diff

diff --git a/managedservices/latest/userguide/transition-to-accelerate.md b/managedservices/latest/userguide/transition-to-accelerate.md
index 0f38c54..300fa3b 100644
--- a//managedservices/latest/userguide/transition-to-accelerate.md
+++ b//managedservices/latest/userguide/transition-to-accelerate.md
@@ -44,0 +45,2 @@ This guide helps you understand what is changing during the transition and what
+  * [Connecting a new VPC to the shared Transit Gateway](./connect-vpc-tgw.html)
+
@@ -129 +131 @@ In AMS Advanced, AMS deploys and manages Trend Micro endpoint security on your E
-As part of the transition, you choose your endpoint security path: continue with Trend Micro by moving to Vision One (a fully SaaS platform hosted by Trend Micro that eliminates the on-premises DSM infrastructure), or move to a different security vendor of your choice. Either way, you take ownership of the agent lifecycle with your chosen vendor—deploying agents, managing licenses, and configuring activation. This must be completed before the transition to Accelerate, because AMS offboards the EPS stack during migration and the boot scripts will no longer install or activate the Trend Micro agent on instance launch.
+As part of the transition, AMS removes the Trend Micro agents and offboards the EPS stack (including DSM infrastructure) from your accounts. The boot scripts will no longer install or activate the Trend Micro agent on instance launch. If you want to continue with Trend Micro, you can opt in to a migration to Vision One before offboarding. For more information, see Option 2. Either way, you take ownership of the agent lifecycle going forward with your chosen vendor: deploying agents, managing licenses, and configuring activation.
@@ -131 +133 @@ As part of the transition, you choose your endpoint security path: continue with
-###### Option 1: Continue with Trend Micro Vision One (SaaS)
+###### Option 1: Use your own endpoint security solution (default)
@@ -133 +135 @@ As part of the transition, you choose your endpoint security path: continue with
-Vision One is the cloud-native Trend Micro platform that integrates with AWS Security Hub. AMS assists with migrating you from your current platform (DSM or Cloud One) to Vision One before offboarding. Once on Vision One, you work directly with Trend Micro for agent lifecycle management. If you currently use DSM, the migration path is sequential: DSM to Cloud One, then Cloud One to Vision One. With Vision One, security alerts are sent to AWS Security Hub. Customers who also onboard to AWS Security Incident Response (SIR) get continued event monitoring and incident response through AWS.
+By default, AMS removes the Trend Micro agents from your instances and offboards the EPS stack during the transition. You select, deploy, and manage an endpoint security solution of your choice. You're responsible for standing up and running your chosen vendor. You can optionally integrate your chosen solution with AWS Security Hub for SIR coverage. No action is required from you for this option to proceed.
@@ -135 +137 @@ Vision One is the cloud-native Trend Micro platform that integrates with AWS Sec
-###### Option 2: Use a different endpoint security solution
+###### Option 2: Continue with Trend Micro Vision One (SaaS)
@@ -137 +139 @@ Vision One is the cloud-native Trend Micro platform that integrates with AWS Sec
-You select, deploy, and manage an endpoint security solution of your choice. AMS removes the Trend Micro agents from your instances and offboards the EPS stack. You're responsible for standing up and running your chosen vendor. You can optionally integrate your chosen solution with AWS Security Hub for SIR coverage.
+If you want to continue with Trend Micro, notify your CSDM or CA so AMS can assist with migrating you from your current platform (DSM or Cloud One) to Vision One before offboarding. Vision One is the cloud-native Trend Micro platform that integrates with AWS Security Hub. After you move to Vision One, you work directly with Trend Micro for agent lifecycle management. If you currently use DSM, the migration path is sequential: DSM to Cloud One, then Cloud One to Vision One. With Vision One, security alerts are sent to AWS Security Hub. Customers who also onboard to AWS Security Incident Response (SIR) get continued event monitoring and incident response through AWS.
@@ -294 +296 @@ After you enable AWS Control Tower, you can choose which controls to apply from
-AWS Control Tower doesn't recreate MALZ networking. Your networking account transitions to Accelerate just like other application accounts. Account Factory can create a standalone VPC in a new account, but it doesn't attach accounts to a transit gateway or set up shared egress and shared-services connectivity the way MALZ did. Cross-account networking remains your responsibility.
+AWS Control Tower doesn't recreate MALZ networking. Your networking account transitions to Accelerate just like other application accounts. Account Factory can create a standalone VPC in a new account, but it doesn't attach accounts to a Transit Gateway or set up shared egress and shared-services connectivity the way MALZ did. Cross-account networking remains your responsibility. You can optionally follow the steps in [Connecting a new VPC to the shared Transit Gateway](./connect-vpc-tgw.html) to set up Transit Gateway for newly created accounts.