Refresh errors - aws_kms_alias.kms_sym_alias is waiting for aws_kms_key.kms_sym_key

[treyp]

Have a few different AWS account i used TF to build out earlier this year. had run jobs many times without an issue over a couple months as things got tweaked.

Using TF 0.12.26 

Now its been several months and with no  real code updates my builds are hanging when doing a refresh. When i run my plan and set refresh=false, it works fine but then obviously I'm not really checking state.

The general error then seems to point at KMS
```

Error: RequestError: send request failed caused by: Post https://kms.us-gov-west-1.amazonaws.com/: dial tcp 138.76.34.49:443: i/o timeout

``` 

Enabling trace on tf indeed shows that:
```
[TRACE] dag/walk: vertex "root" is waiting for "provider.aws (close)"

[TRACE] dag/walk: vertex "provider.aws (close)" is waiting for "aws_kms_alias.kms_sym_alias"

[TRACE] dag/walk: vertex "aws_kms_alias.kms_sym_alias" is waiting for "aws_kms_key.kms_sym_key"
```

the KMS config is pretty simple here, just a new symmetric key with a policy attached and then a friendly alias for it. 

I realized my AWS provider was kinda old 2.1x - so i bumped to a 2.7 and still same. Just tested with ~> 3.0 but still the same.

Also tossed a depends_on in there for the alias on the key since the error seems to say the alias is waiting on the key thinking perhaps an ordering issue but still the same waiting for error.

Any thoughts or advice ti test out? Thanks in advance

- trey