Run any Skill in Manus with one click

hipaa-assistant

Stars15

Forks16

UpdatedJuly 14, 2026 at 22:01

Activate when the user asks about HIPAA compliance scanning, validating AWS configurations against HIPAA Security Rule controls, or pre-deployment HIPAA checks for GenAI workloads on AWS.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

awslabs

awslabs/startups

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

name	hipaa-assistant
description	Activate when the user asks about HIPAA compliance scanning, validating AWS configurations against HIPAA Security Rule controls, or pre-deployment HIPAA checks for GenAI workloads on AWS.

HIPAA Assistant

A Go-based CLI and MCP server that scans your AWS configurations against HIPAA Security Rule controls before deployment.

What it does

Scan - Analyzes CloudFormation, Terraform, or application code for HIPAA Security Rule compliance gaps
Advise - Provides remediation steps for identified gaps
Reference - Maps each finding to the verbatim Code of Federal Regulations text (45 CFR Part 164) so you know exactly which control is at risk

How to use it

https://github.com/aws-samples/sample-hipaa-assistant

Runs as a CLI tool or as an MCP server you can invoke directly from your IDE.

Disclaimer

This tool provides cited technical guidance based on publicly available HIPAA Security Rule text (45 CFR Part 164) and AWS documentation. It is not legal advice and does not constitute a compliance certification. Work with qualified legal counsel and compliance professionals before handling PHI in production.

More from this repository

same repository

heroku-to-aws

awslabs/startups

Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku app, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, Heroku migration, move from Heroku to AWS, migrate Heroku Private Space, Heroku to Elastic Beanstalk, Heroku to ECS, Heroku to Fargate, leave Heroku, migrate off Heroku platform. Runs a 6-phase process: discover Heroku resources from Terraform files, Procfile/app.json, and optional billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Uses a flat resource model (no clustering or dependency graphs) with deterministic mapping tables for core services (Dynos → Elastic Beanstalk by default, Postgres → RDS/Aurora, Redis → ElastiCache, Kafka → MSK) and a fast-path table for 13+ common

2026-07-1815

gcp-to-aws

awslabs/startups

Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality

2026-07-1815

tf-best-practices

awslabs/startups

Best-practice authoring guidance AND a read-only policy gate for AWS Terraform generated by a migration skill. Load during any phase that writes a terraform/ directory — first as the "what to emit" posture rules + security-baseline spec, then after writing as the deterministic policy verdict. Read-only: it reports whether the generated Terraform passes; it never edits .tf files, never touches .phase-status.json, and never decides phase completion. Complements (does not replace) terraform fmt/init/validate.

2026-07-1515

agent-advisor

awslabs/startups

Unified entry point for AI-agent work on AWS: evaluate and pick a runtime, generate a full migration plan (for existing workloads), and build an executable POC — all in one flow. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, I have an agent idea what do I build, move my agents to AWS, migrate my agents to AWS with a plan, agent migration plan, add AgentCore services, add memory/gateway/identity/policy to my agent, enable AgentCore Memory, add observability to my agent, I'm already on AWS and want to add agent capabilities, migrate Temporal workers to AWS, Temporal to AWS, run Temporal on AWS, Temporal workers on AWS, we use Temporal and want to move to AWS, our service is orchestrated by Temporal, what do I build on AWS for my Temporal workers, move a Temporal-based service to AWS, Temporal Cloud or self-hosted on AWS. Runs a phased flow: Intake (entry point + technical background), Discover (ligh

2026-07-1515

llm-to-bedrock

awslabs/startups

Use when the user wants to migrate code that calls OpenAI, Gemini/Google AI, or the Anthropic API to Amazon Bedrock — a pure model/SDK rewrite. End-to-end: assesses the codebase, then rewrites SDK calls, evaluates output quality against Bedrock, and delivers a ready-to-merge git branch. Not for: agent runtime selection, agentic architecture decisions, or agent migration planning — use agent-advisor for those. Not for standalone Bedrock cost estimates or infrastructure-only migration. The Assess phase is handled by this plugin's own gcp-to-aws skill.

2026-07-1515

aidlc-lite

awslabs/startups

Lightweight AI development lifecycle for building on AWS. A simplified take on the AI-DLC philosophy — think together, then build fast. Acts as a design partner that understands intent, proposes alternatives with trade-offs, and ships working code without the ceremony of full requirements/design/spec documents. Use when a founder says "build X on AWS", "add Y to my stack", "scaffold an API", or "write the CDK for Z".

2026-07-0815

name	hipaa-assistant
description	Activate when the user asks about HIPAA compliance scanning, validating AWS configurations against HIPAA Security Rule controls, or pre-deployment HIPAA checks for GenAI workloads on AWS.

HIPAA Assistant

A Go-based CLI and MCP server that scans your AWS configurations against HIPAA Security Rule controls before deployment.

What it does

Scan - Analyzes CloudFormation, Terraform, or application code for HIPAA Security Rule compliance gaps
Advise - Provides remediation steps for identified gaps
Reference - Maps each finding to the verbatim Code of Federal Regulations text (45 CFR Part 164) so you know exactly which control is at risk

How to use it

https://github.com/aws-samples/sample-hipaa-assistant

Runs as a CLI tool or as an MCP server you can invoke directly from your IDE.