Mesmo eu enfrentei o mesmo problema, então tentei reiniciar o Instance e depois de algum tempo nas informações do Route Ipv4, consegui identificar o 3º destino com o qual a Instância tentava pegar os meta-dados. Esta não é a solução exata para o problema, mas um tipo de alternativa.
[ 131.326590] cloud-init[548]: Cloud-init v. 18.4-0ubuntu1~16.04.2 running 'init' at Thu, 29 Nov 2018 13:01:17 +0000. Up 104.95 seconds.
[ 131.373908] cloud-init[548]: ci-info: +++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++++
[ 131.398661] cloud-init[548]: ci-info: +--------+-------+------------------------------+---------------+--------+-------------------+
[ 131.419546] cloud-init[548]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
[ 131.515524] cloud-init[548]: ci-info: +--------+-------+------------------------------+---------------+--------+-------------------+
[ 131.567586] cloud-init[548]: ci-info: | ens3 | True | 20.0.0.9 | 255.255.255.0 | global | fa:16:3e:fb:ba:81 |
[ 131.595173] cloud-init[548]: ci-info: | ens3 | True | fe80::f816:3eff:fefb:ba81/64 | . | link | fa:16:3e:fb:ba:81 |
[ 131.621358] cloud-init[548]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |
[ 131.652707] cloud-init[548]: ci-info: | lo | True | ::1/128 | . | host | . |
[ 131.681617] cloud-init[548]: ci-info: | sit0 | False | . | . | . | . |
[ 131.716687] cloud-init[548]: ci-info: | tunl0 | False | . | . | . | . |
[ 131.747621] cloud-init[548]: ci-info: +--------+-------+------------------------------+---------------+--------+-------------------+
[ 131.828146] cloud-init[548]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++
[ 131.891154] cloud-init[548]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[ 131.912601] cloud-init[548]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
[ 131.935481] cloud-init[548]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[ 131.981100] cloud-init[548]: ci-info: | 0 | 0.0.0.0 | 20.0.0.1 | 0.0.0.0 | ens3 | UG |
[ 132.029476] cloud-init[548]: ci-info: | 1 | 20.0.0.0 | 0.0.0.0 | 255.255.255.0 | ens3 | U |
[ 132.058772] cloud-init[548]: ci-info: | 2 | 169.254.169.254 | 20.0.0.1 | 255.255.255.255 | ens3 | UGH |
[ 132.097319] cloud-init[548]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+
[ 132.126704] cloud-init[548]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
[ 132.154971] cloud-init[548]: ci-info: +-------+-------------+---------+-----------+-------+
[ 132.179131] cloud-init[548]: ci-info: | Route | Destination | Gateway | Interface | Flags |
[ 132.211508] cloud-init[548]: ci-info: +-------+-------------+---------+-----------+-------+
[ 132.219367] cloud-init[548]: ci-info: | 0 | fe80::/64 | :: | ens3 | U |
[ 132.259315] cloud-init[548]: ci-info: | 4 | ff00::/8 | :: | ens3 | U |
[ 132.283589] cloud-init[548]: ci-info: +-------+-------------+---------+-----------+-------+
[ 132.311049] cloud-init[548]: Generating public/private rsa key pair.
[ 132.318065] cloud-init[548]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
[ 132.327114] cloud-init[548]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
[ 132.364865] cloud-init[548]: The key fingerprint is:
[ 132.378265] cloud-init[548]: SHA256:IhhdlSjJqLvj6PGiwTxA+SX7HbTHc4nSKBkqSIY3ye4 root@test1
[ 132.405438] cloud-init[548]: The key's randomart image is: