# Dynamic AWS host catalog : applying filter to hostsets is not working from boundary console

**URL:** <https://discuss.hashicorp.com/t/dynamic-aws-host-catalog-applying-filter-to-hostsets-is-not-working-from-boundary-console/39588>\
**Category:** Boundary\
**Created:** [May 17, 2022, 6:53am UTC](https://discuss.hashicorp.com/t/dynamic-aws-host-catalog-applying-filter-to-hostsets-is-not-working-from-boundary-console/39588 "2022-05-17T06:53:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajasekhar.meesala96](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/rajasekhar.meesala96/32/15966_2.png) [@rajasekhar.meesala96](https://discuss.hashicorp.com/u/rajasekhar.meesala96)\
**Post date:** [May 17, 2022, 6:53am UTC](https://discuss.hashicorp.com/t/dynamic-aws-host-catalog-applying-filter-to-hostsets-is-not-working-from-boundary-console/39588/1 "2022-05-17T06:53:13Z")

</div>

We are able to create AWS dynamic host catalog and while trying to create hostset in it, irrespective of tag filters, it is allowing all hosts of the region into it.  
`Tag format used :`  
tag:tag\_key=tag\_value

Also we are able set filters while creating the host set plugin using commands, but the created hostset details are not appeared in boundary console.

`Command used to create aws host catalog plugin:`

./boundary host-catalogs create plugin -scope-id p\_1234567890 -plugin-name aws -attr disable\_credential\_rotation=true -attr region=ap-south-1 -secret access\_key\_id=env://BOUNDARY\_ACCESS\_KEY\_ID -secret secret\_access\_key=env://BOUNDARY\_SECRET\_ACCESS\_KEY -addr=http://17X.XX.XX.XX:9200

`Boundary create aws host set plugin:`  
./boundary host-sets create plugin -name cloudec2 -host-catalog-id $HOST\_CATALOG\_ID -attr filters=tag:boundary\_connect=true -addr=http://17X.XX.XX.XX:9200

---

<div class="post-metadata">

**Author:** ![stellarsquall](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/stellarsquall/32/18044_2.png) [@stellarsquall](https://discuss.hashicorp.com/u/stellarsquall)\
**Post date:** [May 17, 2022, 5:01pm UTC](https://discuss.hashicorp.com/t/dynamic-aws-host-catalog-applying-filter-to-hostsets-is-not-working-from-boundary-console/39588/2 "2022-05-17T17:01:19Z")

</div>

Is it only the admin console that you cannot see the host set details in?

What happens when you perform a read on the host set? `boundary host-sets read -id $CLOUDEC2_HOST_SET_ID`

---

<div class="post-metadata">

**Author:** ![rajasekhar.meesala96](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/rajasekhar.meesala96/32/15966_2.png) [@rajasekhar.meesala96](https://discuss.hashicorp.com/u/rajasekhar.meesala96)\
**Post date:** [May 23, 2022, 6:29am UTC](https://discuss.hashicorp.com/t/dynamic-aws-host-catalog-applying-filter-to-hostsets-is-not-working-from-boundary-console/39588/3 "2022-05-23T06:29:10Z")

</div>

Yes, We are not able see it in admin console.  
But through commands we are able get results.