This repository was archived by the owner on May 23, 2025. It is now read-only.
Enable using MLOps guidance in nested stack#210
Open
athewsey wants to merge 1 commit intoaws-samples:mainfrom
Open
Enable using MLOps guidance in nested stack#210athewsey wants to merge 1 commit intoaws-samples:mainfrom
athewsey wants to merge 1 commit intoaws-samples:mainfrom
Conversation
Expose useful outputs from MLOps solution guidance stack to enable nesting it inside other CloudFormation templates to trigger and chain the workflows it creates. Shorten role name that was causing problems when nesting the stack. Explicitly set string types to ambiguous bool parameters (YAML interprets plain true as a bool, not string, and in one instance I got errors during CFn deployment complaining about string types). Fill in a placeholder SFn description.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available: N/A
I'd like to be able to re-use the
ml_opssolution guidance stack within other stacks: A deployable stack that provisions the dependencies, the guidance stack, and then some other resources e.g. a customised end-to-end state machine using the pre-built components.Today, that's a challenge because the stacks don't expose any outputs. There's no config in AWS::CloudFormation::Stack to explicitly set stack name: It gets generated automatically and isn't visible via
GetAtton the resource either. So just locating resources by assumed name from the StackName isn't practical.Description of changes:
To make building stacks that nest this guidance practical, proposing these updates:
Now, by nesting the solution in a parent stack something like this:
...The parent stack can e.g. set up state machines referencing
PipelineStack.Outputs.CreateDatasetGroupStateMachineArn, and usePipelineStack.Outputs.StackNameif necessary.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.