AWS CloudWatch/Kinesis input restart issue

When editing and saving the settings for an existing AWS Kinesis/CloudWatch input, the new settings are not effective until the server restarts.

## Steps to reproduce the issue:
1) Create a new AWS Kinesis/Cloudwatch input.
2) Verify that the input is receiving messages.
3) Attempt to change a setting on the input (change the key/secret, or change the stream name).
4) You should see that the change is saved, but is not actually effective (eg. still using the old credentials or stream).
5) Restarting the server always seems to fix the issue.