aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Make "Internal Failure" errors more explicit

Open
#607 0 comments 11 reactions 0 assignees View on GitHub
enhancement
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

## Make "Internal Failure" errors more explicit

## 2. Scope of request

When performing CloudFormation operations, the stacks sometimes fail with the error message *Internal Failure*. This can have multiple reasons like internal parsing failures, service disruptions etc. For me as a developer, it is hard to track the root cause and usually I will open a support ticket and often get help but I always need to wait.

## 3. Expected behavior

From a UX perspective, the error is not helpful so I would be so happy when the message could be more detailed, even if the client error is something like *Failed to parse template* or *Failed to connect to downstream service IAM*.

## 4. Suggest specific test cases

## 5. Helpful Links to speed up research and evaluation

Here is an example:

![Screenshot 2020-08-14 at 10 47 16](https://user-images.githubusercontent.com/39558817/90231486-8bd9a000-de1b-11ea-9c04-6fed45ee8694.png)

## 6. Category (required) - Will help with tagging and be easier to find by other users to +1

UX

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.