Agent/Appliance Initiated does not require you to open inbound ports on the Amazon EC2 instance or Amazon WorkSpace, while Bidirectional and Manager-Initiated do.Set the communication direction following the instructions in Configure communication directionality.You'll need to set the communication direction: either agent-initiated, manager-initiated, or bi-directional. any new Amazon EC2 instances or Amazon WorkSpaces that you launch through AWS under this AWS account are auto-detected by Deep Security Manager and displayed in the list of computers.If an agent was already installed, they appear with a Status of Managed (Online) and green dot next to them. If no agent is installed on them, they appear with a Status of Unmanaged (Unknown) and a grey dot next to them. your existing Amazon EC2 instances and Amazon WorkSpaces appear in Deep Security Manager.These AWS accounts contain the Amazon EC2 instances and Amazon WorkSpaces that you want to protect with Deep Security.įollow the instructions in Add AWS cloud accounts to add your AWS accounts. You'll need to add your AWS account or accounts to Deep Security Manager. Verify that the agent was installed and activated properlyĪdd your AWS accounts to Deep Security Manager.Deploy agents to your Amazon EC2 instances and WorkSpaces.Add your AWS accounts to Deep Security Manager.To protect your existing Amazon EC2 instances and Amazon WorkSpaces with Deep Security, follow these steps: protect Amazon WorkSpaces after already protecting your Amazon EC2 instances, see instead Protect Amazon WorkSpaces if you already added your AWS account.
0 Comments
Leave a Reply. |