Creating workspace image fails with "ErrorCode": "Internal.ServerError"

When creating a custom WorkSpace image, the "Internal.ServerError" error with the message "There was an issue importing your image" can occur due to several underlying issues.

Based on your description, here are some troubleshooting steps to consider:

1. Check antivirus or security agent settings:

• Temporarily disable any antivirus or security software during the image creation process as these can interfere with the process.

2. Verify service account configurations:

• If your application services are using domain accounts, change them to use Local System, Local Service, or Network Service instead.
• You can check services through services.msc

3. Check PowerShell execution policy:

• Ensure that the PowerShell execution policy allows RemoteSigned scripts.
• Verify this by running: Get-ExecutionPolicy

4. Verify Windows Remote Management (WinRM) service configuration:

• Ensure the "Windows Remote Management (WS-Management)" service is set to "Automatic" startup type.

5. Check for domain guest group assignments:

• Make sure the WorkSpace isn't assigned to a user within a Domain Guests group.

6. Review Group Policy Objects (GPOs):

• Some GPOs can restrict access to the RDP certificate thumbprint when requested by EC2Config service or EC2Launch scripts.
• Try moving the WorkSpace to a new organizational unit with blocked inheritance and no GPOs applied.

The fact that you've successfully created images without opening Office apps but fail when you do suggests there might be an issue with how Office is configured or how it interacts with the image creation process. This could be related to licensing activation, configuration files, or other Office-specific settings.

Since you've already run the Image Checker and all tests passed, the issue might be occurring during the actual image import process rather than in the preparation phase. If you continue to experience this issue after trying these steps, contacting AWS Support as suggested in the error message would be the next appropriate step, as they can investigate specific issues with your WorkSpace configuration that require deeper investigation.
Sources
Error in creating custom image of windows workspace | AWS re:Post
Troubleshooting A WorkSpace custom image creation error - Best Practices for Deploying WorkSpaces

All checks are ticked. Workspace is in Default Computer OU so no extra group policy is applied on it. We do not have any support contract with AWS. How would I raise ticket with AWS. Can you please advise