Install the agent on Amazon EC2 and WorkSpaces
Read this page if you want to protect existing Amazon EC2 instances and Amazon WorkSpaces with Deep Security.
If instead you want to:
- launch new Amazon EC2 instances and Amazon WorkSpaces with the agent 'baked in', see Bake the agent into your AMI or WorkSpace bundle.
- protect Amazon WorkSpaces after already protecting your Amazon EC2 instances, see instead Protect Amazon WorkSpaces if you already added your AWS account.
To protect your existing Amazon EC2 instances and Amazon WorkSpaces with Deep Security, follow these steps:
- Add your AWS accounts to Deep Security Manager
- Configure the activation type
- Open ports
- Deploy agents to your Amazon EC2 instances and WorkSpaces
- Verify that the agent was installed and activated properly
- Assign a policy
You'll need to add your AWS account or accounts to Deep Security Manager. These AWS accounts contain the Amazon EC2 instances and Amazon WorkSpaces that you want to protect with Deep Security.
Follow the instructions in Add AWS cloud accounts to add your AWS accounts.
After adding your AWS accounts:
- your existing Amazon EC2 instances and Amazon WorkSpaces appear in Deep Security Manager. If no agent is installed on them, they appear with a Status of Unmanaged (Unknown) and a grey dot next to them. If an agent was already installed, they appear with a Status of Managed (Online) and green dot next to them.
- 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.
'Activation' is the process of registering an agent with a manager. You'll need to indicate whether you'll allow agent-initiated activation. If not, only manager-initiated activation is allowed.
- Log in to Deep Security Manager.
- Click Administration at the top.
- On the left, click System Settings.
- In the main pane, make sure the Agents tab is selected.
- Select or deselect Allow Agent-Initiated Activation, noting that:
- Agent-initiated activation does not require you to open up inbound ports to your Amazon EC2 instances or Amazon WorkSpaces, while manager-initiated activation does.
- If agent-initiated activation is enabled, manager-initiated activation continues to work.
- If you selected Allow Agent-Initiated Activation, also select Reactivate cloned Agents, and Enable Reactivate unknown Agents. See Agent settings for more information.
- Click Save.
- If you're using Amazon WorkSpaces, and you didn't allow agent-initiated activation, manually assign an elastic IP address to each WorkSpace now, before proceeding with further steps on this page. This gives each Amazon WorkSpace a public IP that can be contacted by other computers. This is not required for EC2 instances because they already use public IP addresses.
You'll need to make sure that the necessary ports are open to your Amazon EC2 instances or Amazon WorkSpaces.
To open ports:
- Open ports to your Amazon EC2 instances, as follows:
- Open ports to your Amazon WorkSpaces, as follows:
- Go to the firewall software that is protecting your Amazon WorkSpaces, and open the ports listed above.
You have now opened the necessary ports so that Deep Security Agent and Deep Security Manager can communicate.
- agent-to-manager communication requires you to open the outbound TCP port (443 or 80, by default), while
- manager-to-agent communication requires you to open an inbound TCP port (4118).
- If you enabled Allow Agent-Initiated Activation, you'll need to open the outbound TCP port (443 or 80, by default)
- If you disabled Allow Agent-Initiated Activation, you'll need to open the inbound TCP port of 4118.
You'll need to deploy agents onto your Amazon EC2 instances and Amazon WorkSpaces. Below are a couple of options.
- Option 1: Use a deployment script to install, activate, and assign a policy
- Option 2: Manually install and activate
Use Option 2 if you only need to deploy agents to a few EC2 instances and Amazon WorkSpaces.
- Get the Deep Security Agent software, copy it to the Amazon EC2 instance or Amazon WorkSpace, and then install it. For details, see Get Deep Security Agent software, and Manually install the Deep Security Agent.
- Activate the agent. You can do so on the agent (if agent-initiated activation was enabled) or on the Deep Security Manager. For details, see Activate the agent
Use Option 1 if you need to deploy agents to many Amazon EC2 instances and Amazon WorkSpaces.
With this option, you must run a deployment script on the Amazon EC2 instances or Amazon WorkSpaces. The script installs and activates the agent and then assigns a policy. See Use deployment scripts to add and protect computers for details.
You have now installed and activated Deep Security Agent on an Amazon EC2 instance or Amazon WorkSpace. A policy may or may not have been assigned, depending on the option you chose. If you chose Option 1 (you used a deployment script), a policy was assigned to the agent during activation. If you chose Option 2 (you manually installed and activated the agent), then no policy has been assigned, and you will need to assign one following the instructions further down on this page.
You should verify that your agent was installed and activated properly.
- Log in to Deep Security Manager.
- Click Computers at the top.
- On the navigation pane on the left, make sure your Amazon EC2 instance or Amazon WorkSpace appears under Computers > your_AWS_account > your_region . (Look for WorkSpaces in a WorkSpaces sub-node.)
- In the main pane, make sure your Amazon EC2 instances or Amazon WorkSpaces appear with a Status of Managed (Online) and a green dot next to them.
Skip this step if you ran a deployment script to install and activate the agent. The script already assigned a policy so no further action is required.
If you installed and activated the agent manually, you must assign a policy to the agent. Assigning the policy sends the necessary protection modules to the agent so that your computer is protected.
To assign a policy, see Assign a policy to a computer.
After assigning a policy, your Amazon EC2 instance or Amazon WorkSpace is now protected.