While reviewing customer's jobs, I come across ETL framework that leverages S3 to store config files. During migration, these should be moved to Volumes and Posix file access.
Upgrading clusters to UC (shared) clusters will eliminate embedded instance profiles. Most boto3 implementations rely on the underlying instance profile to access S3 files (and other AWS services).
The assessment / crawler should Identify Jobs and Notebooks that import boto3, s3fs and other libraries indicative of direct use of instance profiles. Use of boto3, s3fs cluster libraries should be flagged.