Estimator can’t take network configuration object as parameter. Instead, it asks for subnets, sg’s and network isolation flag for each

[idanmoradarthas]

Describe the feature you'd like
Like sagemaker.processing.ScriptProcessor receives network_config parameter as sagemaker.network.NetworkConfig object, we want sagemaker.estimator.Estimator to do the same instead of a multiple parameters for subnets, security_group_ids and enable_network_isolation.

How would this feature be used? Please describe.
sagemaker.estimator.Estimator will have a single parameter named network_config that accepts sagemaker.network.NetworkConfig object.

Describe alternatives you've considered
this is what we do today in our pipeline object, as we have processing steps and HPO steps:

step_network_config = NetworkConfig(
        security_group_ids=[security_group],
        subnets=[subnet1, subnet2, subnet3],
        enable_network_isolation=bool(network_isolation_flag)
    )

Estimator(
        subnets=step_network_config.subnets,
        security_group_ids=step_network_config.security_group_ids,
        enable_network_isolation=step_network_config.enable_network_isolation
)

[mufaddal-rohawala]

Hey thanks for reaching out to SageMaker, can you try out the ModelTrainer interface we have released recently for Training. The issue mentioned here should be addressed by it.