Posts

Amazon S3 Object Lock now supports variable retention with event holds - devamazonaws.blogspot.com

Amazon S3 Object Lock now supports variable retention, allowing 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. You can apply event holds to individual objects, configure them as a bucket default, or apply them at scale with S3 Batch Operations. New AWS IAM and bucket policy condition keys let you control who can set or release holds and enforce minimum or maximum hold durations. AWS CloudTrail lo...
Post a Comment
Read more

[MS] A sample use of the winstart.bat file in Windows 95 - devamazonaws.blogspot.com

In my earlier discussion of the the litte-known winstart.bat batch file in Windows 3.1 and Windows 95 , Danielix Klimax wondered whether it was useful in Windows 95, or whether it was primarily used only in Windows 3.x . I found a reference to winstart.bat in the Windows 3.1 SETUP.TXT file : Using the TIGA Display Driver ------------------------------- If you are using the TIGA display driver, you must load the TIGACD.EXE MS-DOS driver manually before running Setup to upgrade Windows. Otherwise, Windows will not upgrade your system properly. After successfully setting up Windows, you can increase the amount of conventional memory available to non-Windows applications when Windows is running in 386 enhanced mode by loading TIGACD.EXE from the WINSTART.BAT file. The WINSTART.BAT file runs only in 386 enhanced mode. If you want to run Windows in standard mode, you must load TIGACD.EXE manually. For more information, see the README.WRI online document. TIGA is the Texas Instrume...
Post a Comment
Read more

Amazon GuardDuty adds optional threat detection rules - devamazonaws.blogspot.com

Amazon GuardDuty now offers Custom Detection Rules, a library of 35 prebuilt, opt-in rules for CloudTrail management events that let you extend threat detection coverage to match your environment. Custom Detection Rules produces 26 unique finding types mapped to 10 MITRE ATT&CK® tactics, without the heavy lifting of log ingestion, normalization, or storage. Some threat techniques, such as sharing an AMI externally, disabling flow logs, or signing in without MFA, could be meaningful indicators of compromise in some accounts but routine in others. Custom Detection Rules lets you enable these detections only where the activity is unexpected — expanding your TTP coverage tailored to your environment. To get started, browse Custom Detection Rules via the GuardDuty console or API, and enable rules in dry-run mode to evaluate detection efficacy before going live. Custom Detection Rules is available in all AWS commercial Regions and the AWS GovCloud (US) Regions. To learn more, s...
Post a Comment
Read more

[MS] Why don't we allow stacks to be sparse, instead of forcing them to be contiguous? - devamazonaws.blogspot.com

When I discussed why we don't just make the entire stack out of guard pages , commenter BCS wondered , "Why require that the stack use contiguously mapped pages? What would break if only touched pages got mapped in? That could actually be a good thing for example with a function that wanted to alloca 512MB on the stack but only read/writes a few pages." So the question is asking why the stack must be contiguous. Why not let it be sparse and fault in only the pages that are touched? The first issue is that the stack check code would have to include an explicit check against the stack limit, instead of just walking down the stack a page at a time. This explicit check is needed to avoid security vulnerabilities if somebody manages to alloca a buffer so large that it goes past the end of the stack reservation entirely. If you go a single page at a time, you will eventually hit the no-access page that marks the end of the stack. But if you can leap over multiple pages at...
Post a Comment
Read more

[MS] The Agentic Road to Revenue - devamazonaws.blogspot.com

Image
The Agentic Road to Revenue   From SaaS concept to Azure Marketplace Building a SaaS application is only part of becoming a commercial software provider. To sell through the Microsoft commercial marketplace, the application also needs tenant isolation, subscription lifecycle management, billing integration, security evidence, and a publishable Partner Centre offer. To make this journey easier we have built SaaS_Skills into GIT-APE. This article follows Contoso Azure SaaS through seven stages, from selecting an offer model and applying the SaaS Architecture Reference Design to publishing its Azure Marketplace listing. All code was opened in VScode and git-ape run from the chat there. This is based on a fictious SaaS app you can find here The SaaS_Skills can be found here The Architecture Reference Desing they reference can be found here We will be run the SaaS journey from concept to Public offer using the below skills now found in to git-ape Step Skill(s) ...
Post a Comment
Read more

Amazon Bedrock Managed Knowledge Base now supports automatic sync scheduling for data source connectors - devamazonaws.blogspot.com

AWS announces automatic sync scheduling for Amazon Bedrock Managed Knowledge Base, a fully managed retrieval-augmented generation (RAG) service that handles data ingestion, storage optimization, and advanced retrieval without requiring you to manage vector databases or data pipelines. Previously, keeping your knowledge base current required manually triggering a sync each time your source data changed or building a custom solution. Now, you can configure daily, weekly, or monthly sync schedules for all native data source connectors, so your AI agents always retrieve the most up-to-date information. With automatic sync scheduling, you can match your sync frequency to how often your source content changes. For example, set a daily sync for a rapidly evolving customer support knowledge base in Confluence, a weekly sync for SharePoint policy documents that update periodically, or a monthly sync for reference materials stored in Amazon S3. This eliminates the need to build and maintain cus...
Post a Comment
Read more

Amazon ECS introduces Early Success Criteria for service deployments - devamazonaws.blogspot.com

Amazon Elastic Container Service (Amazon ECS) now supports Early Success Criteria for rolling service deployments, giving you the flexibility to define when a deployment is considered successful based on your confidence level and the operational needs of your workload. This can help you complete deployments sooner and unblock subsequent deployments, CI/CD pipelines, and other dependent operations. With Early Success Criteria, you configure the healthy percent - the proportion of desired tasks that must be running and healthy on the target service revision before the deployment is marked successful. For example, with a desired count of 100 and a healthy percent of 90%, Amazon ECS marks the deployment successful after 90 tasks are healthy and continues launching the remaining tasks through regular service scaling, outside the deployment lifecycle. This can benefit workloads running on specialized or constrained capacity, such as GPU-accelerated inference workloads, where hardware ...
Post a Comment
Read more