AWS lambda tool mcp server - setup iam role

While I don't see specific information about the lambda-tool-mcp-server in the available sources, I can provide general guidance on AWS authentication approaches that would likely apply.

For AWS services and tools, there are modern authentication approaches that are preferred over using long-term IAM access keys. IAM roles are the recommended approach for granting AWS resource access to applications and automation pipelines.

If your lambda-tool-mcp-server is running on AWS compute services like EC2, ECS, or Lambda itself, you should be able to use IAM roles instead of hardcoded credentials. These roles automatically manage temporary credential rotation and follow security best practices.

For different deployment scenarios:

• If running on EC2: Use instance profile roles
• If using AWS-hosted CI/CD: Use service-linked roles
• If using self-hosted CI/CD tools on EC2: Use instance profile roles

IAM roles eliminate the need to store or manage long-term credentials, significantly reducing security risks. Applications that use an AWS SDK and run in AWS compute environments automatically use the IAM role credentials for authentication.

If the tool currently only mentions access keys in its documentation, you might want to check if it's using the AWS SDK underneath. If it is, it should automatically pick up role-based credentials when running in an AWS environment with an attached role, even if the documentation only mentions access keys.
Sources
Beyond IAM access keys: Modern authentication approaches for AWS | AWS Security Blog
WKLD.01 Use IAM roles for compute environment permissions - AWS Prescriptive Guidance