Amazon Web Service (AWS) via NB-IoT or LTE-M ?
Dear all experts,
currently I am trying to use AWS by NB-IoT.
I can ping the AWS server, but the connect fails. Has anyone experience with AWS and NB-IoT?
I am wondering if this may work better with LTE-M, but I need to get some new DT SIM that would allow me some further testing.
I am using a Murata Type1SC modem.
Any feedback welcome, thanks,
If the simcard comes from iotcreators.com, you just need to follow this instruction: https://docs.iotcreators.com/docs/integrations
But if you got the simcard directly from Telekom Deutschlan, I’ll have to ask a colleague.
We have got the SIM from DT in August 2018
Can you confirm, that AWS accessed via DT NB-IoT should not be a problem (from technical point of view)?
AWS access via our DT APN that is open to the internet is no problem. In case you have a private APN from DT then it’s a bit special but also no problem.
But the point in your case might be: DT offers test SIM that are active for one year. We need to check first whether your SIM are still ready to use. Please DM me and I’ll sort that out for you.
as mentioned SIM works fine with DT CoT, and I can ping AWS succesfully. So it should work
I am using DT APN: internet.nbiot.telekom.de
See the ‘Uta chat room’ (or what do you mean by ‘DM’), I will send you the IMSI, or what do you need?
So in general it really depends on what you mean with “access AWS”.
One possibility is to get a Mobile IP-VPN where you have a private IPSec tunnel from an APN (i.e. Telekom Mobile Network Core) to a Site-to-Site VPN in your AWS account. Your devices can not reach the public internet then but only instances/services in AWS (using private IP adresses of the instances).
If you have a SIM card with a public APN (which you have) you can reach public IP addresses from your device. This includes of course also EC2 instances in AWS that have a public IP address. With NB-IoT you would have to make sure that the way you communicate with your EC2 instance is based on a UDP-protocol because NB-IoT is limited in regards to bandwith.
If you want to use AWS IoT/Greengrass, you are going to run into problems with NB-IoT and we do not recommend it. AWS IoT is based on MQTT which is based on TCP. NB-IoT is (as the name suggests) NarrowBand. The pipe is just too thin for protocols based on TCP. AWS IoT does currently not support protocols that are suited for Constrained Devices (e.g. CoAP, LwM2M).
It is a whole different story for LTE-M though, because LTE-M has way higher bandwidth and MQTT will work perfectly fine.
Hope this answers the question!
Dear Yassine, good to meet you again, hope you are doing well?
Thanks for the explanation. As you know, we are not using NB-IoT actively, just trying to learn how to support customers in case of LPWAN application together with our low-power micros. Actually, I was trying to see whether AWS IoT + MQTT can work. If I understand you correctly, then probably we should better talk about to do some tests with LTE-M + AWS. Does DT cover the Rhein-Main area (Frankfurt/Darmstadt)?
I am doing well, thanks! Hope you as well
Strictly speaking it will work when you have good coverage but it doesn’t make a lot of sense for NB-IoT especially because the battery is suffering a lot while trying to send that much data frequently.
In worse coverage conditions, where the latency is higher and the bandwidth lower you will run into problems, guaranteed.
Yes, we cover Frankfurt/Darmstadt area
In your case, you can’t go wrong with LTE-M and I think you will be very happy with it. Try it out!
The battery efficiency is still high and the bandwidth gives you more freedom for your use cases.
@Yassine-Amraue : this sounds good! Just need to clarify how we can get some new SIMs for testing purpose.
Thank you very much! Appreciating the Telekom support!
Stay safe and healthy!
@Holger-Wech Your SIM cards are deactivated now because the contract ended 2019. But I’ll replace them for free and they will be shipped in the next few days. Thus you can additionally benefit from our new features like LTE-M and roaming. I’m glad that we were able to solve the issue this way.
I have received the new SIMs NB-IoT is working, but I am not sure about the LTE-M … CREG result is 5,2 respectively 3,0,19
Do I need to change the APN for LTE-M? All the description (QuickStartGuide, Developer Guide) only refer to NB-IoT. How to use/test the LTE-M now?
@Holger-Wech you can use LTE-M instead of the 2G/3G fallback that is described in our quick start guide. Please use the APN internet.m2mportal.de for LTE-M.
This post is deleted!
This post is deleted!