9/24/2024, 12:00:00 AM ~ 9/25/2024, 12:00:00 AM (UTC)

Recent Announcements

AWS Resilience Hub extends support for Amazon ElastiCache

AWS Resilience Hub has expanded its capabilities to assess applications that include Amazon ElastiCache. Resilience Hub serves as a centralized platform to define, validate, and monitor the resilience of your applications, helping you avoid unnecessary downtime because of software, infrastructure, or operational disruptions. For applications using Amazon ElastiCache, including ElastiCache Serverless and Global Datastores, AWS Resilience Hub now provides enhanced resilience recommendations. These include guidelines for Region and multi-region setups, as well as strategies for Availability Zone and Multi-AZ deployments, resource grouping, and backup. AWS Resilience Hub also offers a set of AWS CloudWatch alarms specifically for Amazon ElastiCache, giving customers improved control over their resilience posture.\n The new capabilities are available in all of the AWS Regions where Resilience Hub is supported. See the AWS Regional Services List for the most up-to-date availability information. To learn more about Resilience Hub, visit the product page or technical documentation.

Amazon Redshift data sharing governed through AWS Lake Formation is now available in 11 additional regions

AWS Lake Formation’s centralized access control and permission for Amazon Redshift data sharing is now available in 11 additional regions. You can manage permission grants, view access controls, and audit permissions on the tables and views in the Redshift datashares using Lake Formation APIs and the AWS Management Console. Furthermore, Lake Formation supports trusted identity propagation with AWS IAM Identity Center, allowing you to leverage Lake Formation to manage permissions to datashares for specific users and groups defined in your Identity Provider (IdP).\n AWS Lake Formation managed data sharing improves the security of your data by enabling data lake administrators in Lake Formation to manage granular entitlements such as table-level, column-level, or row-level access to tables and views being shared in Redshift data sharing. You can also apply AWS Lake Formation tag-based access control to Redshift data sharing, which simplifies management of data access across multiple AWS services and accounts through centralized tag-based policies. With trusted identity propagation, end-users’ access and actions are authorized based on their user and group memberships when they query the data sharing from a consumer data warehouse. AWS Lake Formation’s centralized access control and permission for Redshift data sharing is available the following 11 additional regions: Canada West (Calgary), Middle East (UAE), Asia Pacific (Hyderabad), Asia Pacific (Melbourne), Israel (Tel Aviv), Asia Pacific (Osaka), Asia Pacific (Hong Kong), Middle East (Bahrain), Europe (Milan), Africa (Cape Town), Asia Pacific (Jakarta). To learn more, visit AWS Lake Formation database developer guide, blog and demo.

Valkey GLIDE v1.1, a client for Valkey and Redis OSS, now supports Node.js

Today, we are announcing Node.js support for Valkey General Language Independent Driver for Enterprise (GLIDE). GLIDE is an open source client library for Valkey, an open source key-value data store that supports a variety of workloads such as caching and message queues. With this launch, GLIDE supports Java, Python, and Node.js. GLIDE is one of the official client libraries for Valkey and it supports all Valkey commands. GLIDE supports Valkey versions 7.2 and 8.0, as well as Redis open-source versions 6.2, 7.0, and 7.2.\n Valkey GLIDE is designed for reliability, optimized performance, and high-availability, for connecting to a Valkey or Redis OSS datastore. It is pre-configured with best practices learned from over a decade of operating Redis OSS-compatible services used by thousands of customers. To ensure consistency in application development and operations, GLIDE is implemented using a core driver framework, written in Rust, with language specific extensions. This design ensures consistency in features across languages, and reduces overall complexity. As of today, GLIDE is available for Java, Python, and Node.js, with support for additional languages actively under development. Valkey GLIDE is open source, permissively licensed (Apache 2.0 license), and it can be used with Amazon ElastiCache and Amazon MemoryDB. You can get started by downloading it from the major open source package managers. Learn more about it in this blog post, and submit contributions on the Valkey GLIDE GitHub repository.

AWS Resource Explore now supports discovery of all tagged AWS resources

AWS Resource Explorer introduced a new search operator that powers the complete discovery of tagged AWS resources across Services, AWS Regions, and AWS accounts.\n Customers use Resource Explorer to discover both tagged and untagged resources for resource types with full Resource Explorer support. Starting today, customers can specifically request to query all of their tagged resources, regardless of whether the resource types are fully supported by Resource Explorer. This feature immediately improves resource discovery coverage for customers by including resources fully supported by Resource Explorer, as well as any tagged resource from any service. To use this new feature, customers add the operator “tag:all” to any Resource Explorer query. Discovery of all tagged resources is supported in the AWS management console’s unified search bar, the Resource Explorer console, and the AWS SDKs and CLI. To learn more about this new search capability, please visit our search query syntax documentation. To start using the new search capability filter, visit the AWS Resource Explorer console. This feature is available in all AWS Commercial Regions.

Amazon S3 to apply a default minimum object size for S3 Lifecycle transition rules

Amazon S3 is beginning to apply a default minimum object size of 128 KB for S3 Lifecycle transition rules to any S3 storage class. This change can help optimize your transition costs for datasets with many kilobyte-sized objects by reducing the number of transition requests. You can override this new default and customize the minimum object size for S3 Lifecycle transition rules to any value.\n Using S3 Lifecycle filters, you can create custom rules to transition objects based on prefix, tags, and object sizes. While the object size filter for your existing S3 Lifecycle rules will not automatically change, this new default behavior will be applied to any new or modified S3 Lifecycle configuration. This change does not impact objects that have already transitioned using S3 Lifecycle. We have started deploying this S3 Lifecycle default to all AWS Regions and deployment will complete in the coming days. To learn more, visit the S3 User Guide.

WorkSpaces Secure Browser now supports FIPS 140-3 validated cryptography

Today, AWS End User Computing Services announced that customers can use Federal Information Processing Standard 140-3 (FIPS) validated cryptography endpoints with their WorkSpaces Secure Browser portals. FIPS 140-3 is a U.S. and Canadian government standard that specifies the security requirements for cryptographic modules that protect sensitive information.\n WorkSpaces Secure Browser FIPS endpoints use FIPS-validated cryptographic standards, which may be required for certain sensitive information or regulated workloads. To use a FIPS-validated connection for your portal, specify a FIPS endpoint when creating a portal using the AWS Command Line Interface (AWS CLI). You can use FIPS endpoints with any new portals at no additional charge. If you are new to WorkSpaces Secure Browser you can get started by visiting the pricing page and adding the Free Trial offer to your AWS account. Then, go to the Amazon WorkSpaces Secure Browser console and create your portal, today.

Amazon Managed Grafana now supports silences for Grafana alerts

You can now use silences to suppress alert notifications for Grafana alerts in Amazon Managed Grafana. Grafana alerts enable you to proactively monitor your data and receive notifications about critical issues in real time. Silences allow you to temporarily disable notifications from specific alerts, for a specified duration.\n Silences reduce alert fatigue during scheduled maintenances, operational events or when dealing with known issues, without disabling the underlying alert rules. You can silence your Grafana alert notifications based on alert labels or by directly silencing notifications for a specific Grafana alert rule. This feature is supported on all Amazon Managed Grafana workspaces running Grafana version 10.4, across all AWS regions where Amazon Managed Grafana is generally available. Check out the Amazon Managed Grafana user guide for detailed documentation.

AWS Blogs

AWS Japan Blog (Japanese)

AWS Big Data Blog

Containers

AWS Database Blog

AWS HPC Blog

The Internet of Things on AWS – Official Blog

AWS Machine Learning Blog

Networking & Content Delivery

AWS Security Blog

AWS Storage Blog

Open Source Project

AWS CLI

AWS CDK

Amplify for iOS

Amplify for Android

Bottlerocket OS