Windows Upgrade using AWSEC2-CloneInstanceAndUpgradeWindows automation fail

0

I am attempting to upgrade a Windows Server 2012R2 EC2 Instance to Windows Server 2019 using the AWS Systems Manager automation:
AWSEC2-CloneInstanceAndUpgradeWindows

I have followed the instructions outlined here to perform the upgrade:
https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/automated-upgrades.html

I have updated the SSM agent on the server that I am upgrading to the newest version. I have also updated the EC2Config service to the latest version and rebooted the server.

I have created a new IAM role to use for the upgrade and I have attached the AmazonSSMManagedInstanceCore policy to the role. I have set this role as the IAM role on the instance that I am attempting to upgrade.

I am running the upgrade with a subnet that is in the same default VPC as the instance that I am trying to upgrade. The subnet is a different previously unused default subnet within that default VPC as the instructions suggest. The subnet does have Auto-assign public IPv4 address set to yes.

The automation fails on step 7:

Automation step7: runUpgradeFrom2012R2Or2016

Failed to run automation with executionId: theId Failed :
{Status=[Failed], Output=[No output available yet because the step is not successfully executed, No output available yet because the step is not successfully executed], ExecutionId=theId}

I am having trouble narrowing down the problem or finding a cause for the failure based on the error above. Any pointers or help will be greatly appreciated!

Thank you,

Brian

질문됨 3년 전1283회 조회
1개 답변
0

I got to the bottom of this. I ended up installing the latest SSM Manager again as it seemed to be failing on startup. I removed all traces of EC2Config on the system (both in program files and program data), then installed EC2LaunchV2. After doing all of this the upgrade seems to have started working.

답변함 3년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠