Unknown symbol CONFIG_AWS_IOT_SEC_TAG (v2.5.1->v2.6.1) in proj.conf

[HoovinSchoovin]

Hi, 

I had previously had a working project that was on the v2.5.1 toolchain sending mqtt messages up to my AWS IOT core. I then created a workspace in v2.6.1 and opened the AWS Iot sample. In the sample, I am no longer able to add CONFIG_AWS_IOT_SEC_TAG, only CONFIG_AWS_IOT_CLIENT_ID_STATIC and CONFIG_AWS_IOT_BROKER_HOST_NAME. I would like to know where i should put the security tag of the certificates now its not letting me in the .conf. 

When building the CONFIG_AWS_IOT_SEC_TAG in the conf, i get 

warning: attempt to assign the value 'XXXXX' to the undefined symbol AWS_IOT_SEC_TAG.

Additionally, if i have the certificates on the device from the certificate manager, do I also need them in the /certs folder in the directory. 

Any help here would be greatly appreciated - have tried looking for anything online and came up empty.

Thanks,

Sam

[HoovinSchoovin]

UPDATE: 
I belive from v2.5.1 to v2.6.1, CONFIG_AWS_IOT_SEC_TAG is now replaced by CONFIG_MQTT_HELPER_SEC_TAG. I have followed this tutorial and still get this issue below. 

Any direction to go would be very helpful. Thanks!

[00:03:59.244,934] <err> mqtt_helper: getaddrinfo() failed, error -2
[00:03:59.244,964] <err> aws_iot: mqtt_helper_connect, error: 2
[00:03:59.244,964] <err> aws_iot_sample: aws_iot_connect, error: 2

[HoovinSchoovin]

Final update (for those who run into the same issue):

Ultimately, the issue did not stem from the version change (which was a red herring), but. change of location i belive. I had recently moved to Scotland and my sim provider (onomondo) uses O2. I believe that this network causes the DNS lookup to fail, maybe because i need to add extra configuration. 

Since i am only in Scotland for a little bit, I have changed the DNS configuration to temporarily hardcode the ip address of the AWS endpoint. 

I think this relates to: this question and this question. 

Hopefully this helps and if this is not the right explanation or if there is any other things that could cause this DNS issue please let me know. 

[HoovinSchoovin]

Can confirm that out of Edinburgh, Scotland everything works fine. Think its an issue with the O2 network or my cell tower possibly.

[HoovinSchoovin]

For anyone using O2 in the UK, especially if using Onomondo, check out this: here

Affected areas:

LTE-M

• Vodafone (262-02), Germany

• Vodafone (230-03), Czech Republic

• O2 (234-10), UK

NB-IoT

• Orange (206-10), Belgium

Hope this saves someone some time debugging