6/7/2024, 12:00:00 AM ~ 6/10/2024, 12:00:00 AM (UTC)
Recent Announcements
Amazon Redshift Serverless is now available in the AWS Middle East (UAE) region
Amazon Redshift Serverless, which allows you to run and scale analytics without having to provision and manage data warehouse clusters, is now generally available in the AWS Middle East (UAE) region. With Amazon Redshift Serverless, all users, including data analysts, developers, and data scientists, can use Amazon Redshift to get insights from data in seconds. Amazon Redshift Serverless automatically provisions and intelligently scales data warehouse capacity to deliver high performance for all your analytics. You only pay for the compute used for the duration of the workloads on a per-second basis. You can benefit from this simplicity without making any changes to your existing analytics and business intelligence applications.\n With a few clicks in the AWS Management Console, you can get started with querying data using the Query Editor V2 or your tool of choice with Amazon Redshift Serverless. There is no need to choose node types, node count, workload management, scaling, and other manual configurations. You can create databases, schemas, and tables, and load your own data from Amazon S3, access data using Amazon Redshift data shares, or restore an existing Amazon Redshift provisioned cluster snapshot. With Amazon Redshift Serverless, you can directly query data in open formats, such as Apache Parquet, in Amazon S3 data lakes. Amazon Redshift Serverless provides unified billing for queries on any of these data sources, helping you efficiently monitor and manage costs.
Amazon CodeCatalyst now supports Bitbucket Cloud source code repositories
Amazon CodeCatalyst now supports the use of source code repositories hosted in Bitbucket Cloud in CodeCatalyst projects. This allows customers to use Bitbucket Cloud repositories with CodeCatalyst’s features such as its cloud IDE (Development Environments), Generative AI features such as Q feature development, and custom blueprints. Customers can also trigger CodeCatalyst workflows based on events in Bitbucket Cloud, view the status of CodeCatalyst workflows back in Bitbucket Cloud , and even block Bitbucket Cloud pull request merges based on the status of CodeCatalyst workflows.\n Customers want the flexibility to use source code repositories hosted in Bitbucket Cloud, without the need to migrate to CodeCatalyst to use its functionality. Migration is a long process and customers want to evaluate CodeCatalyst and its capabilities using their own code repositories before they decide to migrate. Support for popular source code providers such as Bitbucket Cloud is the top customer ask for CodeCatalyst. Now customers can use the capabilities of CodeCatalyst without the need for migration of source code from Bitbucket Cloud. This capability is available in regions where CodeCatalyst is available. There is no change to pricing. For more information, see the documentation or visit the Amazon CodeCatalyst website.
Amazon Data Firehose now supports integration with AWS Secrets Manager
Amazon Data Firehose (Firehose) now supports integration with AWS Secrets Manager (Secrets Manager) to configure secrets such as database credentials or keys to connect to streaming destinations such as Amazon Redshift, Snowflake, Splunk, and HTTP endpoints.\n Amazon Data Firehose needs to access a secret such as database credentials or keys to connect to a streaming destination. With this launch, Amazon Data Firehose can retrieve a secret from Secrets Manager instead of using a plain text secret in configuration to connect to the destination. By using Secrets Manager integration, you can ensure that secrets are not visible in plain text during Firehose stream creation workflow either in AWS Management Console or API parameters. This feature provides a more secure practice to store and maintain a secret in Firehose and allows you to leverage automatic secret rotation capability provided by Secrets Manager.
Amazon FSx for Lustre increases maximum metadata IOPS by up to 15x
Amazon FSx for Lustre, a service that provides high-performance, cost-effective, and scalable file storage for compute workloads, is increasing the maximum level of metadata IO operations per second (IOPS) you can drive on a file system by up to 15x, and now allows you to provision metadata IOPS independently of your file system’s storage capacity.\n A file system’s level of metadata IOPS determines the number of files and directories that you can create, list, read, and delete per second. By default, the metadata IOPS of an FSx for Lustre file system scales with its storage capacity. Starting today, you can provision up to 15x higher metadata performance per file system—independently of your file system’s storage capacity—allowing you to scale to even higher levels of performance, accelerate time-to-results, and optimize your storage costs for metadata-intensive machine learning research and high-performance computing (HPC) workloads. You can also update your file system’s metadata IOPS level with the click of a button, allowing you to quickly increase performance as your workloads scale.
Centrally manage member account root email addresses across your AWS Organization
Today, we are making it easier for AWS Organizations customers to centrally manage the root email address of member accounts across their Organization using the AWS Command Line Interface (CLI), AWS Software Development Kit (SDK), and AWS Organizations console. We previously released the Accounts SDK that enables Organizations customers to centrally and programmatically manage both primary and alternate contact information as well as the enabled AWS Regions for their accounts. In order to manage the root email address, customers were forced to login as root to manage the root email address of member accounts. Starting today, customers can use the same SDK to update the root email address of a member account from either the Organization’s management account (or delegated administrator), saving them the time and effort of logging into each account directly and allowing them to manage their Organization’s root addresses at scale. Additionally, this API will require customers to verify the new root email address using One Time Password (OTP) ensuring customers are using accurate email addresses for their member accounts. The root email address won’t change to the new email address until it has been verified.
Amazon API Gateway customers can easily secure APIs using Amazon Verified Permissions
Amazon Verified Permissions expanded support for securing Amazon API Gateway APIs, with fine grained access controls when using an Open ID connect (OIDC) compliant identity provider. Developers can now control access based on user attributes and group memberships, without writing code. For example, say you are building a loan processing application. Using this feature, you can restrict access to the “approve_loan” API to only users in the “loan_officer” group.\n Amazon Verified Permissions is a scalable fine-grained authorization service for the applications that you build. Verified Permissions launched a new feature to secure API Gateway REST APIs for customers using an OIDC compliant identity provider. The feature provides a wizard for connecting Verified Permissions with API Gateway and an identity provider, and defining permissions based on user groups. Verified Permissions automatically generates an authorization model and Cedar policies that allow only authorized user groups access to application’s APIs. The wizard deploys a Lambda authorizer that calls Verified Permissions to validate that the API request has a valid OIDC token and is authorized. Additionally, the lambda authorizer caches authorization decisions to reduce latency and cost. To get started, visit the Verified Permissions console, and create a policy store by selecting “Import using API Gateway and Identity Provider”. We have partnered with leading identity providers, CyberArk, Okta, and Transmit Security, to test this feature and ensure a smooth experience. This feature is available in all regions where Verified permissions is available. For more information visit the product page.
AWS Blogs
AWS Japan Blog (Japanese)
AWS Cloud Operations & Migrations Blog
AWS Database Blog
- Exploring new features of Apache TinkerPop 3.7.x in Amazon Neptune
- Turn petabytes of relational database records into a cost-efficient audit trail using Amazon Athena, AWS DMS, Amazon RDS, and Amazon S3
AWS DevOps Blog
AWS for Industries
AWS for M&E Blog
AWS Storage Blog
Open Source Project
AWS CLI
AWS CDK
Amplify for JavaScript
- tsc-compliance-test@0.1.39
- required-release: chore(release): Publish [skip release]
- 2024-06-06 Amplify JS release - aws-amplify@6.3.6
- @aws-amplify/storage@6.4.6
- @aws-amplify/pubsub@6.1.9
- @aws-amplify/predictions@6.1.10
- @aws-amplify/notifications@2.0.35
- @aws-amplify/interactions@6.0.34
- @aws-amplify/geo@3.0.35
- @aws-amplify/datastore-storage-adapter@2.1.37