- Newest
- Most votes
- Most comments
I would suggest passing "None" in the command line parameter --lb-type
and then migrate your load balancer separately.
There was a version "released" May 25, but apparently there has been at least 2 updates since then. Make sure you have downloaded the most recent version as well. The ETag on the most recent S3 object is 6f5ffc96a28499e9af3bb23f80200e31
and the VersionId is U.9K6yB20qa_xqlPJUYIX5f_.w.RL74K
the Last Modified date is 2023-06-23.
My opinion of that exporter script: hastily written, not tested -- LOTS of bugs and will create multiple issues for you down the road. Use it as a template to look at, but don't actually use it. Take some time to realize what the script is attempting to create for you, and then do it the right way.
I've been documenting my progress on migrating on a Medium article
https://medium.com/@jwestbrook/migrating-from-aws-opsworks-stacks-to-aws-systems-manger-eb3127a7a6c
Relevant content
- asked 4 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago