Skip to main content
Glama
AWS Health MCP Server

AWS Health MCP Server

Official
by aws-samples

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOG_LEVELNoLogging level (DEBUG, INFO, WARNING)INFO
AWS_REGIONNoRegion (Health API is us-east-1 only)us-east-1
AWS_PROFILENoAWS credentials profile
HEALTH_API_TIMEOUTNoAPI timeout in seconds30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_service_healthA

Get current AWS service health events.

Returns active and upcoming AWS health events with descriptions and timelines. Consider summarize_health_events first: this returns full descriptions and can be very large on a busy account.

Args: regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "Show me all current AWS service health issues"

  • "What's broken in us-west-2?"

  • "Are there any active AWS service disruptions?"

get_affected_entitiesA

Get affected entities for all open AWS health events.

Shows resources impacted by active health events, grouped by event and status.

Example prompts:

  • "What resources are affected by current AWS issues?"

  • "Show me all impacted AWS entities"

  • "Which AWS resources are experiencing problems?"

get_service_eventsA

Get health events for a specific AWS service.

Args: service: The AWS service name (e.g., 'EC2', 'RDS', 'LAMBDA'). Case insensitive. Use list_event_types to discover the codes AWS Health uses. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What's happening with EC2 right now?"

  • "Any RDS issues in eu-west-1?"

  • "Are there any problems with S3?"

get_completed_eventsA

Get completed/closed health events.

Args: service: Optional. The AWS service name to filter by. Case insensitive. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "Show me recently resolved AWS issues"

  • "What EC2 problems were fixed in us-east-1?"

  • "Get history of resolved incidents"

get_scheduled_changesA

Get all scheduled changes/maintenance events across AWS services.

Returns upcoming maintenance windows, planned updates, and infrastructure improvements.

Args: regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What maintenance is planned for AWS services?"

  • "Any upcoming maintenance in eu-west-1?"

  • "When is the next AWS maintenance?"

get_org_health_eventsA

Get health events across your AWS Organization.

If no arguments are provided, returns all active org health events.

Args: service: Optional. The AWS service name to filter by. Case insensitive. account_id: Optional. The AWS account ID to filter events for. status: Optional. 'active' (default) or 'closed'. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "Show me org-wide AWS health events"

  • "What issues affect account 123456789012?"

  • "Any org-wide events in ap-southeast-2?"

get_org_service_healthA

Get current AWS service health events across your organization.

Provides a comprehensive overview of active health events across all accounts in your AWS Organization.

Example prompts:

  • "Show me all current AWS service health issues across my organization"

  • "Are there any active AWS service disruptions affecting multiple accounts?"

get_org_affected_entitiesA

Get affected entities for AWS health events across your organization.

Args: account_id: Optional. The AWS account ID to filter events for. event_arn: Optional. The ARN of a specific event to get details for.

Example prompts:

  • "What resources are affected by current AWS issues across my organization?"

  • "Show me impacted entities in account 123456789012"

get_org_service_eventsA

Get health events for a specific AWS service across your organization.

Args: service: The AWS service name (e.g., 'EC2', 'RDS', 'LAMBDA'). Case insensitive. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What's happening with EC2 across my organization?"

  • "Show me all RDS issues affecting my AWS accounts"

get_org_account_eventsA

Get health events for a specific AWS account in your organization.

Args: account_id: The 12-digit AWS account ID. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2'].

Example prompts:

  • "What health events are affecting account 123456789012?"

  • "Show me all issues in my account"

get_org_scheduled_changesA

Get scheduled changes/maintenance events across your AWS Organization.

Returns upcoming maintenance affecting accounts in your organization.

Example prompts:

  • "What maintenance is planned across my organization?"

  • "Show me upcoming AWS changes affecting my accounts"

get_event_detailsA

Get the full detail of specific AWS health events by ARN.

Use this to drill into events surfaced by the listing tools, instead of pulling every description for every event.

Args: event_arns: One or more event ARNs, as returned by the listing tools.

Example prompts:

  • "Give me the full details of that EC2 retirement event"

  • "What exactly does event arn:aws:health:... say?"

summarize_health_eventsA

Count active AWS health events without returning their descriptions.

A cheap overview for "is anything wrong?" questions. Listing tools return full descriptions and can run to tens of thousands of tokens; this returns counts only.

Args: group_by: One of 'service', 'status', 'category' or 'region'. include_closed: Include resolved events as well as open/upcoming ones.

Example prompts:

  • "How many AWS health events are open, by service?"

  • "Give me a summary of current AWS issues"

  • "Which regions have active events?"

count_affected_entitiesA

Count the resources affected by events, without listing them.

Use this before the entity-listing tools when an event could touch thousands of resources.

Args: event_arns: One or more event ARNs.

Example prompts:

  • "How many instances does this retirement event affect?"

  • "What's the blast radius of these events?"

list_affected_accountsB

List the organization accounts affected by a single health event.

Args: event_arn: The ARN of an organization health event.

Example prompts:

  • "Which accounts does this event affect?"

  • "How wide is the blast radius of this event across my organization?"

list_event_typesA

List the event types AWS Health can report, optionally for one service.

Also the way to discover valid service names: the service codes AWS Health uses do not always match the marketing name (Step Functions is 'STATES', EventBridge is 'EVENTS').

Args: service: Optional. Restrict to one AWS service. Case insensitive. category: Optional. One of 'issue', 'accountNotification', 'scheduledChange', 'investigation'.

Example prompts:

  • "What service names does AWS Health use?"

  • "What kinds of EC2 events can AWS Health report?"

find_events_for_resourcesA

Find which health events affect specific resources of yours.

Answers "is my instance / cluster / database affected by anything?".

Matching goes through DescribeAffectedEntities, where entity values match exactly. The equivalent filter on DescribeEvents cannot be used for this: it also returns events that have no entities at all, so a resource ID that exists nowhere still comes back with matches.

Args: entity_values: Resource identifiers, e.g. ['i-1234567890abcdef0']. include_closed: Also search resolved events, not just open/upcoming.

Example prompts:

  • "Is i-1234567890abcdef0 affected by any AWS issue?"

  • "Do any current events touch my cluster my-prod-cluster?"

check_health_accessA

Diagnose whether this server can actually reach the AWS Health API.

Reports the calling identity, whether the account's support plan allows Health API access, and whether organization view is enabled. Run this first when other tools return access errors.

Example prompts:

  • "Why can't you see my AWS health events?"

  • "Is AWS Health set up correctly?"

  • "Do I have organization-wide health access?"

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 18 tools

Disambiguation3/5

There are systematic org/non-org pairs (get_service_health vs get_org_service_health, get_affected_entities vs get_org_affected_entities, etc.) which are nameable-apart, but the fuzzy boundaries between get_service_health and get_service_events, and between the several overlapping event-listing tools, create real misselection risk.

Naming Consistency5/5

All names follow a consistent snake_case verb_noun pattern (get_, list_, count_, summarize_, find_, check_) with predictable prefixes for org-scoped variants.

Tool Count4/5

18 tools is at the upper end but justified by the read-only domain spanning single-account, org-wide, entity, and summary operations. It is slightly heavy but each tool earns a place.

Completeness4/5

The surface covers listing, drilling into details, affected entities, counts, summaries, event-type discovery, org-wide views, and an access diagnostic — strong lifecycle coverage for a read-only API. Minor gaps around pagination/continuation handling keep it from a 5.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues