Amazon Route 53 Domains adds support for .ai, and other top-level domains

Amazon Route 53 Domains now supports registration and management of ten new top-level domains (TLDs): .ai, .nz, .shop, .bot, .moi, .spot, .free, .deal, .now, and .hot. This expansion enhances Route 53’s capabilities as a domain registration and DNS management service, offering customers more options to establish their online presence. With these additions, businesses and individuals can now leverage domain names tailored to specific industries, regions, or purposes directly through Amazon Web Services (AWS). The new TLDs cater to various use cases. To name a few, the .ai domain, originally for Anguilla, has become popular among artificial intelligence companies. E-commerce sites can utilize .shop for their online storefronts. The .bot domain suits chatbot and AI-related services. The .now domain works well for time-sensitive services and instant delivery platforms. Users can register these domains through the Route 53 console, AWS CLI, or SDKs, enjoying integrated DNS management and automatic renewal features. This seamless integration allows for efficient domain administration alongside existing Route 53 hosted zones and DNS records. To learn more about Amazon Route 53 Domains and start registering new domains, visit the Amazon Route 53 page. Domain registration pricing varies by TLD. Visit the pricing page for detailed pricing information.
 
Quelle: aws.amazon.com

Amazon Connect adds conditional logic and real-time updates to Step-by-Step Guides

Amazon Connect Step-by-Step Guides now enables managers to build more dynamic and responsive guided experiences. Managers can create conditional user interfaces that adapt based on user interactions, making workflows more efficient. For example, managers can configure dropdown menus to show or hide fields, change default values, or adjust required fields based on the input in prior fields, creating tailored experiences for different scenarios. In addition, Step-by-Step Guides can now automatically refresh data from Connect resources such as flow modules at specified intervals, ensuring agents always work with the most current information. Amazon Connect Step-by-Step Guides is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (London), and the AWS GovCloud (US-West) Region. To learn more and get started, visit the Amazon Connect webpage and documentation.
Quelle: aws.amazon.com

Announcing general availability of Amazon EC2 M4 Max Mac instances

Amazon Web Services announces general availability of Amazon EC2 M4 Max Mac instances, powered by the latest Mac Studio hardware. Amazon EC2 M4 Max Mac instances are the next-generation EC2 Mac instances, that enable Apple developers to migrate their most demanding build and test workloads onto AWS. These instances are ideal for building and testing applications for Apple platforms such as iOS, macOS, iPadOS, tvOS, watchOS, visionOS, and Safari. Amazon EC2 M4 Max Mac instances offer up to 25% better application build performance compared to Amazon EC2 M1 Ultra Mac instances. M4 Max Mac instances are powered by the AWS Nitro System, providing up to 10 Gbps network bandwidth and 8 Gbps of Amazon Elastic Block Store (Amazon EBS) storage bandwidth. These instances are built on Apple M4 Max Mac Studio computers featuring a 16-core CPU, 40-core GPU, 16-core Neural Engine, and 128GB of unified memory. 
Amazon EC2 M4 Max Mac instances are available in US East (N. Virginia) and US West (Oregon).  To learn more about Amazon EC2 M4 Max Mac instances, visit the Amazon EC2 Mac page.
Quelle: aws.amazon.com

Amazon EVS now supports multiple VMware NSX Edge Gateways

Today, we’re announcing that Amazon Elastic VMware Service (Amazon EVS) now supports the ability to deploy multiple VMware NSX Tier-0 Gateways within VMware Software-Defined Data Centers (SDDC), enabling enhanced network segmentation and more flexible routing configurations. Multiple NSX Tier-0 Gateways allow for better performance and scale by distributing network traffic across multiple NSX Edge Clusters. This latest enhancement enables improved network segmentation, allowing you to isolate different workload environments and maintain distinct security policies for each gateway. You can also use multiple gateways to create separate test environments for validating network configurations and performing gateway upgrades with minimal impact to production workloads. This architecture flexibility helps you align your network topology with specific business requirements while maintaining operational efficiency in running your VMware workloads on AWS with Amazon EVS.  To learn more about this newest enhancement, read this re:Post article that walks you through the process of deploying multiple NSX Edge Clusters within your EVS environment. To get started with Amazon EVS, visit the product detail page and user guide.
Quelle: aws.amazon.com

EC2 Auto Scaling Introduces New Mechanisms for Group Deletion Protection

EC2 Auto Scaling is introducing a new policy condition key autoscaling:ForceDelete. This condition key is used with the DeleteAutoScalingGroup action to control whether the ForceDelete parameter can be used during deletion, which determines if an Auto Scaling group (ASG) can be deleted while it still contains running instances. You can use this condition key in IAM policies to restrict deletion permissions. This provides a safety measure to prevent accidental deletion of ASGs that still have running instances. Furthermore, EC2 Auto Scaling now offers deletion protection at the group level. The new deletion-protection configuration can be set either when you create your ASGs or update them. This new feature lets you set enhanced controls based on your workload’s criticality, with multiple protection levels available to safeguard against accidental deletions and help maintain application availability. Combining the autoscaling:ForceDelete condition key with deletion protection at the group level provides a layered defense against unwanted ASG termination by allowing you to both restrict IAM permissions for force-delete operations and set enhanced protection controls directly on critical ASGs. The features now available in all AWS Regions and AWS GovCloud (US) Regions. To get started, visit the EC2 Auto Scaling console or refer to our technical documentation for deletion protection and policy condition keys for Amazon EC2 Auto Scaling.
Quelle: aws.amazon.com

AWS Config launches 13 new managed rules

AWS Config announces launch of an additional 13 managed Config rules for various use cases such as security, durability, and operations. You can now search, discover, enable and manage these additional rules directly from AWS Config and govern more use cases for your AWS environment. With this launch, you can now enable these controls across your account or across your organization. For example, you can assess your security posture across Amazon Cognito User pools, Amazon EBS Snapshots, AWS Cloudformation Stacks and more. Additionally, you can leverage Conformance Packs to group these new controls and deploy across an account or across organization, streamlining your multi-account governance. For the full list of recently released rules, visit the AWS Config developer guide. For description of each rule and the AWS Regions in which it is available, please refer our Config managed rules documentation. To start using Config rules, please refer our documentation. New Rules Launched:

AURORA_GLOBAL_DATABASE_ENCRYPTION_AT_REST
CLOUDFORMATION_STACK_SERVICE_ROLE_CHECK
CLOUDFORMATION_TERMINATION_PROTECTION_CHECK
CLOUDFRONT_DISTRIBUTION_KEY_GROUP_ENABLED
COGNITO_USER_POOL_DELETE_PROTECTION_ENABLED
COGNITO_USER_POOL_MFA_ENABLED
COGNITO_USERPOOL_CUST_AUTH_THREAT_FULL_CHECK
EBS_SNAPSHOT_BLOCK_PUBLIC_ACCESS
ECS_CAPACITY_PROVIDER_TERMINATION_CHECK
ECS_TASK_DEFINITION_EFS_ENCRYPTION_ENABLED
ECS_TASK_DEFINITION_LINUX_USER_NON_ROOT
ECS_TASK_DEFINITION_WINDOWS_USER_NON_ADMIN
SES_SENDING_TLS_REQUIRED

Quelle: aws.amazon.com

Amazon EC2 C8i and C8i-flex instances are now available in Asia Pacific (Sydney) and Europe (Frankfurt) regions

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C8i and C8i-flex instances are available in the Asia Pacific (Sydney), and Europe (Frankfurt) regions. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. These C8i and C8i-flex instances offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% higher performance than C7i and C7i-flex instances, with even higher gains for specific workloads. The C8i and C8i-flex are up to 60% faster for NGINX web applications, up to 40% faster for AI deep learning recommendation models, and 35% faster for Memcached stores compared to C7i and C7i-flex. C8i-flex are the easiest way to get price performance benefits for a majority of compute intensive workloads like web and application servers, databases, caches, Apache Kafka, Elasticsearch, and enterprise applications. They offer the most common sizes, from large to 16xlarge, and are a great first choice for applications that don’t fully utilize all compute resources. C8i instances are a great choice for all memory-intensive workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. C8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications. To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information about the new C8i and C8i-flex instances visit the AWS News blog.
Quelle: aws.amazon.com

Amazon MQ now supports Java Messaging Service (JMS) specification for RabbitMQ brokers

Amazon MQ now supports the ability for RabbitMQ 4 brokers to connect to JMS applications through the RabbitMQ JMS Topic Exchange plugin and JMS client. The JMS topic exchange plugin is enabled by default on all RabbitMQ 4 brokers, allowing you to use the JMS client to run your JMS 1.1, JMS 2.0, and JMS 3.1 applications on RabbitMQ. You can also use the RabbitMQ JMS client to send JMS messages to an AMQP exchange and consume messages from an AMQP queue to interoperate or migrate JMS workloads to AMQP workloads. To start using your JMS applications on RabbitMQ, simply select RabbitMQ 4.2 when creating a new broker using the M7g instance type through the AWS Management console, AWS CLI, or AWS SDKs, and then use the RabbitMQ JMS client to connect your applications. To learn more about the plugin, see the Amazon MQ release notes and the Amazon MQ developer guide. This plugin is available in all regions where Amazon MQ RabbitMQ 4 instances are available today. 
Quelle: aws.amazon.com

AWS expands Resource Control Policies support for Cognito and CloudWatch Logs

AWS Resource Control Policies (RCPs) now provide support for Amazon Cognito and Amazon CloudWatch Logs. Resource control policies (RCPs) are a type of organization policy that you can use to manage permissions in your organization. RCPs offer central control over the maximum available permissions for resources in your organization. With this expansion, you can now use RCPs to manage permissions for Amazon Cognito and Amazon CloudWatch Logs resources. For example, you can create policies that prevent identities outside your organization from accessing these resources, helping you build a data perimeter and enforce baseline security standards across your AWS environment. RCPs are available in all AWS commercial Regions and AWS GovCloud (US) Regions. To learn more about RCPs and view the full list of supported AWS services, visit the Resource control policies (RCPs) documentation in the AWS Organizations User Guide.
Quelle: aws.amazon.com

Amazon Bedrock AgentCore Browser now supports custom browser extensions

Amazon Bedrock AgentCore Browser now supports custom Chrome browser extensions, enabling automation for complex workflows that standard browser automation cannot handle alone. This enhancement builds upon AgentCore’s existing secure browser features, allowing users to upload Chrome-compatible extensions to S3 and automatically install them during browser sessions. The feature serves enterprise developers, automation engineers, and organizations across industries requiring specialized browser functionality within a secure environment.
This new feature enables powerful use cases including custom authentication flows, automated testing, and improved web navigation with performance optimization through ad blocking. Organizations gain the ability to integrate third-party tools that operate as browser extensions, eliminating manual processes while maintaining security within the AgentCore Browser environment. This feature is available in all nine AWS Regions where Amazon Bedrock AgentCore Browser is available: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), and Europe (Ireland). To learn more about implementing custom browser extensions in Amazon Bedrock AgentCore, visit the Browser documentation.
Quelle: aws.amazon.com