Hello,
I can get ec2 info,
but I can't get status , It's show not support, and time out to executing shell script

I had permissions following below figure

Template AWS doesnt have any item

please help me

thanks a lot

for now all aws EC2 hosts added, but each instance in zabbix have interface IP 127.0.0.1. This is greyed and not editable because added by discovery rule from template.
My EC2 instances have hostname that is "APPNAME_INSTANCEID", like "web1_i-01013167c8f712345". So I changed "host prototype" in rule to:
{#INSTANCE.NAME}_{#INSTANCE.ID}

Now all added, but problem to allow agents to be accepted, probably because this registered in zabbix host names have different interface IP (127.0.0.1) then real host IP. Same issue if host added by agent - discovery rule can do nothing because this name exists....

The goal is to manage instance lifecycle (adding and removing) and AWS resources with zaws discovery, but be able to monitor with installed there agent.

How to define discovery to add real instance IP instead of 127.0.0.1?

Thanks!

After upgrading to Zabbix 4.4, whenever there is a host down the cloudwatch stats monitor will trigger this error message and can be seen in the "zabbix_server.log"

Hi Ike,

I try ZWAS on Zabbix 3.0, and he can discovery my hosts, but without any information...

On zabbix_server.log, I have this error:

2205:20160304:161438.281 cannot process json request: Can't open JSON object or array "null,"clock":1457108078}"

Do you know how can I figure out this ?

Thanks!

Hi @ike-dai !

Is it possivel to add Agent interfaces on AWS discovered hosts? I want to a Agent interface pointing to the public IP address of my AWS instance on port 10050 to collect data from the Zabbix agent installed on the instance.

Thank you a lot for this resource.

Thank you for this really nice tool.

I have start using this to monitoring EC2 instances, but facing a issue with the item disk space utilization, that doesn't show any information on zabbix 3.0. Is there some adicional configuration to do?

Thank you.

When i've tried to discover metrics for my t3.* instance, i've got this responce:

{"data":[{"{#METRIC.NAME}":"NetworkPacketsIn","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSReadBytes","{#METRIC.UNIT}":"Bytes","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"NetworkPacketsOut","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSReadOps","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"CPUCreditUsage","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSIOBalance%!"(MISSING),"{#METRIC.UNIT}":"Percent","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"CPUSurplusCreditBalance","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"CPUCreditBalance","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"CPUUtilization","{#METRIC.UNIT}":"Percent","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSWriteOps","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"NetworkOut","{#METRIC.UNIT}":"Bytes","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"StatusCheckFailed_Instance","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"NetworkIn","{#METRIC.UNIT}":"Bytes","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSWriteBytes","{#METRIC.UNIT}":"Bytes","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"EBSByteBalance%!"(MISSING),"{#METRIC.UNIT}":"Percent","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"CPUSurplusCreditsCharged","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"StatusCheckFailed_System","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"},{"{#METRIC.NAME}":"StatusCheckFailed","{#METRIC.UNIT}":"Count","{#METRIC.NAMESPACE}":"AWS/EC2"}]}

And that's not a valid JSON object (already confirmed that at https://jsonlint.com/), because there are two metrics with "broken" names:

"{#METRIC.NAME}": "EBSIOBalance%!"(MISSING),
and
"{#METRIC.NAME}": "EBSByteBalance%!"(MISSING),

It appears, that "(MISSING)" string breaks json format.

As i am not a programmer, but a jack-of-no-trades OPS, i have no knowledge how to fix that in source code. And suddenly an idea came into my mind - i can solve this with bash and sed like this:

1. 've renamed zaws to zaws-bin
2. 've created shell-script zaws with such content:

`#!/bin/bash

/usr/lib/zabbix/externalscripts/zaws-bin $@ | sed -e "s|(MISSING)||g"`

So, if anyone can fix this issue in source code and build new binary - it would be awesome.

Hi Ike,

Trying to configure zaws plugin in zabbix 3.4, but get 'Value should be a json object' on 'Discovery rules' page. Could you help to find and solve the root cause? Thanks!

Can you document what permissions are required for the AWS user (apart from given them entire admin access)

I am a bit new at this but was wondering if the keys could be omitted if a role with the proper permissions was already attached to the EC2 instance on which zaws was running. Looking at the code, it appears that execution will exit if there is no key provided. I have tended to use role assignment on EC2 instances to avoid having to worry about key vulnerability.

Is there any chance to upgrade your code a little?
Now it is calling only for ELBv1, I need it to call ELBv2 as well.

hi, its work with zabbix 4+?

Thankyou for this nice tool.

I have started using this but facing issue in monitoring ELB.
It show request count always 1 , please suggest how can I get actual count.

Thankyou