Available solutions

AWS by HTTP
AWS Cost Explorer by HTTP
3rd party solutions

This template is for Zabbix version: 6.4

Also available for: 6.2 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cloud/AWS/aws_http?at=release/6.4

AWS by HTTP

Overview

This template is designed for the effortless deployment of AWS monitoring by Zabbix via HTTP and doesn't require any external scripts.

Requirements

Zabbix version: 6.4 and higher.

Tested versions

This template has been tested on:

AWS by HTTP

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.

Add the following required permissions to your Zabbix IAM policy in order to collect metrics.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudwatch:DescribeAlarms",
                "cloudwatch:GetMetricData",
                "ec2:DescribeInstances",
                "ec2:DescribeVolumes",
                "ec2:DescribeRegions",
                "rds:DescribeEvents",
                "rds:DescribeDBInstances",
                "ecs:DescribeClusters",
                "ecs:ListServices",
                "ecs:ListTasks",
                "ecs:ListClusters",
                "s3:ListAllMyBuckets",
                "s3:GetBucketLocation",
                "elasticloadbalancing:DescribeLoadBalancers",
                "elasticloadbalancing:DescribeTargetGroups",
                "ec2:DescribeSecurityGroups"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

If you are using role-based authorization, add the appropriate permissions:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "iam:PassRole",
            "Resource": "arn:aws:iam::<<--account-id-->>:role/<<--role_name-->>"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "cloudwatch:DescribeAlarms",
                "cloudwatch:GetMetricData",
                "ec2:DescribeInstances",
                "ec2:DescribeVolumes",
                "ec2:DescribeRegions",
                "rds:DescribeEvents",
                "rds:DescribeDBInstances",
                "ecs:DescribeClusters",
                "ecs:ListServices",
                "ecs:ListTasks",
                "ecs:ListClusters",
                "s3:ListAllMyBuckets",
                "s3:GetBucketLocation",
                "ec2:AssociateIamInstanceProfile",
                "ec2:ReplaceIamInstanceProfileAssociation",
                "elasticloadbalancing:DescribeLoadBalancers",
                "elasticloadbalancing:DescribeTargetGroups",
                "ec2:DescribeSecurityGroups"
            ],
            "Resource": "*"
        }
    ]
}

To gather Request metrics, enable Requests metrics on your Amazon S3 buckets from the AWS console.

Set macros "{$AWS.AUTH_TYPE}". Possible values: role_base, access_key.

If you are using access key-based authorization, set the following macros {$AWS.ACCESS.KEY.ID}, {$AWS.SECRET.ACCESS.KEY}.

For more information about managing access keys, see official documentation.

Refer to the Macros section for a list of macros used for LLD filters.

Additional information about the metrics and used API methods:

Macros used

Name	Description	Default
{$AWS.DATA.TIMEOUT}	A response timeout for an API.	`60s`
{$AWS.PROXY}	Sets HTTP proxy value. If this macro is empty then no proxy is used.
{$AWS.ACCESS.KEY.ID}	Access key ID.
{$AWS.SECRET.ACCESS.KEY}	Secret access key.
{$AWS.AUTH_TYPE}	Authorization method. Possible values: role_base, access_key.	`access_key`
{$AWS.EC2.LLD.FILTER.NAME.MATCHES}	Filter of discoverable EC2 instances by namespace.	`.*`
{$AWS.EC2.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered EC2 instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.EC2.LLD.FILTER.REGION.MATCHES}	Filter of discoverable EC2 instances by region.	`.*`
{$AWS.EC2.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered EC2 instances by region.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.NAME.MATCHES}	Filter of discoverable ECS clusters by name.	`.*`
{$AWS.ECS.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered ECS clusters by name.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.STATUS.MATCHES}	Filter of discoverable ECS clusters by status.	`ACTIVE`
{$AWS.ECS.LLD.FILTER.STATUS.NOT_MATCHES}	Filter to exclude discovered ECS clusters by status.	`CHANGE_IF_NEEDED`
{$AWS.S3.LLD.FILTER.NAME.MATCHES}	Filter of discoverable S3 buckets by namespace.	`.*`
{$AWS.S3.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered S3 buckets by namespace.	`CHANGE_IF_NEEDED`
{$AWS.RDS.LLD.FILTER.NAME.MATCHES}	Filter of discoverable RDS instances by namespace.	`.*`
{$AWS.RDS.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered RDS instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.RDS.LLD.FILTER.REGION.MATCHES}	Filter of discoverable RDS instances by region.	`.*`
{$AWS.RDS.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered RDS instances by region.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.REGION.MATCHES}	Filter of discoverable ECS clusters by region.	`.*`
{$AWS.ECS.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered ECS clusters by region.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.NAME.MATCHES}	Filter of discoverable ELB load balancer by name.	`.*`
{$AWS.ELB.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by name.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.REGION.MATCHES}	Filter of discoverable ELB load balancer by region.	`.*`
{$AWS.ELB.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by region.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.STATE.MATCHES}	Filter of discoverable ELB load balancer by status.	`active`
{$AWS.ELB.LLD.FILTER.STATE.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by status.	`CHANGE_IF_NEEDED`

LLD rule S3 buckets discovery

Name	Description	Type	Key and additional info
S3 buckets discovery	Get S3 bucket instances.	Script	aws.s3.discovery

LLD rule EC2 instances discovery

Name	Description	Type	Key and additional info
EC2 instances discovery	Get EC2 instances.	Script	aws.ec2.discovery

LLD rule RDS instances discovery

Name	Description	Type	Key and additional info
RDS instances discovery	Get RDS instances.	Script	aws.rds.discovery

LLD rule ECS clusters discovery

Name	Description	Type	Key and additional info
ECS clusters discovery	Get ECS clusters.	Script	aws.ecs.discovery

LLD rule ELB load balancers discovery

Name	Description	Type	Key and additional info
ELB load balancers discovery	Get ELB load balancers.	Script	aws.elb.discovery

Feedback

Please report any issues with the template at https://support.zabbix.com

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 6.2

Also available for: 6.4 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cloud/AWS/aws_http?at=release/6.2

AWS by HTTP

Overview

For Zabbix version: 6.2 and higher
The template to monitor AWS EC2, RDS and S3 instances by HTTP via Zabbix that works without any external scripts.

Setup

See Zabbix template operation for basic instructions.

Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.

Add the following required permissions to your Zabbix IAM policy in order to collect metrics.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudwatch:Describe*",
                "cloudwatch:Get*",
                "cloudwatch:List*",
                "ec2:Describe*",
                "rds:Describe*",
                "s3:ListAllMyBuckets",
                "s3:GetBucketLocation"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

To gather Request metrics, enable Requests metrics on your Amazon S3 buckets from the AWS console.

Set macros {$AWS.ACCESS.KEY.ID}, {$AWS.SECRET.ACCESS.KEY}, {$AWS.REGION}.

For more information about managing access keys, see official documentation.

Also, see the Macros section for a list of macros used in LLD filters.

Additional information about metrics and used API methods:

Zabbix configuration

No specific Zabbix configuration is required.

Macros used

Name	Description	Default
{$AWS.ACCESS.KEY.ID}	Access key ID.	``
{$AWS.EC2.LLD.FILTER.NAME.MATCHES}	Filter of discoverable EC2 instances by namespace.	`.*`
{$AWS.EC2.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered EC2 instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.RDS.LLD.FILTER.NAME.MATCHES}	Filter of discoverable RDS instances by namespace.	`.*`
{$AWS.RDS.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered RDS instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.REGION}	Amazon EC2 region code.	`us-west-1`
{$AWS.S3.LLD.FILTER.NAME.MATCHES}	Filter of discoverable S3 buckets by namespace.	`.*`
{$AWS.S3.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered S3 buckets by namespace.	`CHANGE_IF_NEEDED`
{$AWS.SECRET.ACCESS.KEY}	Secret access key.	``
{$AWS.PROXY}	Sets HTTP proxy value. If this macro is empty then no proxy is used.	``

Template links

There are no template links in this template.

Discovery rules

Name Description Type Key and additional info

EC2 instances discovery

Name	Description	Type	Key and additional info
EC2 instances discovery	Get EC2 instances.	SCRIPT	aws.ec2.discovery Filter: AND - {#AWS.EC2.INSTANCE.NAME} MATCHES_REGEX `{$AWS.EC2.LLD.FILTER.NAME.MATCHES}` - {#AWS.EC2.INSTANCE.NAME} NOT_MATCHES_REGEX `{$AWS.EC2.LLD.FILTER.NAME.NOT_MATCHES}`
RDS instances discovery	Get RDS instances.	SCRIPT	aws.rds.discovery Filter: AND - {#AWS.RDS.INSTANCE.ID} MATCHES_REGEX `{$AWS.RDS.LLD.FILTER.NAME.MATCHES}` - {#AWS.RDS.INSTANCE.ID} NOT_MATCHES_REGEX `{$AWS.RDS.LLD.FILTER.NAME.NOT_MATCHES}`
S3 buckets discovery	Get S3 bucket instances.	SCRIPT	aws.s3.discovery Filter: AND - {#AWS.S3.NAME} MATCHES_REGEX `{$AWS.S3.LLD.FILTER.NAME.MATCHES}` - {#AWS.S3.NAME} NOT_MATCHES_REGEX `{$AWS.S3.LLD.FILTER.NAME.NOT_MATCHES}`

Get EC2 instances.

SCRIPT

aws.ec2.discovery

Filter:

AND

- {#AWS.EC2.INSTANCE.NAME} MATCHES_REGEX {$AWS.EC2.LLD.FILTER.NAME.MATCHES}

- {#AWS.EC2.INSTANCE.NAME} NOT_MATCHES_REGEX {$AWS.EC2.LLD.FILTER.NAME.NOT_MATCHES}

RDS instances discovery

Get RDS instances.

SCRIPT

aws.rds.discovery

Filter:

AND

- {#AWS.RDS.INSTANCE.ID} MATCHES_REGEX {$AWS.RDS.LLD.FILTER.NAME.MATCHES}

- {#AWS.RDS.INSTANCE.ID} NOT_MATCHES_REGEX {$AWS.RDS.LLD.FILTER.NAME.NOT_MATCHES}

S3 buckets discovery

Get S3 bucket instances.

SCRIPT

aws.s3.discovery

Filter:

AND

- {#AWS.S3.NAME} MATCHES_REGEX {$AWS.S3.LLD.FILTER.NAME.MATCHES}

- {#AWS.S3.NAME} NOT_MATCHES_REGEX {$AWS.S3.LLD.FILTER.NAME.NOT_MATCHES}

Items collected

Group	Name	Description	Type	Key and additional info

Triggers

Name	Description	Expression	Severity	Dependencies and additional info

Feedback

Please report any issues with the template at https://support.zabbix.com

You can also provide feedback, discuss the template or ask for help with it at ZABBIX forums.

This template is for Zabbix version: 6.0

Also available for: 6.4 6.2

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cloud/AWS/aws_http?at=release/6.0

AWS by HTTP

Overview

This template is designed for the effortless deployment of AWS monitoring by Zabbix via HTTP and doesn't require any external scripts.

Requirements

Zabbix version: 6.0 and higher.

Tested versions

This template has been tested on:

AWS by HTTP

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.

Add the following required permissions to your Zabbix IAM policy in order to collect metrics.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "cloudwatch:DescribeAlarms",
                "cloudwatch:GetMetricData",
                "ec2:DescribeInstances",
                "ec2:DescribeVolumes",
                "ec2:DescribeRegions",
                "rds:DescribeEvents",
                "rds:DescribeDBInstances",
                "ecs:DescribeClusters",
                "ecs:ListServices",
                "ecs:ListTasks",
                "ecs:ListClusters",
                "s3:ListAllMyBuckets",
                "s3:GetBucketLocation",
                "elasticloadbalancing:DescribeLoadBalancers",
                "elasticloadbalancing:DescribeTargetGroups",
                "ec2:DescribeSecurityGroups"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

If you are using role-based authorization, add the appropriate permissions:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "iam:PassRole",
            "Resource": "arn:aws:iam::<<--account-id-->>:role/<<--role_name-->>"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "cloudwatch:DescribeAlarms",
                "cloudwatch:GetMetricData",
                "ec2:DescribeInstances",
                "ec2:DescribeVolumes",
                "ec2:DescribeRegions",
                "rds:DescribeEvents",
                "rds:DescribeDBInstances",
                "ecs:DescribeClusters",
                "ecs:ListServices",
                "ecs:ListTasks",
                "ecs:ListClusters",
                "s3:ListAllMyBuckets",
                "s3:GetBucketLocation",
                "ec2:AssociateIamInstanceProfile",
                "ec2:ReplaceIamInstanceProfileAssociation",
                "elasticloadbalancing:DescribeLoadBalancers",
                "elasticloadbalancing:DescribeTargetGroups",
                "ec2:DescribeSecurityGroups"
            ],
            "Resource": "*"
        }
    ]
}

To gather Request metrics, enable Requests metrics on your Amazon S3 buckets from the AWS console.

Set macros "{$AWS.AUTH_TYPE}". Possible values: role_base, access_key.

If you are using access key-based authorization, set the following macros {$AWS.ACCESS.KEY.ID}, {$AWS.SECRET.ACCESS.KEY}.

For more information about managing access keys, see official documentation.

Refer to the Macros section for a list of macros used for LLD filters.

Additional information about the metrics and used API methods:

Macros used

Name	Description	Default
{$AWS.DATA.TIMEOUT}	A response timeout for an API.	`60s`
{$AWS.PROXY}	Sets HTTP proxy value. If this macro is empty then no proxy is used.
{$AWS.ACCESS.KEY.ID}	Access key ID.
{$AWS.SECRET.ACCESS.KEY}	Secret access key.
{$AWS.AUTH_TYPE}	Authorization method. Possible values: role_base, access_key.	`access_key`
{$AWS.EC2.LLD.FILTER.NAME.MATCHES}	Filter of discoverable EC2 instances by namespace.	`.*`
{$AWS.EC2.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered EC2 instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.EC2.LLD.FILTER.REGION.MATCHES}	Filter of discoverable EC2 instances by region.	`.*`
{$AWS.EC2.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered EC2 instances by region.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.NAME.MATCHES}	Filter of discoverable ECS clusters by name.	`.*`
{$AWS.ECS.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered ECS clusters by name.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.STATUS.MATCHES}	Filter of discoverable ECS clusters by status.	`ACTIVE`
{$AWS.ECS.LLD.FILTER.STATUS.NOT_MATCHES}	Filter to exclude discovered ECS clusters by status.	`CHANGE_IF_NEEDED`
{$AWS.S3.LLD.FILTER.NAME.MATCHES}	Filter of discoverable S3 buckets by namespace.	`.*`
{$AWS.S3.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered S3 buckets by namespace.	`CHANGE_IF_NEEDED`
{$AWS.RDS.LLD.FILTER.NAME.MATCHES}	Filter of discoverable RDS instances by namespace.	`.*`
{$AWS.RDS.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered RDS instances by namespace.	`CHANGE_IF_NEEDED`
{$AWS.RDS.LLD.FILTER.REGION.MATCHES}	Filter of discoverable RDS instances by region.	`.*`
{$AWS.RDS.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered RDS instances by region.	`CHANGE_IF_NEEDED`
{$AWS.ECS.LLD.FILTER.REGION.MATCHES}	Filter of discoverable ECS clusters by region.	`.*`
{$AWS.ECS.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered ECS clusters by region.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.NAME.MATCHES}	Filter of discoverable ELB load balancer by name.	`.*`
{$AWS.ELB.LLD.FILTER.NAME.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by name.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.REGION.MATCHES}	Filter of discoverable ELB load balancer by region.	`.*`
{$AWS.ELB.LLD.FILTER.REGION.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by region.	`CHANGE_IF_NEEDED`
{$AWS.ELB.LLD.FILTER.STATE.MATCHES}	Filter of discoverable ELB load balancer by status.	`active`
{$AWS.ELB.LLD.FILTER.STATE.NOT_MATCHES}	Filter to exclude discovered ELB load balancer by status.	`CHANGE_IF_NEEDED`

LLD rule S3 buckets discovery

Name	Description	Type	Key and additional info
S3 buckets discovery	Get S3 bucket instances.	Script	aws.s3.discovery

LLD rule EC2 instances discovery

Name	Description	Type	Key and additional info
EC2 instances discovery	Get EC2 instances.	Script	aws.ec2.discovery

LLD rule RDS instances discovery

Name	Description	Type	Key and additional info
RDS instances discovery	Get RDS instances.	Script	aws.rds.discovery

LLD rule ECS clusters discovery

Name	Description	Type	Key and additional info
ECS clusters discovery	Get ECS clusters.	Script	aws.ecs.discovery

LLD rule ELB load balancers discovery

Name	Description	Type	Key and additional info
ELB load balancers discovery	Get ELB load balancers.	Script	aws.elb.discovery

Feedback

Please report any issues with the template at https://support.zabbix.com

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 6.4

Also available for: 6.0

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cloud/AWS/aws_cost_http?at=release/6.4

AWS Cost Explorer by HTTP

Overview

The template to monitor AWS Cost Explorer by HTTP via Zabbix, which works without any external scripts. Most of the metrics are collected in one go, thanks to Zabbix bulk data collection. NOTE This template uses the Cost Explorer API calls to list and retrieve metrics. For more information, please refer to the Cost Explorer pricing page.

Requirements

Zabbix version: 6.4 and higher.

Tested versions

This template has been tested on:

AWS by HTTP

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.

IAM policies for AWS Cost Management

Add the following required permissions to your Zabbix IAM policy in order to collect metrics.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "ce:GetDimensionValues",
                "ce:GetCostAndUsage"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

If you are using role-based authorization, add the appropriate permissions:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "iam:PassRole",
            "Resource": "arn:aws:iam::<<--account-id-->>:role/<<--role_name-->>"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "ce:GetDimensionValues",
                "ce:GetCostAndUsage",
                "ec2:AssociateIamInstanceProfile",
                "ec2:ReplaceIamInstanceProfileAssociation"
            ],
            "Resource": "*"
        }
    ]
}

Set macros "{$AWS.AUTH_TYPE}". Possible values: role_base, access_key.

If you are using access key-based authorization, set the following macros {$AWS.ACCESS.KEY.ID}, {$AWS.SECRET.ACCESS.KEY}.

For more information about managing access keys, see the official documentation.

Also, see the Macros section for a list of macros used in LLD filters.

Additional information about metrics and used API methods:

Describe AWS Cost Explore API actions

Macros used

Name	Description	Default
{$AWS.PROXY}	Sets HTTP proxy value. If this macro is empty, then no proxy is used.
{$AWS.ACCESS.KEY.ID}	Access key ID.
{$AWS.SECRET.ACCESS.KEY}	Secret access key.
{$AWS.BILLING.REGION}	Amazon Billing region code.	`us-east-1`
{$AWS.AUTH_TYPE}	Authorization method. Possible values: role_base, access_key.	`access_key`
{$AWS.BILLING.MONTH}	Months to get historical data from AWS Cost Explore API, no more than 12 months.	`11`
{$AWS.BILLING.LLD.FILTER.SERVICE.MATCHES}	Filter of discoverable discovered billing service by name.	`.*`
{$AWS.BILLING.LLD.FILTER.SERVICE.NOT_MATCHES}	Filter to exclude discovered billing service by name.	`CHANGE_IF_NEEDED`

Items

Name	Description	Type	Key and additional info
AWS Cost: Get monthly costs		Script	aws.get.monthly.costs Preprocessing Check for not supported value ⛔️Custom on fail: Discard value
AWS Cost: Get daily costs	Get raw data on the daily costs by service	Script	aws.get.daily.costs Preprocessing Check for not supported value ⛔️Custom on fail: Discard value

Name

Description

Type

Key and additional info

AWS Cost: Get monthly costs

Script

aws.get.monthly.costs

Preprocessing

Check for not supported value
⛔️Custom on fail: Discard value

AWS Cost: Get daily costs

Get raw data on the daily costs by service

Script

aws.get.daily.costs

Preprocessing

Check for not supported value
⛔️Custom on fail: Discard value

LLD rule AWS daily costs by services discovery

Name Description Type Key and additional info

AWS daily costs by services discovery

Name	Description	Type	Key and additional info
AWS daily costs by services discovery	Discovery of daily blended costs by services.	Dependent item	aws.daily.services.costs.discovery Preprocessing JSON Path: `$..Groups.first()`

Discovery of daily blended costs by services.

Dependent item

aws.daily.services.costs.discovery

Preprocessing

JSON Path: $..Groups.first()

Item prototypes for AWS daily costs by services discovery

Name Description Type Key and additional info

AWS Cost: Service [{#AWS.BILLING.SERVICE.NAME}]: Blended daily cost

Name	Description	Type	Key and additional info
AWS Cost: Service [{#AWS.BILLING.SERVICE.NAME}]: Blended daily cost	The daily blended cost of the {#AWS.BILLING.SERVICE.NAME} service for the previous day.	Dependent item	aws.daily.service.cost["{#AWS.BILLING.SERVICE.NAME}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value

The daily blended cost of the {#AWS.BILLING.SERVICE.NAME} service for the previous day.

Dependent item

aws.daily.service.cost["{#AWS.BILLING.SERVICE.NAME}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value

LLD rule AWS monthly costs by services discovery

Name Description Type Key and additional info

AWS monthly costs by services discovery

Name	Description	Type	Key and additional info
AWS monthly costs by services discovery	Discovery of monthly costs by services.	Dependent item	aws.cost.service.monthly.discovery Preprocessing JSON Path: `$.monthly_service_costs`

Discovery of monthly costs by services.

Dependent item

aws.cost.service.monthly.discovery

Preprocessing

JSON Path: $.monthly_service_costs

Item prototypes for AWS monthly costs by services discovery

Name Description Type Key and additional info

AWS Cost: [{#AWS.BILLING.SERVICE.NAME}]: Month [{#AWS.BILLING.MONTH}] Blended cost

Name	Description	Type	Key and additional info
AWS Cost: [{#AWS.BILLING.SERVICE.NAME}]: Month [{#AWS.BILLING.MONTH}] Blended cost	The monthly cost by service {#AWS.BILLING.SERVICE.NAME}.	Dependent item	aws.monthly.service.cost["{#AWS.BILLING.SERVICE.NAME}", "{#AWS.BILLING.MONTH}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value

The monthly cost by service {#AWS.BILLING.SERVICE.NAME}.

Dependent item

aws.monthly.service.cost["{#AWS.BILLING.SERVICE.NAME}", "{#AWS.BILLING.MONTH}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value
JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value

LLD rule AWS monthly costs discovery

Name Description Type Key and additional info

AWS monthly costs discovery

Name	Description	Type	Key and additional info
AWS monthly costs discovery	Discovery of monthly costs.	Dependent item	aws.monthly.cost.discovery Preprocessing JSON Path: `$.monthly_costs`

Discovery of monthly costs.

Dependent item

aws.monthly.cost.discovery

Preprocessing

JSON Path: $.monthly_costs

Item prototypes for AWS monthly costs discovery

Name Description Type Key and additional info

AWS Cost: [{#AWS.BILLING.MONTH}]: Blended cost per month

Name	Description	Type	Key and additional info
AWS Cost: [{#AWS.BILLING.MONTH}]: Blended cost per month	The blended cost by month {#AWS.BILLING.MONTH}.	Dependent item	aws.monthly.cost["{#AWS.BILLING.MONTH}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value Discard unchanged with heartbeat: `3h`

The blended cost by month {#AWS.BILLING.MONTH}.

Dependent item

aws.monthly.cost["{#AWS.BILLING.MONTH}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value
Discard unchanged with heartbeat: 3h

Feedback

Please report any issues with the template at https://support.zabbix.com

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

This template is for Zabbix version: 6.0

Also available for: 6.4

Source: https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/cloud/AWS/aws_cost_http?at=release/6.0

AWS Cost Explorer by HTTP

Overview

Requirements

Zabbix version: 6.0 and higher.

Tested versions

This template has been tested on:

AWS by HTTP

Configuration

Zabbix should be configured according to the instructions in the Templates out of the box section.

Setup

Before using the template, you need to create an IAM policy for the Zabbix role in your AWS account with the necessary permissions.

IAM policies for AWS Cost Management

Add the following required permissions to your Zabbix IAM policy in order to collect metrics.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "ce:GetDimensionValues",
                "ce:GetCostAndUsage"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

If you are using role-based authorization, add the appropriate permissions:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "iam:PassRole",
            "Resource": "arn:aws:iam::<<--account-id-->>:role/<<--role_name-->>"
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": [
                "ce:GetDimensionValues",
                "ce:GetCostAndUsage",
                "ec2:AssociateIamInstanceProfile",
                "ec2:ReplaceIamInstanceProfileAssociation"
            ],
            "Resource": "*"
        }
    ]
}

Set macros "{$AWS.AUTH_TYPE}". Possible values: role_base, access_key.

If you are using access key-based authorization, set the following macros {$AWS.ACCESS.KEY.ID}, {$AWS.SECRET.ACCESS.KEY}.

For more information about managing access keys, see the official documentation.

Also, see the Macros section for a list of macros used in LLD filters.

Additional information about metrics and used API methods:

Describe AWS Cost Explore API actions

Macros used

Name	Description	Default
{$AWS.PROXY}	Sets HTTP proxy value. If this macro is empty, then no proxy is used.
{$AWS.ACCESS.KEY.ID}	Access key ID.
{$AWS.SECRET.ACCESS.KEY}	Secret access key.
{$AWS.BILLING.REGION}	Amazon Billing region code.	`us-east-1`
{$AWS.AUTH_TYPE}	Authorization method. Possible values: role_base, access_key.	`access_key`
{$AWS.BILLING.MONTH}	Months to get historical data from AWS Cost Explore API, no more than 12 months.	`11`
{$AWS.BILLING.LLD.FILTER.SERVICE.MATCHES}	Filter of discoverable discovered billing service by name.	`.*`
{$AWS.BILLING.LLD.FILTER.SERVICE.NOT_MATCHES}	Filter to exclude discovered billing service by name.	`CHANGE_IF_NEEDED`

Items

Name	Description	Type	Key and additional info
AWS Cost: Get monthly costs		Script	aws.get.monthly.costs Preprocessing Check for not supported value ⛔️Custom on fail: Discard value
AWS Cost: Get daily costs	Get raw data on the daily costs by service	Script	aws.get.daily.costs Preprocessing Check for not supported value ⛔️Custom on fail: Discard value

Name

Description

Type

Key and additional info

AWS Cost: Get monthly costs

Script

aws.get.monthly.costs

Preprocessing

Check for not supported value
⛔️Custom on fail: Discard value

AWS Cost: Get daily costs

Get raw data on the daily costs by service

Script

aws.get.daily.costs

Preprocessing

Check for not supported value
⛔️Custom on fail: Discard value

LLD rule AWS daily costs by services discovery

Name Description Type Key and additional info

AWS daily costs by services discovery

Name	Description	Type	Key and additional info
AWS daily costs by services discovery	Discovery of daily blended costs by services.	Dependent item	aws.daily.services.costs.discovery Preprocessing JSON Path: `$..Groups.first()`

Discovery of daily blended costs by services.

Dependent item

aws.daily.services.costs.discovery

Preprocessing

JSON Path: $..Groups.first()

Item prototypes for AWS daily costs by services discovery

Name Description Type Key and additional info

AWS Cost: Service [{#AWS.BILLING.SERVICE.NAME}]: Blended daily cost

Name	Description	Type	Key and additional info
AWS Cost: Service [{#AWS.BILLING.SERVICE.NAME}]: Blended daily cost	The daily blended cost of the {#AWS.BILLING.SERVICE.NAME} service for the previous day.	Dependent item	aws.daily.service.cost["{#AWS.BILLING.SERVICE.NAME}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value

The daily blended cost of the {#AWS.BILLING.SERVICE.NAME} service for the previous day.

Dependent item

aws.daily.service.cost["{#AWS.BILLING.SERVICE.NAME}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value

LLD rule AWS monthly costs by services discovery

Name Description Type Key and additional info

AWS monthly costs by services discovery

Name	Description	Type	Key and additional info
AWS monthly costs by services discovery	Discovery of monthly costs by services.	Dependent item	aws.cost.service.monthly.discovery Preprocessing JSON Path: `$.monthly_service_costs`

Discovery of monthly costs by services.

Dependent item

aws.cost.service.monthly.discovery

Preprocessing

JSON Path: $.monthly_service_costs

Item prototypes for AWS monthly costs by services discovery

Name Description Type Key and additional info

AWS Cost: [{#AWS.BILLING.SERVICE.NAME}]: Month [{#AWS.BILLING.MONTH}] Blended cost

Name	Description	Type	Key and additional info
AWS Cost: [{#AWS.BILLING.SERVICE.NAME}]: Month [{#AWS.BILLING.MONTH}] Blended cost	The monthly cost by service {#AWS.BILLING.SERVICE.NAME}.	Dependent item	aws.monthly.service.cost["{#AWS.BILLING.SERVICE.NAME}", "{#AWS.BILLING.MONTH}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value

The monthly cost by service {#AWS.BILLING.SERVICE.NAME}.

Dependent item

aws.monthly.service.cost["{#AWS.BILLING.SERVICE.NAME}", "{#AWS.BILLING.MONTH}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value
JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value

LLD rule AWS monthly costs discovery

Name Description Type Key and additional info

AWS monthly costs discovery

Name	Description	Type	Key and additional info
AWS monthly costs discovery	Discovery of monthly costs.	Dependent item	aws.monthly.cost.discovery Preprocessing JSON Path: `$.monthly_costs`

Discovery of monthly costs.

Dependent item

aws.monthly.cost.discovery

Preprocessing

JSON Path: $.monthly_costs

Item prototypes for AWS monthly costs discovery

Name Description Type Key and additional info

AWS Cost: [{#AWS.BILLING.MONTH}]: Blended cost per month

Name	Description	Type	Key and additional info
AWS Cost: [{#AWS.BILLING.MONTH}]: Blended cost per month	The blended cost by month {#AWS.BILLING.MONTH}.	Dependent item	aws.monthly.cost["{#AWS.BILLING.MONTH}"] Preprocessing JSON Path: `The text is too long. Please see the template.` ⛔️Custom on fail: Discard value Discard unchanged with heartbeat: `3h`

The blended cost by month {#AWS.BILLING.MONTH}.

Dependent item

aws.monthly.cost["{#AWS.BILLING.MONTH}"]

Preprocessing

JSON Path: The text is too long. Please see the template.
⛔️Custom on fail: Discard value
Discard unchanged with heartbeat: 3h

Feedback

Please report any issues with the template at https://support.zabbix.com

You can also provide feedback, discuss the template, or ask for help at ZABBIX forums

Link	Source	Compatibility	Type, Technology	Created Updated	Rating
AWS CloudWatch via Docker Wrapper Repository for access to Cloudwatch via API REST using AWS-SDK + NodeJS Wrapper. The templatre only use HTTP Agent to recolect all metrics from AWS Cloudwatch.Git Repo template_aws_cloudwatch_via_docker_wrapper_with_http_agent	GitHub Community Templates	5.0+
ZAWS Zabbix AWS monitoring template with autoregistreation for EC2 and ELB intances github.com/ike-dai/zaws []	GitHub 50		Externalscripts, Templates Go	2016-02-02 1 y	Popular
Zabbix AWS Monitoring Templates This template collection is for effective monitoring AWS(Amazon Web Services) with Zabbix. github.com/tech-sketch/zabbix_aws_template []	GitHub 49		Externalscripts, Templates Python, Bash	2016-05-19 12 m	Popular
AWS monitoring using Zabbix and Chef automation POC for AWS monitoring using Zabbix and Chef automation. This is an usable proof of concept on how to manage an efficient capacity planning (do more with less) and monitoring for cloud computing over Amazon's AWS installations and using Zabbix SIA's monitoring tool and Opscode's Chef automation tool github.com/lorieri/zabbix []	GitHub 43		Externalscripts, Templates Chef, Ruby	2011-09-09 8 m	Popular
Check AWS resource status github.com/allenta/zabbix-aws-status []	GitHub 7		Externalscrips Python	2016-10-03 8 m
Autoscale AWS instances in Zabbix Auto(Up-)Scaled hosts can be added to Zabbix OOTB, using AutoRegistration. However, when scaling down, Zabbix should be notified to avoid triggering alerts. This is where aws-autoscale-zabbix (AAZ) comes in. AAZ can receive AWS SNS messages via HTTP(S) and will remove (delete or disable) hosts from Zabbix ... github.com/schnoddelbotz/aws-autoscale-zabbix []	GitHub 7		Daemon Go	2017-01-02 2 y
Remove terminated AWS EC2 instances from Zabbix This script checks availability of AWS EC2 instances in Zabbix, and if they do not exist in default AWS region (because of termination for ex.), they will be removed from Zabbix. github.com/vensder/remove-ec2-from-zabbix	GitHub 6		Container Docker, Jenkins	2017-11-30 2 y
zabbix-aws-monitoring using discovery (no template) This python module provides Zabbix monitoring support for AWS resources. github.com/digiapulssi/zabbix-aws-monitoring []	GitHub 6		Agent Python	2018-05-23 11 m
Zabbix AWS SES Notification Script Script for zabbix send e-mails notifications using AWS SES. github.com/rsgfernandes/zabbix-ses []	GitHub 5		Externalscripts Bash	2014-12-02 6 y
Forward CloudWatch logs to Zabbix with Lambda function This is AWS Lambda function to route CloudWatch Logs log events to Zabbix. github.com/yokota-shinsuke/aws-lambda-cloudwatchlogs-to-zabbix	GitHub 4		AWS Lambda function AWS Lambda	2015-06-14 2 y
AWS SQS Template for Zabbix The SQS Zabbix Template github.com/julienlevasseur/zabbix_sqs_template []	GitHub 4		Externalscripts, Templates Python	2017-06-28 12 m
aws-cloudwatch-tool (incomplete, no templates, not updated) Amazon CloudWatch query tool is a script that can be used with Zabbix or any other monitoring tool to get values from AWS Cloudwatch. github.com/rstefanx/aws-cloudwatch-tool []	GitHub 1		Externalsscripts Python	2014-07-14 7 y

See all Zabbix community templates

Zabbix + AWS

AWS

Available solutions

AWS by HTTP

Overview

Requirements

Tested versions

Configuration

Setup

Macros used

LLD rule S3 buckets discovery

LLD rule EC2 instances discovery

LLD rule RDS instances discovery

LLD rule ECS clusters discovery

LLD rule ELB load balancers discovery

Feedback

AWS by HTTP

Overview

Setup

Zabbix configuration

Macros used

Template links

Discovery rules

Items collected

Triggers

Feedback

AWS by HTTP

Overview

Requirements

Tested versions

Configuration

Setup

Macros used

LLD rule S3 buckets discovery

LLD rule EC2 instances discovery

LLD rule RDS instances discovery

LLD rule ECS clusters discovery

LLD rule ELB load balancers discovery

Feedback

AWS Cost Explorer by HTTP

Overview

Requirements

Tested versions

Configuration

Setup

Macros used

Items

LLD rule AWS daily costs by services discovery

Item prototypes for AWS daily costs by services discovery

LLD rule AWS monthly costs by services discovery

Item prototypes for AWS monthly costs by services discovery

LLD rule AWS monthly costs discovery

Item prototypes for AWS monthly costs discovery

Feedback

AWS Cost Explorer by HTTP

Overview

Requirements

Tested versions

Configuration

Setup

Macros used

Items

LLD rule AWS daily costs by services discovery

Item prototypes for AWS daily costs by services discovery

LLD rule AWS monthly costs by services discovery

Item prototypes for AWS monthly costs by services discovery

LLD rule AWS monthly costs discovery

Item prototypes for AWS monthly costs discovery

Feedback

Articles and documentation

Request custom integration

Propose your integration