1 Answer
- Newest
- Most votes
- Most comments
0
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...
answered 2 years ago
Relevant content
- Accepted Answerasked 2 years ago
- asked 6 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Appreciate the follow up on resolving the issue - the best practice for providing internet access to WorkSpaces instances is to use a NAT gateway.
In addition to what "MuraliAtAWS" stated. You can refer to this best practices guide for more details. https://docs.aws.amazon.com/whitepapers/latest/best-practices-deploying-amazon-workspaces/best-practices-deploying-amazon-workspaces.html