ACUVA

Your Accurate Search for New Technology

Amazon Q Developer introduces a new, simplified setup experience for Pro tier subscriptions

By

Today, we are excited to announce a new onboarding experience that makes it easy to set up and manage Amazon Q Developer Pro tier subscriptions. The workflow on Amazon Q console has been redesigned to provide a friendlier 2-step setup for users or teams that are looking to try out Amazon Q Developer in their Integrated Development Environment (IDE).

AWS account administrators can create subscriptions using the Amazon Q console for their standalone or AWS Organizations member accounts using a guided setup to create local users and configure Amazon Q Developer managed applications. Once the setup is complete, subscribed users will receive details on setting up credentials to start using Amazon Q Developer. After installation of the Amazon Q Developer plugin in their preferred IDE, users can leverage context-aware code recommendations and enhanced development capabilities to accelerate their software development. Administrators in the Organizations management accounts will continue to maintain their existing IAM Identity Center capabilities to manage workforce access to Amazon Q Developer.

To learn more about the new getting started experience, visit Amazon Q Developer User Guide . To get started with Amazon Q Developer, visit the AWS Console .
 

Amazon Personalize now supports Internet Protocol Version 6 (IPv6)

By

Amazon Personalize introduces dual stack support for the Personalize API endpoints, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when you privately access the Personalize API endpoint from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink.

The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on Personalize endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to help meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6.

Support for IPv6 on Amazon Personalize in all supported regions . To learn more on best practices for configuring IPv6, see the whitepaper on IPv6 in AWS.
 

Amazon MSK expands Express Brokers to 10 more AWS Regions

By

Amazon MSK has added support for Express brokers in all AWS Regions where Amazon MSK offers Graviton3 based M7g instances. You can now benefit from Amazon MSK Express brokers in ten additional AWS Regions: Asia Pacific (Mumbai), Europe (Paris), South America (Sao Paulo), Asia Pacific (Hyderabad), Asia Pacific (Seoul), Asia Pacific (Malaysia), Europe (London), Canada (Central), Europe (Spain), and Middle East (Bahrain).

Express brokers are a new broker type for Amazon MSK Provisioned designed to deliver up to 3x more throughput per broker, scale up to 20x faster, and reduce recovery time by 90% as compared to standard Apache Kafka brokers. Express brokers come pre-configured with Kafka best practices by default, support all Kafka APIs, and provide the same low-latency performance that Amazon MSK customers expect, so they can continue using existing client applications without any changes.

You can now create an MSK cluster with Express brokers in these AWS Regions from the Amazon MSK console . To learn more, check out this blog .
 

AWS Verified Access launches Zero Trust access to resources over non-HTTP(S) protocols

By

Today, AWS announces the general availability of AWS Verified Access’ support for secure access to resources that connect over protocols such as TCP, SSH, and RDP. With this launch, you can use Verified Access to provide secure VPN-less access to all your corporate applications and resources using AWS zero trust principles . This feature eliminates the need to manage separate access, and connectivity solutions for non-HTTP(S) resources on AWS and simplifies security operations.

Verified Access allows admins to set access policies based on user identity and device posture. It evaluates access for new connections and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren’t met. Now you can extend your existing Verified Access policies to enable secure access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. For example, you can centrally define access policies granting prod database access only to authenticated database administrators using compliant, managed devices. This simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface.

This feature is generally available in 18 AWS regions: US East (Ohio), US East (Northern Virginia), US West (N California), US West (Oregon), Canada (Central), Asia Pacific (Sydney), Asia Pacific (Jakarta), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Milan), Europe (Stockholm), South America (São Paulo), and Israel (Tel Aviv).

To learn more, visit the product page , pricing page , and documentation .
 

Scroll Up