11/19/2024, 12:00:00 AM ~ 11/20/2024, 12:00:00 AM (UTC)

Recent Announcements

AWS AppSync GraphQL APIs now support data plane logging to AWS CloudTrail

Today, AWS AppSync announced support for logging GraphQL data plane operations (query, mutation, and subscription operations and connect requests to your real-time WebSocket endpoint) using AWS CloudTrail, enabling customers to have greater visibility into GraphQL API activity in their AWS account for best practices in security and operational troubleshooting. AWS AppSync GraphQL is a serverless GraphQL service that gives application developers the ability to access data from multiple databases, micro-services, and AI models with a single GraphQL API request.\n CloudTrail captures API activities related to AWS AppSync GraphQL APIs as events, including calls from the AWS console and calls made programmatically to the AWS AppSync GraphQL API endpoints. Using the information that CloudTrail collects, you can identify a specific request to an AWS AppSync GraphQL API, the IP address of the requester, the requester’s identity, and the date and time of the request. Logging AWS AppSync GraphQL APIs using CloudTrail helps you enable operational and risk auditing, governance, and compliance of your AWS account. To opt-in for CloudTrail logging you can simply configure logging on your data stream using the AWS CloudTrail Console or by using CloudTrail APIs. Logging data plane AWS AppSync GraphQL APIs using AWS CloudTrail is now available in all commercial AWS Regions where AppSync is available. To learn more about logging data plane APIs using AWS CloudTrail, see AWS Documentation. For more information about CloudTrail, see the AWS CloudTrail User Guide.

Amazon OpenSearch Serverless now supports point in time (PIT) search

Amazon OpenSearch Serverless has added support for Point in Time (PIT) search, enabling you to run multiple queries against a dataset fixed at a specific moment. This feature allows you to maintain consistent search results even as your data continues to change, making it particularly useful for applications that require deep pagination or need to preserve a stable view of data across multiple queries.\n Point in time search supports both forward and backward navigation through search results, ensuring consistency even during ongoing data ingestion. This feature is ideal for e-commerce applications, content management systems, and analytics platforms that require reliable and consistent search capabilities across large datasets. Point in time search on Amazon OpenSearch Serverless is now available in 15 regions globally: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe West (Paris), Europe West (London), Asia Pacific South (Mumbai), South America (Sao Paulo), Canada Central (Montreal), Asia Pacific (Seoul). and Europe (Zurich). Please refer to the AWS Regional Services List for more information about Amazon OpenSearch Service availability. To learn more about OpenSearch Serverless, see the documentation.

Introducing Binary Embeddings for Titan Text Embeddings model in Amazon Bedrock

Amazon Titan Text Embeddings V2 now supports Binary Embeddings. With Binary Embeddings, customers can reduce the storage cost for their Retrieval Augmented Generation (RAG) applications while maintaining similar accuracy of regular embeddings.\n Amazon Titan Text Embeddings model generates semantic representations of documents, paragraphs, and sentences, as 1,024 (default), 512, or 256 dimensional vector. With Binary Embeddings, Titan Text Embeddings V2 will represent data as binary vectors with each dimension encoded as a single binary digit (0 or 1). This binary representation converts high-dimensional data into a more efficient format for storage in Amazon OpenSearch Serverless in Bedrock Knowledge Bases for cost-effective RAG applications. Binary Embeddings is supported in Titan Text Embeddings V2, Amazon OpenSearch Serverless and Amazon Bedrock Knowledge Bases in all regions where Amazon Titan Text Embeddings V2 is supported. To learn more, visit the documentation for Binary Embeddings.

AWS support case management is now available in AWS Chatbot for Microsoft Teams and Slack

AWS Chatbot announces general availability of AWS Support case management in Microsoft Teams and Slack. AWS customers can now use AWS Chatbot to monitor AWS support cases updates and respond to them from chat channels.\n When troubleshooting issues, customers need to stay informed up-to-date on the latest support case updates in a place where they are collaborating. Previously, customers had to install a separate app or navigate to the Console to manage support cases. Now, customers can monitor and manage support cases from Microsoft Teams and Slack with AWS Chatbot. To manage support cases from chat channels with AWS Chatbot, customers subscribe a chat channel to support case events published in EventBridge. As new case correspondences get added, AWS Chatbot sends the support case update notifications to the configured chat channels. Channel members can the use action buttons on the notifications to view the latest case updates and respond to them without leaving the chat channel. To interact with support cases in chat channels, you must have a Business, Enterprise On-Ramp, or Enterprise Support plan. The case management in chat applications is available at no additional cost in AWS Regions where AWS Chatbot is offered. Get started with AWS Chatbot by visiting the AWS Management Chatbot Console and by downloading the AWS Chatbot app from the Microsoft Teams marketplace or Slack App Directory. Visit the AWS Chatbot product page and Managing AWS Support cases from chat channels in AWS Chatbot documentation to learn more.

Amazon EFS now supports cross-account Replication

Amazon EFS now supports cross-account Replication, allowing customers to replicate file systems between AWS accounts. EFS Replication enables you to easily maintain an up-to-date replica of your file system in the AWS Region of your choice. With this launch, EFS Replication customers can meet business continuity, multi-account disaster recovery, and compliance requirements by automatically keeping replicas of their file data in separate accounts.\n Customers often use multiple AWS accounts to help isolate and manage business applications and data for operational excellence, security, and reliability. Starting today, you can use EFS Replication to replicate your file system to another account in any AWS region. This eliminates the need to set up custom processes to synchronize EFS data across accounts, enhancing resilience and reliability in distributed environments. EFS cross-account Replication is available for all existing and new EFS file systems in all commercial AWS Regions. To learn more, visit the Amazon EFS Documentation and get started by configuring EFS Replication in just a few clicks using the Amazon EFS Console, AWS CLI, AWS CloudFormation, and APIs.

Amazon EKS enhances Kubernetes control plane monitoring

Amazon EKS enhances visibility into the Kubernetes control plane by offering new intuitive dashboards in EKS console and providing a broader set of Kubernetes control plane metrics. This enables cluster administrators to quickly detect, troubleshoot, and remediate issues. All EKS clusters on Kubernetes version 1.28 and above will now automatically display a curated set of dashboards visualizing key control plane metrics within the EKS console, making it easy to observe the health and performance of the control plane. Additionally, a broader set of control plane metrics are made available in Amazon CloudWatch and in a Prometheus endpoint, providing customers with the flexibility to utilize their preferred monitoring solution — be it Amazon CloudWatch, Amazon Managed Service for Prometheus, or third-party monitoring tools.\n Newly introduced pre-configured dashboards in the EKS console provide cluster administrators with visual representations of key control plane metrics, enabling rapid assessment of control plane health and performance. Additionally, the EKS console dashboards now integrate with Amazon CloudWatch Log Insights queries, surfacing critical insights from control plane logs directly within the console. Finally, customers now get access to Kubernetes control plane metrics from kube-scheduler and kube-controller-manager, in addition to the existing API server metrics. The new set of dashboards and metrics are available at no additional charge in all AWS commercial regions and AWS GovCloud (US) Regions. To learn more, visit the launch blog post or EKS user guide.

Amazon OpenSearch Service now scales to 1000 data nodes on a single cluster

Amazon OpenSearch Service now enables you to scale a single cluster to 1000 data nodes (1000 hot nodes and/or 750 warm nodes) and enables you to manage 25 petabytes of data (10 Petabytes in hot nodes and further 15 Petabytes in warm nodes). You no longer need to setup multiple clusters for workloads that require more than 200 data nodes or more than 3 Petabytes of data.\n Today, for workloads of more than 3 to 4 petabytes of data, you need to create multiple clusters in OpenSearch Service. This may have required you to refactor your applications or business logic to work with your workload split across multiple clusters. In addition, every cluster requires its own configuration, management, and monitoring, adding to the operational overhead. With this launch, you can scale a single cluster up to 1000 nodes, or 25 petabytes of data, removing the operational overhead that comes with managing multiple clusters. To scale a cluster beyond 200 nodes, you have to request an increase through Service Quota, after which you can modify your cluster configuration using the AWS Console, AWS CLI, or the AWS SDK. Depending on the size of the cluster, OpenSearch Service will recommend configuration pre-requisites across data nodes, cluster manager nodes, and coordinator nodes. For more information, refer to the documentation. The new limits are available to all OpenSearch Service clusters running OpenSearch 2.17 and above in all AWS regions where Amazon OpenSearch Service is available. Please refer to the AWS Region Table for more information about Amazon OpenSearch Service availability.

AWS Amplify launches the full-stack AI kit for Amazon Bedrock

Today, AWS announces the general availability of the AWS Amplify AI kit for Amazon Bedrock, the quickest way for fullstack developers to build web apps with AI capabilities such as chat, conversational search, and summarization. The Amplify AI kit allows developers to easily leverage their data to get customized responses from Amazon Bedrock AI models. The Amplify AI kit allows anyone with knowledge of JavaScript or TypeScript, and web frameworks like React or Next.js, to add AI experiences to their apps, without any prior machine learning expertise.\n The AI kit offers the following capabilities:

A pre-built, fully customizable React UI component that offers a real-time, streaming chat experience along with features like UI responses instead of plain-text, chat history, and resumable conversations.

A type-safe client that provides secure server-side access to Amazon Bedrock.

Secure, built-in capabilities to share user context (e.g. data the user can access) with Amazon Bedrock models.

Define tools with additional context that can be invoked by the models.

A fullstack TypeScript developer experience layered on Amplify Gen 2 and AWS AppSync.

To get started with the AI kit, see our launch blog.

Amazon OpenSearch Serverless now supports Binary Vector and FP16 cost savings features

We are excited to announce that Amazon OpenSearch Serverless now is supporting Binary Vector and FP16 compression helping reduce costs by lowering the memory requirements. It also lowers the latency, improve performance with acceptable accuracy tradeoff. OpenSearch Serverless is a serverless deployment option for Amazon OpenSearch Service that makes it simple to run search and analytics workloads without the complexities of infrastructure management. OpenSearch Serverless’ compute capacity used for data ingestion, search, and query is measured in OpenSearch Compute Units (OCUs).\n The support for OpenSearch Serverless is now available in 17 regions globally: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe West (Paris), Europe West (London), Asia Pacific South (Mumbai), South America (Sao Paulo), Canada Central (Montreal), Asia Pacific (Seoul). Europe (Zurich), AWS GovCloud (US-West), and AWS GovCloud (US-East). Please refer to the AWS Regional Services List for more information about Amazon OpenSearch Service availability. To learn more about OpenSearch Serverless, see the documentation.

YouTube

AWS Developer Live Show (Japanese)

AWS Blogs

AWS Japan Blog (Japanese)

AWS Open Source Blog

AWS Big Data Blog

AWS Compute Blog

Containers

AWS Database Blog

AWS Developer Tools Blog

AWS DevOps & Developer Productivity Blog

Front-End Web & Mobile

AWS HPC Blog

AWS for Industries

AWS Machine Learning Blog

AWS for M&E Blog

AWS Messaging & Targeting Blog

Networking & Content Delivery

AWS Security Blog

Open Source Project

AWS CLI

AWS CDK

Amplify UI