News For Dev-ops

Amazon Redshift now supports writing directly to Apache Iceberg tables via the AWS Glue Data Catalog (awsdatacatalog) mount and ALTER TABLE DDL statements to modify the schema, partitioning, and properties of Apache Iceberg tables. With write access through the auto-mounted awsdatacatalog, you can land Redshift transformations in your data lake for any engine to query without creating external schemas—particularly useful for Iceberg tables federated with AWS Lake Formation. Supported ALTER TABLE operations include ADD/DROP/ALTER columns, RENAME COLUMN, SET TABLE PROPERTIES to overwrite the default compression type, and ADD/DROP/REPLACE PARTITION FIELD to adapt partitioning strategies as data volumes grow. Previously, updating the structure of Iceberg tables required deleting the table and its data, adding complexity and latency to data pipelines. Tables modified by Redshift remain compatible with other Iceberg-compatible engines, including Amazon EMR and Amazon Athena , pres...

Amazon SageMaker Studio IDEs, including JupyterLab and Code Editor, now support GPU capacity reservations through SageMaker Flexible Training Plans (FTP) , giving you predictable access to high-demand, high-performance computational resources within your budget. By leveraging FTP, you can achieve up to 65% cost savings compared to On-Demand instances while running ML workflows in JupyterLab or Code Editor. FTP provides a fully self-serve procurement experience. To get started, navigate to the SageMaker FTP console and select your preferred instance type, reservation length, and start date for your Studio IDE workload. Review your order, complete the purchase, and wait for the plan to become active. When creating a Studio app from the SageMaker Studio UI, select your purchased plan from the Instance dropdown. SageMaker provisions the instance automatically with no infrastructure management required on your part. As your plan nears expiration, the IDE proactively notifies you, giving y...

AWS SAM CLI now supports AWS CloudFormation Language Extensions , enabling you to reduce duplication in your infrastructure as code (IaC) templates while retaining the full local development workflow. This accelerates your serverless development by letting you define resources once and iterate locally without waiting for cloud deployments. Developers frequently need to define multiple similar resources, such as Lambda functions, DynamoDB tables, or SNS topics, from a single template definition. However, developers who use SAM CLI to build, test, and deploy their serverless applications previously could not process templates that use CloudFormation Language Extensions. This required choosing between reducing template duplication and using SAM CLI for local development. Now, SAM CLI processes Language Extensions in memory for local operations while preserving your original template for CloudFormation deployment. You can define your resources once and test them locally across all SAM C...

If you've run NuGet Audit or a vulnerability scanner on a .NET project, you've likely seen warnings for transitive packages you never explicitly installed. In many cases, those packages — such as System.Text.Json or System.Text.Encodings.Web — are already provided at a newer version by the .NET Runtime Libraries, so the package vulnerability warning is a false positive. In .NET 10, NuGet audits transitive dependencies by default (via NuGetAuditMode set to all ), and package pruning removes packages from the restore graph when the .NET Runtime Libraries already provide them. In our telemetry, projects with these defaults have 70% fewer transitive vulnerability reports compared to projects using the previous defaults. Background: How We Got Here Many libraries on nuget.org target netstandard2.0 for maximum compatibility, and still carry dependencies on packages like System.Memory and System.Text.Json — packages that are now part of the .NET Runtime Libraries . And this...

Today, AWS announces that the AWS Partner Central agents now accelerate opportunity creation through natural language conversation. AWS Partner Central agents , released on March 16, 2026, are AI-powered capabilities built on Amazon Bedrock AgentCore that help partners surface pipeline insights, advance deals with next-step recommendations, and identify funding opportunities. With this update, partners create opportunities through a short conversation instead of completing a multi-step form, so partner sales teams spend less time on data entry and more time selling. Partners describe a deal in natural language, upload meeting notes, proposals, or call transcripts (PDF, DOCX, Excel, TXT), or clone an existing opportunity. The agent extracts the information, enriches customer details, and recommends improvements — such as adding missing context, correcting field values, or strengthening the business problem statement — so partners submit higher-quality opportunities, improve pipeline h...

Amazon CloudWatch Logs now supports retrieving up to 100,000 results using the Logs Insights query language. Customers can specify the limit in their query using the LIMIT command. Previously, customers were limited to 10,000 results and had to split their queries into smaller time ranges to retrieve all results. With this launch, customers can view a larger set of results and use existing features such as patterns, visualization, and export on the full 100,000 result set. The GetQueryResults API has also been updated to support pagination; each invocation can return up to 10,000 results along with a token that can be used to fetch the next set of results. The increased query result limits are available in all commercial AWS regions. You can execute queries and view up to 100,000 results using the Amazon CloudWatch console, AWS CLI, AWS CDK, and AWS SDKs. To learn more, see the Amazon CloudWatch Logs documentation . Post Updated on May 15, 2026 at 10:00PM