Enable using MLOps guidance in nested stack #210
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_ops
solution 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
GetAtt
on 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.StackName
if necessary.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.