You can now publish logs from your Amazon RDS for SQL Server database to CloudWatch Logs. Supported logs include both agent logs and error Logs. Publishing these logs to CloudWatch allows you to maintain continuous visibility into database errors and activity. For example, Customers can set up CloudWatch Alarms to notify them on frequent restarts that are recorded in the error log. Similarly, Customers can create alarms for errors or warnings recorded in SQL Server Agent logs related to their SQL agent jobs.

Starting today you can now launch X1 and X1e instance types using Amazon RDS for SQL Server. 

Today, AWS Secrets Manager announced two changes that make it easier to rotate secrets automatically. First, customers can set up automatic rotation for Redshift clusters and DocumentDB instances via AWS CloudFormation easily. Customers can do this by using the SecretTargetAttachment resource to associate a Redshift cluster or Document DB instance with the corresponding secret created in Secrets Manager. Second, customers can set up rotation easily by specifying a serverless application. AWS will automatically create the Lambda function, IAM role, and IAM permissions needed to execute the rotation. To get started, view the CloudFormation examples to schedule secrets for rotation.

Amazon EC2 Instance Connect is now available in the AWS Europe (Stockholm) Region. 

AWS Security Hub now supports integrations with Aqua Security Cloud Native Security Platform, AttackIQ Platform, BigID Enterprise, Capitis Solutions C2VS, Caveonix RiskForesight, and DisruptOps are now available. Each of these integrations sends findings from their respective product to Security Hub using the AWS Security Finding Format. Customers can view findings from these products in Security Hub and take action on them.  

AWS CodeBuild adds support for Test Reporting giving you an effective and consistent view of your test executions in CodeBuild. Previously, you couldn’t visualize your test results on CodeBuild, making it harder for you to troubleshoot test failures. 

New features of AWS IoT Core, including Configurable Endpoints and Custom Domains, as well as enhancement to AWS IoT Core Custom Authentication, Custom Authorizer for MQTT Connections, make it easy to transition from self-managed infrastructure to fully managed AWS IoT services so you can improve scalability and reliability with few changes to your application code and minimal to no impact to devices already using your services. 

Alexa Voice Service (AVS) Integration is a new feature of AWS IoT Core that enables Alexa Voice to be produced on any type of connected device. AVS Integration for IoT Core reduces the cost of producing Alexa Built-in devices by up to 50% by offloading compute and memory intensive audio workloads to the cloud. With this reduction in production cost, customers can now cost-effectively build new categories of differentiated voice-enabled products such as light switches, thermostats, and small appliances. This allows consumers to talk directly to Alexa in new parts of their home, office, or hotel rooms for a truly ambient experience. 

You can now send data from AWS IoT Core directly to your own web services for processing without writing a single line of code. To do so, simply configure the new HTTP action by providing the HTTPS endpoint of your web service (e.g. https://example.com). After validating your ownership of the endpoint, AWS IoT Core will deliver the data via HTTP POST method.

AWS IoT Greengrass seamlessly extends AWS to edge devices so they can act locally on the data they generate, while still using the cloud for management, analytics, and durable storage. Starting today, developers using AWS IoT Greengrass can now package applications into Docker container images and deploy these seamlessly to edge devices. In addition, developers can collect, process, and export data streams, and manage the life cycle of data streams locally on devices.