Skip to content

feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer#5630

Open
MarvinBeGood wants to merge 12 commits intoaws:masterfrom
MarvinBeGood:feature_kms_encryped_tuner_output
Open

feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer#5630
MarvinBeGood wants to merge 12 commits intoaws:masterfrom
MarvinBeGood:feature_kms_encryped_tuner_output

Conversation

@MarvinBeGood
Copy link

@MarvinBeGood MarvinBeGood commented Mar 15, 2026

Issue #, if available:
#5622

Description of changes:

  • reusing the output_data_config from the model_trainer to allow the encryption with kms key instead of creating a new OutputDataConfig object
  • renamed Resolved template parameters: {'role_arn.md to Resolved_template_parameters_role_arn.md to ensure the filename is also valid for windows
  • replaced MagicMock class with OutputDataConfig because HyperParameterTrainingJobDefinition expectes a OutputDataConfig object at the test_tuner.py

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@MarvinBeGood MarvinBeGood changed the title Feature to allow kms encryped tuner output by reusing the output_data_config from the model_trainer feature: allow kms encryped tuner output by reusing the output_data_config from the model_trainer Mar 17, 2026
Remove merge conflict markers and clean up code.
Removed output data configuration building from tuner.py.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant