[
    {
        "type": "api-change",
        "category": "IoT",
        "description": "As part of this release, we are extending capability of AWS IoT Rules Engine to support IoT Cloudwatch log action. The IoT Cloudwatch log rule action lets you send messages from IoT sensors and applications to Cloudwatch logs for troubleshooting and debugging."
    },
    {
        "type": "api-change",
        "category": "LexModelBuildingService",
        "description": "Amazon Lex now supports tagging for bots, bot aliases and bot channels. "
    },
    {
        "type": "api-change",
        "category": "EC2",
        "description": "Documentation updates for EC2"
    },
    {
        "type": "api-change",
        "category": "ApiGatewayV2",
        "description": "Amazon API Gateway HTTP APIs is now generally available. HTTP APIs offer the core functionality of REST API at up to 71% lower price compared to REST API, 60% lower p99 latency, and is significantly easier to use. As part of general availability, we added new features to route requests to private backends such as private ALBs, NLBs, and IP\/ports. We also brought over a set of features from REST API such as Stage Variables, and Stage\/Route level throttling. Custom domain names can also now be used with both REST And HTTP APIs."
    },
    {
        "type": "api-change",
        "category": "SecurityHub",
        "description": "The AWS Security Finding Format is being augmented with the following changes. 21 new resource types without corresponding details objects are added. Another new resource type, AwsS3Object, has an accompanying details object. Severity.Label is a new string field that indicates the severity of a finding. The available values are: INFORMATIONAL, LOW, MEDIUM, HIGH, CRITICAL. The new string field Workflow.Status indicates the status of the investigation into a finding. The available values are: NEW, NOTIFIED, RESOLVED, SUPPRESSED."
    }
]