# How to achieve not\_analyzed field mapping in AWS solution
**URL:** https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083
**Category:** Elasticsearch
**Created:** [October 27, 2015, 2:55pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083 "2015-10-27T14:55:22Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Mark\_Watkins](https://discuss.elastic.co/u/Mark_Watkins)
#### Post date: [October 27, 2015, 2:55pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/1 "2015-10-27T14:55:22Z")
My first post was the below:
Hi,
I am trying to count unique log streams, and the format of the value is "i-123abc456".
When I do the unique count, it counts the "i" as one value, so it is adding 1 to my unique count.
i.e. if I had a legend, we would have:
i
123abc456
If there were two log streams, "i-123abc456" and "i-789def101", then the count would be three and the legend would be:
i
123abc456
789def101
Do you know what I can do to fix this pls?
* * *
Second question: Now I need to know how to achieve not analysed fields in AWS - if possible?
Thanks,
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 27, 2015, 3:38pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/2 "2015-10-27T15:38:17Z")
> [@Mark\_Watkins](#):
>
> Do you know what I can do to fix this pls?
Define this field as `not_analyzed`.
> [@Mark\_Watkins](#):
>
> Second question: Now I need to know how to achieve not analysed fields in AWS - if possible?
As soon as you can push your mapping it should be doable.
---
### Author:  [@Mark\_Watkins](https://discuss.elastic.co/u/Mark_Watkins)
#### Post date: [October 27, 2015, 3:53pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/3 "2015-10-27T15:53:55Z")
Is this all possible within the AWS managed service of ES and Kibana?
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 27, 2015, 4:11pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/4 "2015-10-27T16:11:48Z")
I have no idea but I suppose it is... Why?
Is that not working for you? What did you do to define your mapping?
---
### Author:  [@Mark\_Watkins](https://discuss.elastic.co/u/Mark_Watkins)
#### Post date: [October 27, 2015, 4:36pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/5 "2015-10-27T16:36:57Z")
Mapping is automatically generated. AWS have launched a managed version, and I think it might be missing some of the features I need to be able to define the field as not\_analyzed - might be wrong, but cannot see where I can edit mappings...
---
### Author:  [@Mark\_Watkins](https://discuss.elastic.co/u/Mark_Watkins)
#### Post date: [October 27, 2015, 4:44pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/6 "2015-10-27T16:44:50Z")
I can see the option to add scripted fields... maybe there is a solution there.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [October 27, 2015, 4:49pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/7 "2015-10-27T16:49:28Z")
I don't believe so. May be you have a link to AWS doc?
But let me say that mappings are automatically generated by elasticsearch on premise as well unless you specifically PUT your mapping before pushing the very first document.
Search for PUT mapping in elasticsearch doc.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:42pm UTC](https://discuss.elastic.co/t/how-to-achieve-not-analyzed-field-mapping-in-aws-solution/33083/8 "2017-07-05T23:42:22Z")