# Event error on check

**URL:** <https://discourse.sensu.io/t/event-error-on-check/1535>\
**Category:** Sensu Go\
**Created:** [December 20, 2019, 8:48am UTC](https://discourse.sensu.io/t/event-error-on-check/1535 "2019-12-20T08:48:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eyangui](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@eyangui](https://discourse.sensu.io/u/eyangui)\
**Post date:** [December 20, 2019, 8:48am UTC](https://discourse.sensu.io/t/event-error-on-check/1535/1 "2019-12-20T08:48:26Z")

</div>

Hello Team,

I launch my first check on sensu, i follow the docs for create the cpu check, i attached him the right suscription.

I work on aws on two agent based on the same VPC.

For the check-cpu i have the same issue for both agent machine supervise :

error getting assets for event: error fetching asset: Get [https://assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks\_4.0.0\_centos\_linux\_amd64.tar.gz:](https://assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks_4.0.0_centos_linux_amd64.tar.gz:) dial tcp 143.204.229.101:443: i/o timeout

I thought of a proxy error my company is very restrictive but if I managed to download the asset and the plugin once I shouldn’t have any more worries

Thanks in advance

---

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [December 20, 2019, 6:35pm UTC](https://discourse.sensu.io/t/event-error-on-check/1535/2 "2019-12-20T18:35:40Z")

</div>

Hey,  
Yes it sounds like some sort of problem with the proxy or network.  
If you need to use a proxy, make sure you setting HTTP\_PROXY in the sensu-agent environment. If you are using the linux packages provided by Sensu, then you should be able to set envvars like HTTP\_PROXY in either /etc/default/sensu-agent or /etc/sysconfig/sensu-agent and then restart the sensu-agent service.

Else, if you need to, you can manually download any of those asset tarballs from bonsai and then host them internally on your own network using a http server you control. You would just need to edit the asset resource to point to your local webserver. You always have the option to host assets locally, it’s just a little more complicated to configure them.

---

<div class="post-metadata">

**Author:** ![eyangui](https://avatars.discourse-cdn.com/v4/letter/e/c37758/32.png) [@eyangui](https://discourse.sensu.io/u/eyangui)\
**Post date:** [January 6, 2020, 10:31am UTC](https://discourse.sensu.io/t/event-error-on-check/1535/3 "2020-01-06T10:31:33Z")

</div>

Hello,

First Happy new years

Thanks for your response. I’m going to host them internally on a S3 bucket. Just like you propose. But ressource in the asset template do i have to change?

---

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [January 6, 2020, 7:32pm UTC](https://discourse.sensu.io/t/event-error-on-check/1535/4 "2020-01-06T19:32:52Z")

</div>

Hey!

If you just want to point to S3 cached tarballs, all you have to do is change the url for the asset resource definition. The sha512 should be the same, if you are just caching the tarball that you would have retrieved from github or bonsai.

If you S3 bucket requires additional http headers, we can add headers into the asset resource as needed.