Many years ago, I created an EC2 instance with OpsWorks set up, as it sounded like a way to automate keeping its Amazon Linux OS up to date.
Fast forward to today, and OpsWorks is being shut down. For some reason the migration script provided for moving it to AWS Systems Manager won't work on this instance (S3 won't allow it to access the bucket the script is in,) and I don't really want to deal with the complexity of Systems Manager for this one instance anyhow.
I just want to break the dependency of this EC2 instance on OpsWorks so I don't have to worry about it somehow failing when OpsWorks is shut down. It runs fine on its own and I can maintain it on my own. Is this possible, or do I really have to rebuild everything on this host from scratch on a new instance?
AWS公式更新しました 3年前
Thanks - it turned out OpsWorks was associated with an EBS volume that no longer even existed in my case, so I ended up rebuilding this server from the ground up on a new instance. Hopefully this tip will help someone else though. Not how I wanted to spend the day, but at least it's done now.