Amazon Personalize now makes it easier to modify datasets by allowing customers to add columns to an existing schema. Amazon Personalize uses datasets provided by customers to train custom personalization models on their behalf. Customers modify existing datasets to add new filtering columns for enhanced business logic and to add new columns that can improve model training. Previously, to add new columns customers would need to reproduce existing resources starting at the dataset level. With this feature, customers can quickly update their schema to append an additional column without having to reproduce resources.

AWS Database Migration Service (AWS DMS) now supports Amazon Redshift Serverless as a target endpoint. With this new support, you can securely migrate your data to Redshift Serverless, where it can be stored, queried, and analyzed without the need to provision or manage infrastructure.

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) M7g and R7g instances are now available in AWS Regions Europe (Frankfurt), Asia Pacific (Tokyo) and Asia Pacific (Sydney). These instances are powered by AWS Graviton3 processors and built on the AWS Nitro System. AWS Graviton3 processors provide up to 25% better compute performance compared to AWS Graviton2 processors. The AWS Nitro System is a collection of AWS designed hardware and software innovations that deliver efficient, flexible, and secure cloud services with isolated multi-tenancy, private networking, and fast local storage. 

AWS Proton introduces deployment history, a new feature that provides greater visibility into cloud infrastructure deployment events. Platform engineers use Proton to define infrastructure as code patterns for their services and manage updates for services across shared resource environments. Proton deployment history makes it easier to see when deployments are initiated, what resources they target, and provides a simple way to track deployment trends over time.

Amazon CloudFront announces support for 3072-bit RSA certificates. Customers can now associate their 3072-bit RSA certificates with CloudFront distributions to enhance communication security between clients and CloudFront edge locations.

With Amazon S3 Inventory, you can now easily review your access control lists (ACLs) on all of your objects to simplify review of access permissions. ACLs were the original way to manage object access when S3 launched in 2006. Now, when migrating to IAM-based bucket policies for access control, you can easily review all of the object ACLs in your buckets before enabling S3 Object Ownership.

We are excited to announce that Amazon EMR on EKS now supports programmatic execution of Jupyter notebooks when running interactive workloads via managed endpoints. Amazon EMR on EKS enables customers to run open-source big data frameworks such as Apache Spark on Amazon EKS. Amazon EMR on EKS customers can setup and use a managed endpoint (available in preview) to run interactive workloads using integrated development environments (IDEs) such as EMR Studio . 

AWS Batch now supports Linux ARM64 and Windows x86 containers in AWS Fargate. This feature helps simplify the adoption of modern container technology for AWS Batch customers by expanding their architecture options for scheduling Linux ARM64 and Windows x86 containers in Fargate compute environments. Support for ARM64 architecture also gives customers sustainability benefits of Graviton instances in Fargate which can help improve price/performance over comparable x86-based instances for a variety of workloads including high performance computing.

Amazon Connect now provides APIs to programmatically delete routing profiles and queues. You can now remove routing profile and queue resources that are no longer applicable, streamlining your contact center as requirements change and you adapt to new strategies for call flows, agent groups and other routing configurations. Deleting unused resources also frees up capacity in your service limits, giving you room to create new routing profiles and queues.

Once upon a time there was an expectation of single chip mobile telephones. In 1999, Lucent Technologies was planning a single chip solution for ‘Internet telephones’. Internet telephones connected to a single Ethernet outlet and sent data and voice through the same cable. Lucent’s chip was to combine 13 electronic functions and reduce the number …

The post The One-Chip Mobile Phone appeared first on Electronics Weekly .