Starting today, Amazon EC2 D3 instances, the latest generation of the dense HDD-storage instances, are available in the Europe (London) region.
Amazon Neptune announces support for SPARQL 1.1 Graph Store HTTP Protocol
Amazon Neptune announces support for SPARQL 1.1 Graph Store HTTP Protocol (GSP) for graphs using W3C’s Resource Description Framework (RDF). Using GSP on SPARQL 1.1 endpoints, customers now have an efficient method to interact with complete named graphs within a graph store. This can streamline building graph applications using Amazon Neptune and tools that support the W3C Recommendation GSP such as Apache Jena .
Amazon CloudWatch adds support for trimmed mean statistics
Amazon CloudWatch announces support for the trimmed mean statistic on CloudWatch Metrics. With trimmed mean statistics, customers gain visibility on the average performance of a metric without the noise of outliers. Trends in average performance represented by the trimmed mean can be visualized on CloudWatch Dashboards or used to set thresholds in alarms for proactive alerting.
Amazon Neptune ML is now generally available with support for edge predictions, automation, and more
Amazon Neptune ML, a machine learning capability for graphs that uses Graph Neural Networks (GNNs), is now generally available in all regions where Amazon Neptune is available. Using the Deep Graph Library (DGL) , an open-source library to which AWS contributes, Neptune ML automates the heavy lifting of selecting and training the best ML model for graph data. With Neptune ML, you can improve the accuracy of most predictions for graphs by over 50% when compared to making predictions using non-graph methods.
Amazon Neptune now supports the openCypher query language
Amazon Neptune announced support for openCypher , a popular query language for building applications with graph databases. Developers can now use openCypher with Amazon Neptune, giving them more choices to build or migrate graph applications to a highly available, secure, and fully managed graph database. Support for openCypher is compatible with our customers’ existing property graphs and developers can use both Apache TinkerPop Gremlin and openCypher queries within the same graph.
Amazon S3 on Outposts supports direct access for applications running outside the Outposts VPC
Amazon S3 on Outposts now supports the ability to create and access S3 objects on Outposts directly from your on-premises network. You can now configure S3 endpoints using your customer owned IP (CoIP) addresses and access your S3 objects from your on-premise network through the Outposts Local Gateway (LGW). With direct access, applications outside the Outposts Virtual Private Cloud (VPC) can now directly access data stored in S3 buckets on your Outposts.
Amazon S3 on Outposts adds two larger storage tiers
Amazon S3 on Outposts now offers two larger storage tiers: 240 TB and 380 TB. These new storage tiers help you meet your needs for workloads with larger object storage requirements, and add to the existing options of: 26 TB, 48 TB, and 96 TB storage tiers.
Amazon MQ now supports RabbitMQ version 3.8.17
You can now launch RabbitMQ 3.8.17 brokers on Amazon MQ. This patch update to RabbitMQ contains several fixes and enhancements compared to the previously supported version, RabbitMQ 3.8.11.
AWS IoT SiteWise Edge now generally available
Today, AWS announces the general availability of AWS IoT SiteWise Edge, a feature of AWS IoT SiteWise that makes it easy for industrial customers to collect, organize, process, and monitor equipment data on-premises (i.e. at the edge). SiteWise Edge software enables factory operators to get visibility into their equipment data and make decisions that help improve equipment uptime, product quality, and process efficiency.
Amazon EC2 Auto Scaling now lets you control which instances to terminate on scale-in
Amazon EC2 Auto Scaling now lets you control which instances to terminate during a scale-in event by allowing you to provide a custom function that selects which instances to terminate. Previously, you could use one of the predefined termination policies to determine which instances Auto Scaling would terminate. (For example, the OldestLaunchTemplate termination policy would terminate instances in order of their launch template age, oldest first.) Now, you can provide a custom Lambda function that indicates which instances are safe to terminate on scale in. This feature is useful for stateful applications where you want to control which instances Auto Scaling terminates so that your application is not disrupted on scale in.