AWS Weekly Roundup: Amazon S3 turns 20, Amazon Route 53 Global Resolver general availability, and more (March 16, 2026)

Twenty years ago this past w...

#AWS #AmazonBedrockAgentcore #AmazonRedshift #AmazonRoute53 #AmazonSimpleStorageService(S3) #AmazonWorkspaces #Announcements #News #WeekInReview

Amazon Route 53 Global Resolver is now generally available Today, AWS announced the general availability of Amazon Route 53 Global Resolver, an internet-reachable anycast DNS resolver that delivers easy, secure, and reliable DNS resolution for authorized clients from anywhere. Global Resolver is now available across 30 AWS Regions, with support for both IPv4 and IPv6 DNS query traffic. Previewed at re:Invent 2025 in 11 AWS Regions, Global Resolver gives authorized clients in your organization anycast DNS resolution of public internet domains and private domains associated with Route 53 private hosted zones — from any location. It also provides DNS query filtering to block potentially malicious domains, not-safe-for-work domains, and domains associated with advanced DNS threats such as DNS tunneling and Domain Generation Algorithms (DGA), along with centralized query logging. With general availability, Global Resolver adds protection against Dictionary DGA threats. New customers can explore Global Resolver with a 30-day free trial. For pricing and feature details, visit the service page. To see supported AWS Regions, see the region table. To get started, see the documentation.

🆕 AWS announced the general availability of Amazon Route 53 Global Resolver, an anycast DNS resolver offering secure, reliable DNS resolution across 30 regions, with IPv4/IPv6 support, DNS filtering, and query logging. Free trial available.

#AWS #AmazonRoute53

Amazon Route 53 Global Resolver is now generally available

Today, AWS announced the general availability of Amazon Route 53 Global Resolver, an internet-reachable anycast DNS resolver that delivers easy, secure, and reliable DNS resolution for authorized clients from anywh...

#AWS #AmazonRoute53

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 5...

#AWS #AmazonRoute53

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.

🆕 Amazon Route 53 Domains now supports ten new TLDs:.ai,.nz,.shop,.bot,.moi,.spot,.free,.deal, .now, and.hot, enhancing domain registration and DNS management, offering tailored options for businesses and individuals via AWS.

#AWS #AmazonRoute53

Amazon Route 53 launches detailed metrics for Resolver endpoints

Starting today, you can enable Amazon CloudWatch metrics for Route 53 to monitor the performance and health of Route 53 Resolver endpoints and any target name servers associated with your outbo...

#AWS #AwsGovcloudUs #AmazonRoute53

Amazon Route 53 launches detailed metrics for Resolver endpoints Starting today, you can enable Amazon CloudWatch metrics for Route 53 to monitor the performance and health of Route 53 Resolver endpoints and any target name servers associated with your outbound Resolver endpoints. Amazon Route 53 Resolver endpoints make hybrid cloud configurations easier to manage by enabling seamless DNS query resolution between your on-premises data center and Amazon Virtual Private Cloud (Amazon VPC). The new metrics can be enabled on CloudWatch for each of your Resolver endpoints allowing you to assess the response latency of DNS queries received by the Resolver endpoints, the number of query responses that resulted in SERVFAIL, NXDOMAIN, REFUSED, or FORMERR statuses. You can also view the availability of target name servers associated with outbound Resolver endpoints, by viewing the response latency of the target server, and the number of queries that resulted in a timeout. The new metrics make it easy for you to quickly evaluate the health of your Route 53 Resolver endpoints and the associated target name servers. To learn more about the metrics, read the documentation or visit the Route 53 VPC Resolver page. Standard CloudWatch and Resolver endpoint charges are applied for using the Route 53 Resolver endpoint detailed metrics. For more information, see Amazon CloudWatch pricing and Resolver endpoint pricing.

🆕 Amazon Route 53 now offers detailed CloudWatch metrics for Resolver endpoints to monitor performance, health, and response latency of DNS queries, including SERVFAIL and timeouts, aiding hybrid cloud DNS resolution management.

#AWS #AwsGovcloudUs #AmazonRoute53

Introducing Amazon Route 53 Global Resolver for secure anycast DNS resolution (preview) | Amazon Web Services Simplify hybrid DNS management with a unified service that resolves public and private domains globally through secure, anycast-based resolution while reducing operational overhead and maintaining consistent...

📰🚨 Introducing Amazon Route 53 Global Resolver for secure anycast DNS resolution (preview)

#AmazonRoute53 #GlobalResolver #DNSResolution #CloudSecurity #HybridInfrastructure

Introducing Amazon Route 53 Global Resolver for secure anycast DNS resolution (preview)

Today, AWS announced the preview of Amazon Route 53 Global Resolver, a new internet-reachable DNS resolver that provides easy, secure, and reliable DNS resolution from anywhere for quer...

#AWS #AmazonRoute53

Introducing Amazon Route 53 Global Resolver for secure anycast DNS resolution (preview)

Simplify hybrid DNS management with a unified service that resolves public and private domains globally through secure, anycast-...

#AWS #AmazonRoute53 #Announcements #Launch #Networking&ContentDelivery #News

Amazon Route 53 launches Accelerated recovery for managing public DNS records | Amazon Web Services Amazon Route 53 now offers Accelerated recovery for managing public DNS records, a new business continuity feature designed to provide a 60-minute recovery time objective (RTO) during service disruptions...

📰🚨 Amazon Route 53 launches Accelerated recovery for managing public DNS records

#AmazonRoute53 #DNSBusinessContinuity #CloudResilience #AWSManagement #AcceleratedRecovery

Amazon Route 53 launches Accelerated recovery for managing public DNS records

Amazon Route 53 now offers Accelerated recovery for managing public DNS records, a new business continuity feature designed to provide a 60-minute recovery time objec...

#AWS #AmazonRoute53 #Announcements #Launch #News

Amazon Route 53 announces accelerated recovery for managing public DNS records

Amazon Route 53 is excited to release the accelerated recovery option for managing DNS records in public hosted zones. Accelerated recovery targets a 60-minute recovery time objective (RTO) for ...

#AWS #AmazonRoute53

Amazon Route 53 announces accelerated recovery for managing public DNS records Amazon Route 53 is excited to release the accelerated recovery option for managing DNS records in public hosted zones. Accelerated recovery targets a 60-minute recovery time objective (RTO) for regaining the ability to make DNS changes to your DNS records in Route 53 public hosted zones, if AWS services in US East (N. Virginia) become temporarily unavailable. The Route 53 public DNS service API is used by customers today for making changes to DNS records in order to facilitate software deployments, run infrastructure operations, and onboard new users. Customers in banking, financial technology (FinTech), and software-as-a-service (SaaS) in particular need a predictable and short RTO for meeting business continuity and disaster recovery objectives. In the past, if AWS services in US East (N. Virginia) became unavailable, customers would not be able to modify or recreate DNS records to point users and internal services to updated endpoints. Now, when you enable the accelerated recovery option on your Route 53 public hosted zone, you can make changes to Route 53 public DNS records (Resource Record Sets) in that hosted zone soon after such an interruption, most often in less than one hour. Accelerated recovery for managing public DNS records is available globally, except in AWS GovCloud and Amazon Web Services in China. There is no additional charge for using this feature. To learn more about the accelerated recovery option, visit our documentation.

🆕 Amazon Route 53 introduces accelerated recovery for public DNS, aiming for a 60-min RTO to manage DNS records if US East (N. Virginia) services fail. Available globally, except AWS GovCloud and China, with no extra charge.

#AWS #AmazonRoute53

Amazon Route 53 DNS service adds support for IPv6 API service endpoint

Starting today, Amazon Route 53 supports dual stack for the Route 53 DNS service API endpoint at route53.global.api.aws, enabling you to connect from Internet Protocol Version 6 (IPv6), Internet Protoco...

#AWS #AmazonRoute53

Amazon Route 53 DNS service adds support for IPv6 API service endpoint Starting today, Amazon Route 53 supports dual stack for the Route 53 DNS service API endpoint at route53.global.api.aws, enabling you to connect from Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. The existing Route 53 DNS service IPv4 API endpoint will remain available for backwards compatibility. Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service that allows customers to register a domain, setup DNS records corresponding to your infrastructure, perform global traffic routing using Traffic Flow, and use Route 53 health checks to monitor the health and performance of your applications and resources. Due to the continued growth of the internet, IPv4 address space is being exhausted and customers are transitioning to IPv6 addresses. Now, clients can connect via IPv6 to the Route 53 DNS service API endpoint, enabling organizations to meet compliance requirements and removing the added complexity of IP address translation between IPv4 and IPv6. Support for IPv6 on the Route 53 DNS service API endpoint is available in all Commercial Regions and available at no additional cost. You can get started with this feature through the AWS CLI or AWS Management Console. To learn more about which Route 53 features are accessible via the route53.amazon.aws service endpoint, visit this page and to learn more about the Route 53 DNS service, visit our documentation.

🆕 Amazon Route 53 now supports IPv6 API endpoint, enabling dual stack connections for IPv4/IPv6, aiding IPv6 transition and compliance. Available in all regions at no extra cost. Use AWS CLI or Console.

#AWS #AmazonRoute53

Amazon Route 53 DNS service now supports AWS PrivateLink

Amazon Route 53 now supports https://aws.amazon.com/privatelink/ for API requests to the route53.amazonaws.com service endpoint, allowing your AWS workloads to make changes to critical DNS infrastructure, including h...

#AWS #AmazonRoute53

Amazon Route 53 DNS service now supports AWS PrivateLink Amazon Route 53 now supports AWS PrivateLink for API requests to the route53.amazonaws.com service endpoint, allowing your AWS workloads to make changes to critical DNS infrastructure, including hosted zones, records, and health checks, without using the public internet. With this release, you can set up private connectivity between your virtual private clouds (VPCs) and the Route 53 API, from your VPC on the AWS backbone, in any AWS Region. The Route 53 API is used by customers for domain name system (DNS) operations, which are a foundational layer of their cloud infrastructure automation, user-facing applications, and internal services. This integration simplifies cloud architecture by removing the need for customers to setup and manage complex networking services that connect resources in their virtual private clouds (VPCs) privately to the Route 53 API. Now, customers can use a VPC endpoint within their VPC to establish connectivity to the Route 53 API. Customers outside the us-east-1 can use cross-region Interface VPC endpoints to natively connect to Route53 from other Regions, without the need to send traffic over the public internet or set up inter-region connectivity like VPC peering. Route 53 support for PrivateLink is available globally, except in AWS GovCloud and Amazon Web Services in China. To learn more about this feature, or to get started, visit the AWS PrivateLink documentation. To learn about pricing, visit the PrivateLink pricing page.

🆕 Amazon Route 53 now supports AWS PrivateLink for private API requests, enabling secure DNS operations without public internet access, simplifying VPC connectivity, and available globally except AWS GovCloud and China.

#AWS #AmazonRoute53

Amazon Route 53 DNS Firewall adds protection against Dictionary-based DGA attacks

Starting today, you can enable Route 53 Resolver DNS Firewall Advanced to monitor and block queries associated with Dictionary-based Domain Generation Algorithm (DGA) attacks, ...

#AWS #AmazonRoute53 #AwsGovcloudUs

Amazon Route 53 DNS Firewall adds protection against Dictionary-based DGA attacks Starting today, you can enable Route 53 Resolver DNS Firewall Advanced to monitor and block queries associated with Dictionary-based Domain Generation Algorithm (DGA) attacks, that generate domain names by pseudo-randomly concatenating words from a predefined dictionary, creating human-readable strings to evade detection. Route 53 DNS Firewall Advanced is an offering on Route 53 DNS Firewall that enables you to enforce protections to monitor and block your DNS traffic in real-time based on anomalies identified in the domain names being queried from your VPCs. These include protections for DNS tunneling and DGA attacks. With this launch, you can also enforce protections for Dictionary-based DGA attacks, which is a variant of the DGA attack, where domain names are generated to mimic and blend with legitimate domain names, to resist detection. To get started, you can configure one or multiple DNS Firewall Advanced rule(s), specifying Dictionary DGA as the threat to be inspected. You can add the rule(s) to a DNS Firewall rule group, and enforce it on your VPCs by associating the rule group to each desired VPC directly or by using AWS Firewall Manager, AWS Resource Access Manager (RAM), AWS CloudFormation, or Route 53 Profiles. Route 53 Resolver DNS Firewall Advanced support for Dictionary DGA is available in all AWS Regions, including the AWS GovCloud (US) Regions. To learn more about the new capabilities and the pricing, visit the Route 53 Resolver DNS Firewall webpage and the Route 53 pricing page. To get started, visit the Route 53 documentation.

🆕 Amazon Route 53 DNS Firewall now blocks Dictionary-based DGA attacks, enhancing protection against domain names generated to evade detection, available in all AWS Regions. Configure DNS Firewall Advanced rules to enforce protections on your VPCs.

#AWS #AmazonRoute53 #AwsGovcloudUs

Amazon Route 53 Profiles now supports Resolver query logging configurations

Today, AWS announced support for Resolver query logging configurations in Amazon Route 53 Profiles, allowing you to manage Resolver query logging configuration and apply it to multip...

#AWS #AmazonRoute53 #AwsGovcloudUs

Amazon Route 53 Profiles now supports Resolver query logging configurations Today, AWS announced support for Resolver query logging configurations in Amazon Route 53 Profiles, allowing you to manage Resolver query logging configuration and apply it to multiple VPCs and AWS accounts within your organization. With this enhancement, Amazon Route 53 Profiles simplifies the management of Resolver query logging by streamlining the process of associating logging configurations with VPCs, and without requiring you to manually associate them with each VPC. Route 53 Profiles allows you to create and share Route 53 configurations (private hosted zones, DNS Firewall rule groups, Resolver rules) across multiple VPCs and AWS accounts. Previously, Resolver query logging required you to manually set it up for each VPC in every AWS account. Now, with Route 53 Profiles you can manage your Resolver query logging configurations for your VPCs and AWS accounts, using a single Profile configuration. Profiles support for Resolver query logging configurations reduces the management overhead for network security teams and simplifies compliance auditing by providing consistent DNS query logs across all accounts and VPCs. Route 53 Profiles support for Resolver query logging is now available in the AWS Regions mentioned here. To learn more about this capability and how it can benefit your organization, visit the Amazon Route 53 documentation. You can get started by accessing the Amazon Route 53 console in your AWS Management Console or through the AWS CLI. To learn more about Route 53 Profiles pricing, see here.

🆕 AWS now supports Resolver query logging in Route 53 Profiles, simplifying VPC and account-wide Resolver query logging management across multiple accounts and VPCs, reducing manual setup and compliance auditing overhead. Available in select regions.

#AWS #AmazonRoute53 #AwsGovcloudUs

Amazon Route 53 Resolver now supports AWS PrivateLink

Amazon Route 53 Resolver now supports https://aws.amazon.com/privatelink/ Customers can now access and manage docs.aws.amazon.com/Route53/latest/Developer... all the related features (Res...

#AWS #AmazonRoute53

Amazon Route 53 Resolver now supports AWS PrivateLink Amazon Route 53 Resolver now supports AWS PrivateLink. Customers can now access and manage Route 53 Resolver and all the related features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Resolver and its features are accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing, can be handled via the Amazon private network.  Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. Route 53 Resolver also offers features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) that you can opt-into. You can use Resolver and its features with AWS PrivateLink in regions where Route 53 Resolver and all its associated features are available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Resolver and its features are available, see here. To learn more about Route 53 Resolver and its features, please refer to the service documentation.

🆕 Amazon Route 53 Resolver now supports AWS PrivateLink for private access to features like Resolver endpoints and DNS Firewall, without public internet exposure, enhancing security over the Amazon network.

#AWS #AmazonRoute53

Amazon Route 53 Profiles now supports AWS PrivateLink

Amazon Route 53 Profiles now supports https://aws.amazon.com/privatelink/ Customers can now access and manage their Profiles privately, without going through the public internet. AWS PrivateLink provide...

#AWS #AwsGovcloudUs #AmazonRoute53

Amazon Route 53 Profiles now supports AWS PrivateLink Amazon Route 53 Profiles now supports AWS PrivateLink. Customers can now access and manage their Profiles privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Profiles is accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing of Profiles, can be handled via the Amazon private network.  Route 53 Profiles allows you to define a standard DNS configuration, in the form of a Profile, that may include Route 53 private hosted zone (PHZ) associations, Route 53 Resolver rules, and Route 53 Resolver DNS Firewall rule groups, and apply this configuration to multiple VPCs in your account. Profiles can also be used to enforce DNS settings for your VPCs, with configurations for DNSSEC validations, Resolver reverse DNS lookups, and the DNS Firewall failure mode. You can share Profiles with AWS accounts in your organization using AWS Resource Access Manager (RAM). Customers can use Profiles with AWS PrivateLink in regions where Route 53 Profiles is available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Profiles is available, see here. To learn more about configuring Route 53 Profiles, please refer to the service documentation.

🆕 Amazon Route 53 Profiles now use AWS PrivateLink for secure, private access, avoiding public internet use. All DNS operations are handled securely over Amazon's network, including management and sharing across accounts. Available in select regions.

#AWS #AwsGovcloudUs #AmazonRoute53

Amazon Route 53 Resolver Query Logging now available in Asia Pacific (New Zealand)

Today, we are announcing the availability of Route 53 Resolver Query Logging in Asia Pacific (New Zealand), enabling you to log DNS queries that originate in your Amazon Virtual Private Clo...

#AWS #AmazonRoute53

Amazon Route 53 Resolver Query Logging now available in Asia Pacific (New Zealand) Today, we are announcing the availability of Route 53 Resolver Query Logging in Asia Pacific (New Zealand), enabling you to log DNS queries that originate in your Amazon Virtual Private Cloud (Amazon VPC). With query logging enabled, you can see which domain names have been queried, the AWS resources from which the queries originated - including source IP and instance ID - and the responses that were received.  Route 53 Resolver is the Amazon provided DNS server that is available by default in all Amazon VPCs. Route 53 Resolver responds to DNS queries from AWS resources within a VPC for public DNS records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones. With Route 53 Resolver Query Logging, customers can log DNS queries and responses for queries originating from within their VPCs, whether those queries are answered locally by Route 53 Resolver, or are resolved over the public internet, or are forwarded to on-premises DNS servers via Resolver Endpoints. You can share your query logging configurations across multiple accounts using AWS Resource Access Manager (RAM). You can also choose to send your query logs to Amazon S3, Amazon CloudWatch Logs, or Amazon Data Firehose.  There is no additional charge to use Route 53 Resolver Query Logging, although you may incur usage charges from Amazon S3, Amazon CloudWatch, or Amazon Data Firehose. To learn more about Route 53 Resolver Query Logging or to get started, visit the Route 53 Resolver product page or the Route 53 documentation.

🆕 AWS Route 53 Resolver Query Logging now available in Asia Pacific (New Zealand) to log DNS queries from VPCs, showing queried domains, source IPs, and responses, with no extra charge, though S3, CloudWatch, or Firehose usage may incur costs.

#AWS #AmazonRoute53

AWS Weekly Roundup: Project Rainier, Amazon CloudWatch investigations, AWS MCP servers, and more (June 30, 2025)

...

#AWS #AmazonBedrockGuardrails #AmazonCloudwatch #AmazonQDeveloper #AmazonRoute53 #AmazonSimpleStorageService(S3) #Announcements #AwsIotDeviceManagement #Launch #News #WeekInReview

Amazon Route 53 launches capacity utilization metric for Resolver endpoints

Starting today, you can enable Amazon CloudWatch metric (ResolverEndpointCapacityStatus) to monitor the status of the query capacity for Elastic Network Interfaces (ENIs) associated ...

#AWS #AmazonRoute53 #AwsGovcloudUs