MCP Boxaws-mcp
Updated at 17 days ago
by RafalWilinski
92
on GitHub
Talk with your AWS using Claude. Model Context Protocol (MCP) server for AWS. Better Amazon Q alternative.
Tags
ai
amazon-q
aws
claude
llm
mcp
What is aws-mcp (AWS Multi-account Cost Processing)
AWS Multi-account Cost Processing (aws-mcp) is a solution designed to process AWS Cost and Usage Reports (CUR) across multiple AWS accounts and consolidate the data into a centralized Athena table for efficient cost analysis and reporting. It leverages AWS services like S3, Athena, Glue, and Lambda for automated processing. It is designed to be deployed via CloudFormation.
How to use
The core of deployment is using CloudFormation. The main CloudFormation template sets up the required resources. Before deploying, it is crucial to configure the following:
- S3 Bucket for CUR: An S3 bucket needs to be created where the CUR data will be delivered by AWS.
- CUR Configuration: The CUR must be configured within the AWS Billing and Cost Management console to deliver reports to the designated S3 bucket. Importantly, the CUR data should be stored with the Hive-compatible manifest file option enabled.
- CloudFormation Deployment: The CloudFormation template provided in the repository is used to provision the necessary AWS resources. The template requires parameters such as the S3 bucket name and the database name in AWS Glue.
- Permissions: Correct IAM permissions are vital to ensure the Glue crawler and other components of the infrastructure are able to read the data within the S3 bucket and execute appropriately.
Post deployment, data will be processed automatically, and a central Athena table provides aggregated cost data. Athena can then be used to run cost and usage queries.
Key features
- Multi-Account Support: Processes CUR data from multiple AWS accounts.
- Centralized Cost Data: Consolidates cost data into a single Athena table.
- Automated Processing: Automates CUR processing using AWS Glue crawler, S3 events and Lambda functions.
- CloudFormation Deployment: Simplifies deployment using CloudFormation templates.
- Athena Integration: Enables cost analysis and reporting using Athena.
- Hive-compatible manifest files support: Relies on CUR configurations using the Hive-compatible manifest file option enabled
Use cases
- Centralized Cost Reporting: Provides a single view of AWS costs across multiple accounts.
- Cost Allocation: Facilitates cost allocation to different departments or projects.
- Cost Optimization: Helps identify areas for cost optimization by analyzing cost data.
- Billing and Invoicing: Streamlines billing and invoicing processes by providing accurate cost data.
- Trend Analysis: Enables trend analysis of AWS costs over time.
FAQ
- What is the main advantage of using aws-mcp? The primary advantage is simplifying the process of aggregating and analyzing cost data from multiple AWS accounts in a centralized location, making cost management more efficient.
- What AWS services are required for aws-mcp? The solution utilizes S3, Athena, Glue, Lambda, and CloudFormation.
- How do I deploy aws-mcp? Deployment is primarily done using the provided CloudFormation template.
- What kind of data does aws-mcp process? aws-mcp processes AWS Cost and Usage Reports (CUR).
- Is there a cost associated with using aws-mcp? Yes, there will be costs associated with the AWS services used by aws-mcp, such as S3 storage, Athena queries, Glue crawler runtime, and Lambda execution.
- Does this solution handle partitioning? Yes, the Glue crawler is configured to handle partitioning of the data.
- What format should the CUR data be in? The CUR data must be configured with the Hive-compatible manifest file option.