This is because the normal kaa deployment in AWS uses a t12 micro instance. This limits the kaa usage. Once the limit is crossed this error will occur.
Creating a new instance will solve the problem. I was finding that the same thing was happening for me until I did so.
This is because the normal kaa deployment in AWS uses a t12 micro instance. This limits the kaa usage. Once the limit is crossed this error will occur.
Creating a new instance will solve the problem. I was finding that the same thing was happening for me until I did so.