da Agency

Amazon S3 Object Lock variable retention with event holds is now available in AWS GovCloud (US) Regions

Amazon S3 Object Lock support for variable retention with event holds is now available in AWS GovCloud (US-East) and AWS GovCloud (US-West).
Amazon S3 Object Lock variable retention allows you to apply write-once-read-many (WORM) protection to objects whose required retention period starts with a future event, such as a contract closing or an audit completing. You place an event hold with a retention duration on an object and S3 protects the object while the hold is in place. When you release the hold, S3 retains the object for the duration you specified. Unlike legal holds, which end protection immediately upon removal, event holds provide WORM compliance for the required retention period after the triggering event, so you can meet event-based retention requirements without retaining data longer than your policy requires.

To learn more, read the AWS Storage Blog post, the S3 Object Lock overview page, and the S3 documentation. This capability has been assessed by Cohasset Associates for use in environments subject to SEC Rule 17a-4(f), FINRA Rule 4511, and CFTC Regulation 1.31.
Quelle: aws.amazon.com

da Agency

Amazon Corretto 8 September 2026 Patch Updates

On September 30, 2026, Amazon announced a patch update for the following Amazon Corretto Long-Term Support (LTS) version of OpenJDK: Corretto 8u504 is now available for download. Amazon Corretto is a no-cost, multi-platform, production-ready distribution of OpenJDK. This patch includes the tzdata 2026d updates.
Visit Corretto home page to download Corretto 27, Corretto 25, Corretto 21, Corretto 17, Corretto 11, or Corretto 8. You can also get the updates on your Linux system by configuring a Corretto Apt, Yum, or Apk repo.
Feedback is welcomed!
Quelle: aws.amazon.com

da Agency

Amazon GuardDuty now supports centralized management using AWS Organizations declarative policies

Amazon GuardDuty now supports AWS Organizations declarative policies, enabling you to centrally enable GuardDuty threat detection across every account and Region in your AWS organization. Using an organization policy, you can now apply a centrally managed GuardDuty enablement configuration. The configuration applies to existing accounts and is automatically maintained as new accounts join your organization.
Enabling GuardDuty across all relevant accounts and Regions helps ensure comprehensive threat detection coverage. Previously, keeping enablement aligned across a large multi-account, multi-Region environment meant configuring GuardDuty’s enablement settings separately in each Region, which could drift over time. Now you can define a central GuardDuty policy from your delegated administrator account that sets an enablement baseline across your organization (at the organization root, OUs, or individual accounts). The policy supports a default configuration that applies in every Region where GuardDuty is available, as well as per-Region overrides for Regions that require different enablement. Enablement set by a policy cannot be overridden via the GuardDuty console or API.
GuardDuty declarative policy support is available in all AWS commercial Regions and the AWS GovCloud (US) Regions. To get started, make sure the delegated administrator has permission to manage GuardDuty policies. Then, sign in to the GuardDuty console and choose Organization policies, or create a policy programmatically using AWS Organizations APIs. To learn more, see Managing accounts using organization policies in the Amazon GuardDuty User Guide and Amazon GuardDuty policies in the AWS Organizations User Guide.
Quelle: aws.amazon.com

da Agency

Amazon DynamoDB Accelerator (DAX) is now available in additional Regions

Today, AWS announces the availability of Amazon DynamoDB Accelerator (DAX) in 17 additional AWS Regions: Asia Pacific (Hong Kong), Asia Pacific (Hyderabad), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Melbourne), Asia Pacific (New Zealand), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Taipei), Asia Pacific (Thailand), Canada West (Calgary), Europe (Milan), Europe (Zurich), Israel (Tel Aviv), Mexico (Central), AWS GovCloud (US-East), and AWS GovCloud (US-West). DAX is a fully managed, highly available, in-memory cache for Amazon DynamoDB that delivers up to 10 times performance improvement—from single-digit milliseconds to microseconds—even at millions of requests per second. This expansion brings DAX to more geographies, helping customers accelerate read-heavy DynamoDB workloads without managing their own cache infrastructure.
With DAX, you can accelerate read-intensive and bursty workloads such as real-time bidding, gaming leaderboards, and retail product catalogs, while offloading read traffic from your DynamoDB tables. DAX is API-compatible with DynamoDB, so you can add microsecond-latency caching to your applications with minimal code changes. Customers in these Regions can now meet local data residency and low-latency requirements while benefiting from DAX’s fully managed operations, including automated patching, failover, and scaling.
To see the full list of Regions where DAX is available, see the following resources: AWS Capabilities by Region.
Quelle: aws.amazon.com

da Agency

SQL Server on Azure Local is now generally available

Some of the world’s most critical databases run in places where cloud connectivity cannot be assumed. A remote industrial site, for example, may need production systems to continue operating when external connectivity is unavailable. A regulated organization may need sensitive data and processing to remain within sovereign boundaries.

Today, SQL Server on Azure Local is generally available for connected and disconnected operations. With this release, customers can modernize where their data resides while maintaining control over infrastructure, connectivity, and data placement. They can bring AI closer to their data with Foundry Local on Azure Local, currently in preview, and use eligible existing SQL Server licensing investments.

Explore SQL Server on Azure LocalRun SQL Server where your data needs to staySQL Server has a long history of supporting mission-critical workloads on customer infrastructure. Azure Local builds on that flexibility by bringing Azure infrastructure to customer-owned environments, giving organizations a consistent platform for running SQL Server across datacenters and edge locations.

Customers can choose the deployment model that fits each environment:

Connected environments: Run SQL Server locally on Azure Local, while using Azure Arc to manage SQL Server resources through Azure.Azure Local Disconnected Operations (ALDO): Run SQL Server in environments where external connectivity is restricted, intermittent, or unavailable, with operations continuing locally.This means organizations can choose the deployment approach that fits the requirements of individual environments rather than making the same connectivity decision across their entire data estate.

SQL Server on Azure Local – connected and disconnected operations.Bring AI closer to your dataModernizing infrastructure is only part of the opportunity. Organizations also want to bring generative AI to existing enterprise data, including information that cannot leave their environment.

With Foundry Local, customers can run AI models on Azure Local infrastructure alongside SQL Server, bringing inferencing closer to the data. This enables organizations to explore AI-powered applications while keeping sensitive information and processing within their environment.

This can be particularly valuable in sovereign, regulated, and edge scenarios, where organizations want the benefits of AI but need greater control over where models execute and where their data is processed.

The goal is simple: customers should not have to move sensitive data somewhere else simply to begin building intelligent applications around it.

Build on your existing SQL server investmentsModernization should also make it easier to build on existing investments.

SQL Server is licensed separately from the Azure Local infrastructure platform. For connected deployments, customers can use eligible existing SQL Server licenses, including licenses with Software Assurance or qualifying subscriptions, or use pay-as-you-go licensing through Azure Arc.

For fully disconnected deployments, customers can use eligible existing SQL Server licenses through Azure Hybrid Benefit.

This gives organizations options to modernize their SQL Server environments while taking advantage of eligible licensing investments they already own.

A foundation for sovereign and edge dataEnterprise data estates increasingly span cloud, datacenter, edge, and sovereign environments. The opportunity is not to force every workload into the same deployment model, but to give organizations a consistent path to modernization across them.

SQL Server on Azure Local extends that choice to mission-critical SQL Server workloads, helping customers modernize close to their data, applications, and operations while bringing Azure-consistent infrastructure and local AI capabilities into those environments.

SQL Server on Azure Local FAQWhat is SQL Server on Azure Local?SQL Server on Azure Local lets organizations run SQL Server on Azure Local infrastructure in their own datacenters and edge locations. It supports SQL Server workloads on virtual machines running Windows Server or Linux.

What is the difference between connected and disconnected deployments?Connected deployments use Azure connectivity and can use Azure Arc to manage SQL Server resources through Azure. Disconnected operations are designed for environments where external connectivity is restricted, intermittent, or unavailable, with operations continuing locally.

Who should consider SQL Server on Azure Local?It is designed for organizations that need local control because of sovereignty, regulatory, latency, operational continuity, or edge requirements, including public sector, defense, financial services, healthcare, manufacturing, energy, and other regulated or connectivity-constrained environments.

Can customers use existing SQL Server licenses?Eligible existing SQL Server licenses can be used according to applicable licensing terms. For connected deployments, customers can also use pay-as-you-go licensing through Azure Arc. Fully disconnected deployments use eligible existing licenses through Azure Hybrid Benefit.

Can organizations run AI close to their SQL Server data?Foundry Local on Azure Local brings AI inference to Azure Local environments and is designed to keep data processing on-premises. As of September 29, 2026, Foundry Local on Azure Local is currently available in preview, so availability and capabilities may change before general availability.

Where can I find deployment guidance?Microsoft Learn provides guidance for deploying SQL Server on Azure Local, including hardware selection, SQL Server installation, monitoring, performance tuning, high availability, and related Azure hybrid services.

Get Started with SQL Server on Azure LocalSQL Server on Azure Local is generally available for connected and disconnected deployment scenarios.

SQL Server on Azure Local – OverviewDeploy SQL Server on Azure LocalDeploy SQL Server on Azure Local Disconnected ModeLearn more about Azure Arc-enabled SQL ServerAdditional resources

Manage SQL Server licensing and billing with Azure ArcFoundry Local on Azure Local overviewFoundry Local deployment overview
The post SQL Server on Azure Local is now generally available appeared first on Microsoft Azure Blog.
Quelle: Azure