Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2140
Regarding the migration strategy... Lets make sure we document on the
migration wiki page [1] that anyone who built custom components using the AWS
controller service should rebuild them with the new dependency as part of their
upgrade process.
Given our component versioning, it would actually be possible to run the
old stuff and the new stuff at the same time, but it would require a
complicated setup. I think you'd have to leave the 1.3.0 AWS NAR, 1.3.0
standard services API NAR, and possibly 1.3.0 standard NAR, plus the users
custom NAR that depended on 1.3.0 AWS NAR. Probably not the recommended
approach, but a fallback option.
[1] https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
---
