- Newest
- Most votes
- Most comments
Update as of May 14th: I talked to support and they should be deploying a change in 24-48 hours that will allow a user to edit the notebook instance and modify the Platform identifier to a value that is associated with Linux 2, and thus allow the instance to start again. I will update to confirm this actually works when I am available to make the change and try to start my old instance (Linux 1 type) again.
Update, May 16th: Nothing has changed, yet. Will ask support now when I should expect the change that was communicated previously.
Update , May 17th. Now I am being told "Monday". They claim they are doing updates "in batches", so the initial 24-48 hours turned into a week. I will continue to update as I get more information or things change.
Hi - I did get a resolution as of today, but it is not what I had initially understood. Support was able to re-enable my old Linux 1 instance so that it now can restart. This did work and I can access my files now for migration to a new instance I have created that is Linux 3 type.
I had misunderstood initially that I would be able to convert my Linux 1 instance to a Linux 3 instance in the Edit screen, but this was not the case. They instead let me restart the instance and this should be an acceptable solution so I can migrate by hand my files.
- Eric
Relevant content
- asked 2 years ago
- asked 10 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago