Category: Management Tools

Learn how the AMA Agentic Platform, built on Amazon Web Services (AWS) using Amazon Bedrock AgentCore. The solution puts AI directly into the hands of all 1,800-plus employees, a shift from treating AI as a feature to working with AI as a colleague.

In this post, we discuss what changed in federal logging requirements from M-21-31 to M-26-14, and how agencies can prepare ahead of the forthcoming Cybersecurity and Infrastructure Security Agency (CISA) logging reference architecture (LRA).

In Part 2 of our two-part series, we discuss the architecture of the Signal-Activated Agent Pattern and its application for proactive government AI. For Part 1, see Signal-activated generative AI: How agencies can reach more people and react faster.

This post explores how an agentic AI architecture on Amazon Web Services (AWS) modernizes the procurement lifecycle from solicitation to proposal evaluation while maintaining compliance with government regulations including United States of America FAR (Federal Acquisition Regulation),United States of America DFARS (Defense Federal Acquisition Regulation), and Canadian procurement frameworks (Public Service Procurement Canada (PSPC) /Shared Services Canada (SSC).

This post presents two complementary patterns for implementing per-user token guardrails on Amazon Bedrock from Amazon Web Services (AWS).

In this post, we discuss how AWS and Wiz support security and resilience for AMCs to help keep the focus more on patient care while maintaining a robust, secure operating environment.

As organisations modernise to meet the evolving expectations of the Australian Government, delivering secure, cloud-based services has become a commercial and operational necessity. This transformation brings a critical challenge: maintaining a hardened security posture while aligning to the Information Security Registered Assessors Program (IRAP) assessment requirements and priorities.

The cost dimensions of agentic workloads on Amazon Web Services (AWS) are invisible to many organizations beginning their agentic journey. It’s straightforward to track tokens consumed because this dimension translates directly to your bill. But most organizations can’t determine the cost per request or the cost to answer a single user question. Without understanding the cost to answer a single user question, organizations are blind to cost issues. In this post, I talk about how to gain visibility into your agentic costs, and I identify three things you can do to better control your costs.

Catching a compliance violation in production is expensive. Catching it in a pull request is nearly free. In this post, we demonstrate how to build a multi-tool infrastructure as code (IaC) validation pipeline that checks AWS CloudFormation templates and Terraform configurations against Federal Risk and Authorization Management Program (FedRAMP) 20x Key Security Indicators (KSIs) before deployment. Combined with the preventive controls from Preventive controls for FedRAMP 20x: Using SCPs and guardrails to enforce KSIs and the methods to be described in future blog posts, this creates a full-lifecycle compliance architecture.

This post is for two audiences. The first is agencies already running MARS-E-compliant workloads on AWS that are looking to map their existing posture onto the new framework. The second is agencies planning a migration from on-premises infrastructure where ARC-AMPE will be in scope from the first day.