Category: Management Tools

In the post Automate AWS GovCloud (US) account creation using AWS Organizations APIs, we showed how to programmatically create GovCloud (US) accounts using AWS Organizations APIs. That post ends at account creation—the new accounts exist but the standard account remains in the organization root while the GovCloud (US) account remains a standalone account. You must manually complete the steps to join a GovCloud (US) organization and move accounts to the correct organizational units (OUs).

In this post, we show how Pariveda and Amazon Web Services (AWS) worked with HS1 to build real-time voice documentation for dental visits. The solution uses Amazon Transcribe for streaming speech recognition and Amazon Bedrock for structured note generation and orchestration. We also explain the architectural choices required to support real-time performance, template-driven output, security controls, and production scale.

Under legacy Federal Risk and Authorization Management Program (FedRAMP) Rev5, continuous monitoring meant monthly deliverables and annual assessments. Under FedRAMP 20x, it means persistent, automated validation where the status of your security posture is always known. In this post, we operationalize that model using AWS Security Hub, AWS Config conformance packs, Amazon GuardDuty, Amazon Inspector, and Sigma detection rules to build an always-on monitoring architecture.

This post describes the program for the 2026 cycle, the services it covers, and how eligible campaigns and committees can enroll. Since AWS first joined DDC in 2020 and expanded the offering in 2022 and again in 2024, eligible campaigns and committees of any size and on either side of the aisle have used these services to protect the data, identities, and applications they rely on through Election Day.

Learn what Amazon Web Services (AWS) and Eastern Switzerland University of Applied Sciences (OST) are now tackling together as part of a new collaboration under the AWS Cloud Innovation Lab program.

Most security teams know what’s needed to defend their organization. Regulatory guidance is available, threat intelligence sharing has increased, and risks are well-documented. So why are healthcare and life sciences (HCLS) groups, from commercial payors to public health systems, still facing recurring incidents or falling behind in protecting sensitive information? The answer is the execution gap: the space between knowing what to do and the ability to get it done.

In this post, we walk through the evidence pipeline, from Amazon Web Services (AWS) Config evaluations and AWS Security Hub findings through transformation and storage, to producing the dual-format output that satisfies FedRAMP 20x Phase 2 completeness requirements.

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.