The Boundary AWS EBS plugin collects information on AWS Elastic Block Store using the CloudWatch API.
The plugin requires Python 2.6 or later, as well as the Boto Python library. Click here for Boto installation instructions.
The plugin reports all EBS metrics reported by CloudWatch. For a full list of these metrics and their descriptions, see this AWS documentation article.
Note: CloudWatch will not supply values for metrics that do not have any activity. For example, the VolumeReadBytes metric will not be supplied for periods where the volume was idle. In this case, you will see holes in the Boundary graph. This is normal and a product of how CloudWatch works.
Note: CloudWatch reports EBS metrics in 60 second periods. You will only see data appear in Boundary every 60 seconds for the preceding 60 seconds. This is normal and a product of how CloudWatch works.
- Login into Boundary Premium
- Display the settings dialog by clicking on the settings icon:
- Click on the Plugins in the settings dialog.
- Locate the aws_ebs plugin item and click on the Install button.
- A confirmation dialog is displayed indicating the plugin was installed successfully, along with the metrics and the dashboards.
- Click on the OK button to dismiss the dialog.
- Login into Boundary Premium
- Display the settings dialog by clicking on the settings icon:
- Click on the Plugins in the settings dialog which lists the installed plugins.
- Locate the aws_ebs plugin and click on the item, which then displays the uninstall dialog.
- Click on the Uninstall button which displays a confirmation dialog along with the details on what metrics and dashboards will be removed.
- Click on the Uninstall button to perfom the actual uninstall and then click on the Close button to dismiss the dialog.
Once the EBS plugin is installed, metric collection requires that a relay is installed on the target system. Instructions on how to install a relay for Linux/Unix can found here, and for Windows here.
Before the plugin will collect metrics, you must provide it with a valid AWS Access Key ID and Secret Access Key. Click here for more information on where to find/generate these keys. The keys you generate should be for a user with access to both CloudWatch and EBS.
General operations for plugins are described in this article.