All integrations
Get an API key
Amazon Web Services
EC2, Lambda, IAM and the rest of the AWS API surface.
Cloud and infrastructure
How an agent reaches it
MCPREST APICLI
How you authenticate
API key
- Create an IAM user or role with least-privilege permissions.
- Store the SECRET access key as the credential value and put the access key ID in the injection settings.
- Set the sigv4 `service` to match the AWS service you are calling (ec2, s3, lambda) and the region to match the endpoint.
Connection details
- Base URL
- https://{service}.{region}.amazonaws.com
- Pagination
- cursor
Common endpoints
| who am I | POST https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15 |
| list EC2 instances | POST https://ec2.{region}.amazonaws.com/?Action=DescribeInstances&Version=2016-11-15 |
| list Lambda functions | GET https://lambda.{region}.amazonaws.com/2015-03-31/functions |
Worth knowing
- Each AWS service is its own API with its own protocol: some are query-string based, some JSON, some XML. There is no single shape.
- The sigv4 `service` and `region` must match the endpoint exactly or the signature is rejected.
- The CLI is almost always the right lane here. Reach for raw HTTP only for a single simple call.