AWS released the latest FreeRTOS kernel that includes additional preconfigured example projects for Armv8-M microcontrollers. The preconfigured examples demonstrate the FreeRTOS Armv8-M port on Arm Cortex-M33, and now also on Arm Cortex-M23, hardware from Nuvoton, NXP, and STMicroelectronics.

AWS Security Token Service (STS)  now enables you to specify IAM managed policies as session policies to create fine-grained session permissions when a user assumes a role in AWS to create a session. With this launch, you have up to 10 full-sized policies to choose from that enable you to define more fine-grained session permissions.

This Quick Start automatically deploys the Agilisium Conversational BI Bot on the Amazon Web Services (AWS) Cloud in about 25 minutes. It provisions a web interface to interact with the BI bot by using AWS services such as Amazon Redshift, Amazon Lex, Amazon Simple Storage Service (Amazon S3), AWS Lambda, and Amazon Cognito.

You can now develop your AWS Lambda functions using Node.js v10. In addition to the leveraging new features in Node.js v10 such as the performance improvements in the V8 6.6 engine, Lambda functions written in Node.js 10 run on the latest generation of Amazon Linux, Amazon Linux 2 .

You can now launch and run Kubernetes clusters managed by Amazon Elastic Container Service for Kubernetes (EKS) into AWS VPCs with public (non-RFC1918) IP addresses.

The two companies are targeting the architectural lighting market. Meanwhile, OLEDWorks also teams up with Audi.

Starting today, Amazon EC2 C5d, M5, M5d, R5, and R5d instances are available in additional AWS regions:

• C5d, M5d (including bare metal), R5 bare metal, and R5d instances (including bare metal) are now available in the AWS GovCloud (US-East) region.
• M5d and R5d bare metal instances are now available in the AWS GovCloud (US-West) region.
• M5 and M5d bare metal instances are now available in the Asia Pacific (Tokyo) region.
• R5 and R5d bare metal instances are now available in the Asia Pacific (Sydney) region.

You can now share Amazon Machine Images (AMIs) encrypted with Customer-Managed Customer Master Keys (CMKs ) across accounts with a single API call . Additionally, you can also launch instances from shared encrypted AMIs in a single step.

Smart and connected luminaire architectures will benefit from a standardized version of DALI deployed internally between LED drivers and connectivity/sensor modules, and such a modular architecture offers flexibility in network options.

AWS OpsWorks for Chef Automate now supports Chef Automate 2, which is an upgrade that makes it much easier to explore the state of your infrastructure and has an even greater emphasis on compliance features than its predecessor. Chef Automate has been re-architectured using a Go-based microservice architecture and includes an enhanced web UI providing a streaming event feed, trend graphs and a rich query language.

Using Chef Automate 2, AWS OpsWorks for Chef Automate empowers you to uphold configuration compliance of any resource in your infrastructure. It comes with 149 prepared compliance profiles including Center for Information Security (CIS) profiles for 45 AWS resources. It also introduces a compliance profile for Secure Technical Implementation Guidelines (STIG), which is a security technical implementation guide developed by the Defense Information Systems Agency.

You are not limited to verify configuration compliance of AWS resources only. Through API integration with Chef InSpec, you can use AWS OpsWorks for Chef Automate to test and manage resource compliance in heterogeneous environments. From the unified Chef Automate dashboard, you can analyze infrastructure and compliance automation data spanning on-premise, AWS and other cloud environments.

In regard to configuration options, Chef Automate 2 brings preservation during backup and restore of any customization you perform of your Chef Automate settings, e.g. LDAP and SAML configuration. You can configure a data retention period which enables automatic removal of nodes that are not checking in anymore. An action that used to be manual.

As of today, all newly created OpsWorks servers will automatically get AWS OpsWorks for Chef Automate with Chef Automate 2. Existing customers already up and running with AWS OpsWorks for Chef Automate will within the next months be offered a migration path. From the OpsWorks console, it will be possible through a button-click to upgrade any existing Chef Automate server to Automate 2.

Should you be new to OpsWorks for Chef Automate and curious to experience it, it is easy to get started. By following this Getting Started walk-through, you can within 15 minutes be up and running with your first compliance profile and your first compliance check.