When you import a resource to another stack, is an identical resource recreated or is the same resource being reused? In other words, can one resource belong to multiple stacks?
Hi, there. 👋 While we don't have an answer for you as yet, we've submitted your question for internal review. ⚙️ For any technical questions, feel free to reach out to our community of helpful specialists at re:Post: go.aws/aws-repost. ✍️ ^ZP
We have good news! Our service team responded with more information. When it comes to these operations, you import an existing resource into the stack along with the data it contains. One resource can not belong to multiple stacks. It will not give you the option to import a resource into a stack if it is already being managed by an existing stack. Please direct any further questions to our re:Post community: go.aws/aws-repost. 📝 ^ZP
Is there a way to edit or modify a failed stack that was trying to be imported? There are some resources that failed and would like to remove from this stack. When trying to go back and "edit" the stack its not available. Other than deleting the stack and starting over I don't see any other options
Sorry to hear that you've encountered issues. I was able to find a few CloudFormation official docs that cover this: go.aws/3TSvE4S & go.aws/3TQlotJ & go.aws/3TQcWum & go.aws/3TRL9tC. ⬅️📄 If these aren't quite what you're looking for, you can also check with our community of experts on re:Post for additional advice and suggestions: go.aws/aws-repost. 📮 ^TE
Great service. I was trying to find this sort of service in AWS and internet few months back when I am trying to figure out a inherited AWS account.
Glad it was helpful! 😀
Exactly what I have been looking for.
When you import a resource to another stack, is an identical resource recreated or is the same resource being reused? In other words, can one resource belong to multiple stacks?
Hi, there. 👋 While we don't have an answer for you as yet, we've submitted your question for internal review. ⚙️ For any technical questions, feel free to reach out to our community of helpful specialists at re:Post: go.aws/aws-repost. ✍️ ^ZP
We have good news! Our service team responded with more information. When it comes to these operations, you import an existing resource into the stack along with the data it contains. One resource can not belong to multiple stacks. It will not give you the option to import a resource into a stack if it is already being managed by an existing stack. Please direct any further questions to our re:Post community: go.aws/aws-repost. 📝 ^ZP
@@awssupport Thank you for the information!
No problem, happy to help! 😀 ^LG
Is there a way to edit or modify a failed stack that was trying to be imported? There are some resources that failed and would like to remove from this stack. When trying to go back and "edit" the stack its not available. Other than deleting the stack and starting over I don't see any other options
Sorry to hear that you've encountered issues. I was able to find a few CloudFormation official docs that cover this: go.aws/3TSvE4S & go.aws/3TQlotJ & go.aws/3TQcWum & go.aws/3TRL9tC. ⬅️📄 If these aren't quite what you're looking for, you can also check with our community of experts on re:Post for additional advice and suggestions: go.aws/aws-repost. 📮 ^TE
AWS firehose streams are not identified as resources when trying to create template using CloudFormation IaC Generator