I've experienced this exact issue on t1.micro instances in eu-west-1 running erlang and postgresql. Java isn't even installed. Does Amazon have a publicly accessible page tracking the issue and the rollout of the fix to regions other than us-west-2?
I've experienced this exact issue on t1.micro instances in eu-west-1 running erlang and postgresql. Java isn't even installed. Does Amazon have a publicly accessible page tracking the issue and the rollout of the fix to regions other than us-west-2?