cloudwatch-appsignals-mcp-server - config

[josephschoi]

Describe the bug

Can we change the config Auth method with the other CW server so we don't have two separate methods?
Change from:
"env": {
"AWS_ACCESS_KEY_ID": "[AWS Access Key ID]",
"AWS_SECRET_ACCESS_KEY": "[AWS Access Key]",
"AWS_REGION": "[AWS Region]",
"FASTMCP_LOG_LEVEL": "ERROR"
to this:
"env": {
"AWS_PROFILE": "[The AWS Profile Name to use for AWS access]",

Expected Behavior

Current Behavior

Reproduction Steps

Possible Solution

Additional Information/Context

No response

OS

macos

Server

other

Server Version

No response

Region experiencing the issue

all regions

Other information

No response

Service quota

• I have reviewed the service quotas for this construct