ICE Errors for EC2

I apologize, but I don't have specific information about generating an "ICE error report" for EC2 instances as you've described. The term "ICE error" is not a standard AWS terminology for EC2 instances.

However, if you're looking to gather information about EC2 instances that have failed to start, there are a few approaches you can consider:

1. You can use Amazon CloudWatch to set up metrics and alarms for your EC2 instances. This would allow you to monitor instance status and receive notifications when instances fail to start.

2. AWS Config can be used to track configuration changes and maintain an inventory of your EC2 resources, including failed instance launches.

3. For detailed system-level information on Linux instances that have failed, you can use EC2Rescue for Linux or the sosreport tool. These tools can help collect logs and system information that might provide insights into why an instance failed to start.

4. The Amazon EC2 API provides error codes and messages when instances fail to launch. You can review these error responses to understand the reason for launch failures.

To get the specific details you're looking for (region, instance family, instance SKU, quantity of failed instances, date and time), you might need to combine data from multiple AWS services and potentially create a custom solution using AWS Lambda or another service to aggregate and format the data as needed.

If you're experiencing persistent issues with EC2 instances failing to start, it's recommended to contact AWS Support for personalized assistance. They can help you troubleshoot the specific problems you're encountering and provide guidance on how to collect and analyze relevant error data.
Sources
Collect logs from failed Amazon EC2 Linux instances | AWS re:Post
Error codes for the Amazon EC2 API - Amazon Elastic Compute Cloud