Amazon Managed Streaming for Apache Kafka (Amazon MSK) can now continuously stream Apache Kafka broker logs to Amazon Cloudwatch Logs, Amazon S3, or Amazon Elasticsearch Service via Amazon Kinesis Data Firehose. With access to broker logs, customers can more easily troubleshoot and understand the performance of their applications that use Amazon MSK clusters as a data store. Broker Logs are available for both new and existing clusters and can be enabled from the Amazon MSK Console or AWS CLI. To learn how to setup broker log delivery, see the Amazon MSK broker logs documentation .

Amazon RDS for MariaDB now supports MariaDB 10.3 in AWS GovCloud (US) Regions. MariaDB 10.3 offers improved Oracle compatibility, support for querying historical states of the database, features that increase flexibility for developers and DBAs, and improved manageability.

You can now use Amazon CloudWatch to monitor metrics and logs related to AWS Chatbot. You can see metrics and create alarms for the events going to Slack and Amazon Chime via AWS Chatbot, such as the number of processed events, delivery failures, throttled events, and others. You can see details of events and troubleshoot failures by enabling Amazon CloudWatch Logs for your AWS Chatbot configurations. Using logs, you can see the raw event as well as the details of unsuccessful deliveries, throttling, and other failures that will help you troubleshoot AWS Chatbot configurations. 

You can now assign AWS resource tags to Spot Fleet requests on creation to more easily identify their purpose. For example, you can use tags to identify all Spot Fleet requests used by a particular department, project, or application. 

The AWS Certified Solutions Architect – Associate certification validates the ability to design and deploy well-architected solutions on AWS that meet customer requirements.  

You can now use AWS Step Functions to log workflow execution history to CloudWatch Logs, which make it faster and easier to monitor event-driven, serverless workflows. You can select different levels of logging, and also have the ability to exclude the logging of a workflow’s payload.  

Amazon Managed Apache Cassandra Service (MCS), a scalable, highly available, and managed Apache Cassandra–compatible database service, now enables you to add new columns to existing tables. 

Amazon CloudFront customers in China can now get detailed information about their CloudFront usage and activity by using CloudFront Reports in the AWS Management Console. Customers in China can use the CloudFront Cache Statistics Report to see total requests, the percentage of viewer requests by result type, bytes transferred, HTTP status codes, and the percentage of GET requests that did not finish downloading. The CloudFront Popular Objects Report shows the 50 most popular objects and statistics about those objects. The CloudFront Top Referrers Report shows the top 25 referrers and the number of requests from each referrer. The CloudFront Usage Report shows the number of requests and data transferred by protocol or destination. The CloudFront Viewers Report shows the breakdown of viewers by devices, browsers, operating systems, and locations. These reports are available to all CloudFront customers at no additional cost. To get started with CloudFront in China, go to Amazon CloudFront . For documentation, see CloudFront Reports in the Console in the Amazon CloudFront Developer Guide.

Amazon Elastic Container Service now supports reading AWS Secrets Manager secrets with a specific version or from a key within a JSON object for tasks using the EC2 launch type. This gives you more granular control to reference sensitive information such as database credentials, tokens, or configuration variables for your applications on Amazon ECS. Previously, you could only load the latest version of a secret and could not read secrets from JSON objects directly. Now, you can now load a secret by specifying a particular version instead of the latest version by default. Additionally, you can now load a secret from a specific key within a JSON object.

Amazon EC2 Auto Scaling now publishes notifications to the AWS Personal Health Dashboard and AWS Health API when EC2 instances fail to launch in one of your Auto Scaling groups due to a missing launch template or security group. This gives you actionable feedback to review and update the Auto Scaling group.