# Functionbeat 7.16.2 parses quoted strings with periods as objects
**URL:** https://discuss.elastic.co/t/functionbeat-7-16-2-parses-quoted-strings-with-periods-as-objects/294097
**Category:** Beats
**Tags:** functionbeat
**Created:** [January 12, 2022, 1:16am UTC](https://discuss.elastic.co/t/functionbeat-7-16-2-parses-quoted-strings-with-periods-as-objects/294097 "2022-01-12T01:16:44Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cafuego](https://discuss.elastic.co/u/cafuego)
#### Post date: [January 12, 2022, 1:16am UTC](https://discuss.elastic.co/t/functionbeat-7-16-2-parses-quoted-strings-with-periods-as-objects/294097/1 "2022-01-12T01:16:44Z")
We maintain a set of billing tags on our AWS resources that are prefixed with "cost.". The 7.16.2 version of functionbeat errors out on those tags, despite me quoting the tag strings in the yaml file, it interprets them as objects and errors out when I try to update:
`Function: functionbeat-cloudwatch-elk, could not update, error: can not convert 'object' into 'string' accessing 'functionbeat.provider.aws.functions.0.tags.cost' (source:'config.yml')`
I was pretty sure that worked with the previous version I used (7.15.0) but I can't reproduce that behaviour now, so I probably hallucinated it 🙂
Nevertheless, it would be good if I could set tags in formats that are completely acceptable to AWS. Do I need to do a magic thing to make it accept "cost.foobar" as a valid tag name, or is this a bug in the config parser?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 9, 2022, 3:17am UTC](https://discuss.elastic.co/t/functionbeat-7-16-2-parses-quoted-strings-with-periods-as-objects/294097/2 "2022-02-09T03:17:28Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.