问题描述
为什么可以解释为什么运行Windows 10的EC2实例不能始终访问其自身的元数据或用户数据?
What could explain why an EC2 instance running Windows 10 does not consistently have access to its own metadata or userdata?
我知道用户数据设置正确，因为大约30次t2.nano和c4.xlarge实例的启动使用了完全相同的脚本:t2.nano从未遇到读取元数据的任何问题，但在尝试使用a的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).
任何提示都值得赞赏.
Any hint is appreciated.
推荐答案
有一个脚本调用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无法访问元数据的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！