AWS EC2 Windows 10 无法访问元数据 [英] AWS EC2 Windows 10 can't access metadata

问题描述

有什么可以解释为什么运行 Windows 10 的 EC2 实例无法始终访问其自己的元数据或用户数据?

What could explain why an EC2 instance running Windows 10 does not consistently have access to its own metadata or userdata?

我知道 userdata 设置正确，因为完全相同的脚本用于 t2.nano 和 c4.xlarge 实例的大约 30 次启动:t2.nano 从未遇到任何读取元数据的问题，但在 3 次尝试中c4.xlarge 只有一个人可以访问它.该脚本仅在实例名称上有所不同(至少根据 git 历史记录).

I know the userdata is set correctly because the exact same script was used for about thirty launches of t2.nano and c4.xlarge instances: the t2.nano never encountered any issue reading the metadata, but out of three attempts with a c4.xlarge only one had access to it. The script only differed by the name of instance (as per git history at least).

我按照下面的说明进行操作，即使在 Powershell 中，Uri 也无法加载(参见图 2).

I followed the instructions below, and even from a Powershell, the Uri fails to load (cf. Figure 2).

任何提示表示赞赏.

推荐答案

有一个脚本调用 InitializeInstance.ps1 会重置一些配置信息.

There is a script call InitializeInstance.ps1 that resets some configuration information.

例如，如果实例更改了子网，则由于缓存的路由规则，它可能无法正常工作.InitializeInstance.ps1 可以纠正这个问题.

For example, if the instance has changed subnets it might not work correctly due to cached routing rules. The InitializeInstance.ps1 can correct this.

这篇关于AWS EC2 Windows 10 无法访问元数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！