In case anyone runs into the same issue:
- the Worskpace loses the association to the Elastic IP during the migration
- it needs to be re-associated to the (any) Elastic IP to restores Internet access, dah.
I suggested to AWS to inform about the Elastic IP been de-associated in the Administration Guide...
Does Microsoft SQL Server 2019 Standard on Windows Server 2019 include SSRS?asked 3 days ago
Cannot access the workspace using workspace client or RDPasked 2 months ago
No Internet access after migration of Workspace from Server 2016 to 2019Accepted Answerasked a month ago
AMI created by Server Migration ServiceAccepted Answerasked 5 months ago
Migration of Windows File Server from Datacenter to AWSasked 18 days ago
Windows Server image migration in appstream from Windows Server 2012 R2 to 2016 or 2019.Accepted Answerasked 3 months ago
Ec2 instance Windows server 2019 upgradeasked 2 months ago
About DMS migration from ms-sql to dynamodbasked 2 months ago
Connection to external VPN from Windows Server 2016asked 6 months ago
Migrate on-pre VDI data to AWS Workspaceasked 2 months ago