Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack deployment fails if stack name starts with AWS #74

Closed
4 of 6 tasks
mukitmomin opened this issue Dec 14, 2022 · 0 comments · Fixed by #76
Closed
4 of 6 tasks

Stack deployment fails if stack name starts with AWS #74

mukitmomin opened this issue Dec 14, 2022 · 0 comments · Fixed by #76
Labels
bug Something isn't working

Comments

@mukitmomin
Copy link
Member

mukitmomin commented Dec 14, 2022

Describe the bug
The stack deployment fails if the stack name starts with 'AWS'. Cloudformation throws an error when creating the AppRegistry construct. This might be a problem for customers that wish to use 'AWS' to deploy the solutions.

To Reproduce

  • Go to CloudFormation console
  • Click Create stack dropdown and select With new resources (standard)
  • Specify the template with the appropriate s3 url and click next
  • In the stack name field give any name starting with 'AWS', for example AwsStreamingSolution
  • Fill out the rest of the fields as appropriate and select Create Stack

This will start creating cloudformation resources, and eventually will throw an error while creating the AppRegistry resource, causing the stack deployment to rollback.

Expected behavior
The stack is expected to deploy successfully regardless of the stack name given by the customer.

Please complete the following information about the solution:

  • Version: v1.7.0

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0124) - AWS Streaming Data Solution for Amazon Kinesis. Version v1.0.0".

  • Region: all
  • Was the solution modified from the version published on this repository?
  • If the answer to the previous question was yes, are the changes available on GitHub?
  • Have you checked your service quotas for the sevices this solution uses?
  • Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

@mukitmomin mukitmomin added the bug Something isn't working label Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant