Adding suffix to resource names, so that resource creation does not fail #3
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.
While running both the templates. I encountered an error due to the resource names being the same.
So, I added the stack name as the suffix on the following resources causing problem
Old names:
RoleName: 'SSMforEC2'
InstanceProfileName: 'SSMforEC2InstanceProfile'
new names:
RoleName: !Sub SSMforEC2-${AWS::StackName}
InstanceProfileName: !Sub SSMforEC2InstanceProfile-${AWS::StackName}
what was SSMforEC2 will now be SSMforEC2-openvino / SSMforEC2-opea
CloudFormation stack names do not allow characters that are disallowed in IAM role names (e.g., /, *, spaces), using AWS::StackName as a suffix in an IAM role name will not cause issues related to invalid characters