17 years ago Electronics Weekly published this list of the biggest UK electronics companies:

This story continues at How Times Change

Or just read more coverage at Electronics Weekly

This is the Electronica that was. Check out Electronica 2018 in condensed form, with a flavour of the news and views from the show floor in Munich.

This story continues at Electronica: Video Overview – It’s a wrap!

Or just read more coverage at Electronics Weekly

Biennial electronics industry event in Munich hosts LED Trends Forum and features many SSL-centric demos focused primarily on the automotive lighting application area; while Instrument Systems demos a new photometric test system.

Don’t worry; it’s coming, backers of the wireless smart lighting technology reassure the LuxLive crowd.

You can now tag your Amazon Elastic Container Service (Amazon ECS) and AWS Fargate resources such as services, task definitions, tasks, clusters, and container instances . This will enable you to better allocate cost, improve visibility into your workloads, easily search and identify your containerized applications, implement programmatic infrastructure management actions, and define fine-grained resource-level permissions.

Many ECS customers are managing thousands of resources such as task definitions, services, tasks, and clusters, spread across different teams, products, business units, and environments. Without tagging, it was difficult to manage the entire infrastructure and the underlying cost in a systematic manner. Now, you can tag your ECS resources at creation or at runtime using the ECS APIs and Console. Customers using the AWS Fargate launch-type can now easily allocate the cost of their ECS Tasks using tags. For customers using the EC2 launch-type, ECS now provides detailed ECS Tasks usage data in the Cost & Usage Report, which customers can use to allocate the cost of the underlying EC2 instances.

To take advantage of tagging, you will need to opt-in to the new Amazon Resource Names (ARN) and resource identifiers (ID) format for tasks, container instances, and services. These new ARNs and IDs are necessary to introduce the new tagging functionality and all its underlying benefits.

Additional information about the new ARN and ID formats can be found in the FAQ and documentation . You can also read our post to learn more about moving to new ARN and ID. If you have questions, please reach out to your account team or contact AWS Support on the community forums or through AWS Premium Support. To opt in, visit the ECS page of your AWS console. Resource tagging is currently not available in the GovCloud (US-East) region.  

You can now use new task definition conventions to easily inject sensitive information stored in AWS Systems Manager Parameter Store into containers managed by Amazon Elastic Container Service (Amazon ECS).

As customers build applications, they need to reference sensitive information such as database credentials, tokens, configuration variables or SSH keys. Previously, customers had to directly reference this sensitive information in the task definition or manage your own run-time secrets with custom solutions to decouple secrets from core application logic stored in container images.

Now, you have new task definition conventions for exposing sensitive information stored in AWS Systems Manager Parameter Store to container instances. You can still set, get, update and delete secrets via existing AWS Systems Manager Parameter Store APIs. However, task definitions can now be used to designate which of those secrets should be exposed to what containers.

To learn more about how to integrate ECS with Parameter Store, read our documentation .
 

The AWS Deep Learning AMIs  for Ubuntu  and Amazon Linux  now come with an optimized build of TensorFlow 1.12  and support for MMS 1.0 , a Model Server for Apache MXNet  that provides a flexible and easy way to serve deep learning models exported from MXNet  or the Open Neural Network Exchange (ONNX) . For Amazon EC2 C5 instances, Deep Learning AMIs deploy compute-optimized TensorFlow built with Intel Advanced Vector Extensions (AVX instruction sets) to speed up the performance of vector and floating point operations. The AMIs also come pre-configured to leverage Intel Math Kernel Library for Deep Neural Networks (MKL-DNN). Training a ResNet-50 benchmark with the synthetic ImageNet dataset using our optimized build of TensorFlow 1.12 on a c5.18xlarge instance type was 13x faster than training using the stock TensorFlow 1.12 binaries.

Amazon Transcribe is an automatic speech recognition (ASR) service that makes it easy for you to add a speech-to-text capability to your applications. Amazon Transcribe now supports transcription of audio in the following new languages: British English, Australian English, and Canadian French. These languages expand upon the existing two languages already available in Amazon Transcribe: US English and US Spanish.

Amazon Comprehend for advanced text analytics now includes Custom Classification.

With the introduction of Amazon S3 Block Public Access, securing your S3 data has never been easier. With a few clicks in the S3 management console, you can apply S3 Block Public Access to every bucket in your account – both existing and any new buckets created in the future – and make sure that there is no public access to any object. By default, new S3 bucket settings do not allow public access, but customers can modify these settings to grant public access using policies or object-level permissions. The Amazon S3 Block Public Access settings override S3 permissions that allow public access, making it easy for the account administrator to set up a centralized control to prevent variation in security configuration regardless of how an object is added or a bucket is created. These settings are auditable, providing a further layer of control, using AWS Trusted Advisor bucket permission checks, AWS CloudTrail logs, Amazon Macie and Amazon CloudWatch.