Access restrictions

Restrict access to your analytic resources to named users only. Avoid the trap of keeping a single user ID and password that everyone uses. For resources accessed by public/private keys, make sure to keep the private key in a safe, secure place.

For networking security, only allow network traffic through to your resources that are needed. Block all others. Lock everything down from the start and then open things up only when needed.

In a distributed computing environment, such as you will use for IoT analytics, networking is a key element in both security and problem solving. You will run into situations where your analytic jobs will not run correctly and find that the source was a network or security related setting. It is best to understand this and use best practices from the start of your analytics projects.