AutoGluon framework support

[athewsey]

Describe the feature you'd like

autogluon, which is already available through image_uri_config and seems to work in script mode, should ideally have fully-documented framework support!

A full set of AutoGluon Framework-based classes for estimator/model/predictor/processor/etc for these DLCs would be ideal, but even if that's not possible, it seems like some more documentation could help boost awareness?

How would this feature be used? Please describe.

I was surprised to see in this recent AWS Innovate video (also linked above), that we can already use autogluon as a framework-like container for building cool multi-modal models in script mode.

It's a shame because it seems like a cool tool and not cleanly documented/incorporated along with the other available tools:

• AutoGluon-Tabular algorithm docs only cover the (non-multi-modal) JumpStart-based algorithm option
• There's no mention of AutoGluon on the SDK frameworks doc that I could see
• The JumpStart models doc focusses on actual models rather than script-mode-capable frameworks
• The SageMaker Developer Guide pre-built containers list doesn't seem to cover them either

Mentioning it in the relevant doc(s) could help users find and get started with this tool faster, and providing more explicit SDK-based support via extra classes could further help with usability.

Describe alternatives you've considered

I guess the two main options to me at the moment seem:

1. Build AutoGluon functionality directly into the SDK, presumably as a thin wrapper over Framework and the other base classes since not much framework-specific behaviour seems required at the moment - or
2. No significant code changes, but try to incorporate AutoGluon into relevant documentation to help users discover and get started with using it in script mode (particularly for e.g. multi-model models or timeseries models not currently supported by the built-in algorithm option?)

Additional context

I know the available DLCs are listed here already, but IMO that's not really documentation of the available framework functionality by itself...