
Developing Applications On Managed Service For Apache Flink
This is the skill you need loaded before Claude answers anything about Apache Flink or Amazon Managed Service for Apache Flink. It enforces a critical rule: always read the reference files instead of relying on training data, because MSF has service-specific constraints that contradict generic Flink knowledge. Things like the KPU resource model, the confusing v1/v2 API naming split (kinesisanalyticsv2 for CLI, kinesisanalytics for IAM), prohibited checkpoint configs in application code, and Flink 1.x to 2.x migration gotchas. The skill includes 20+ reference files covering connectors, KPU sizing, checkpoint tuning, IAM policy mistakes, Iceberg streaming, and restart loop diagnosis. If you're building real-time data pipelines on MSF or debugging why your Flink app won't start, this removes the guesswork.
- skills.sh installs
- 5.4K
- GitHub stars
- 3.4K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add aws/agent-toolkit-for-aws --skill developing-applications-on-managed-service-for-apache-flink --agent claude-codeInstalls into .claude/skills of the current project.
Files
Managed Service for Apache Flink
Overview
Domain expertise for Apache Flink applications on Amazon Managed Service for Apache Flink (MSF). Covers development, KPU resource management, connectors, state management, monitoring, IaC deployment, and version migration.
Execute commands using available tools from the AWS MCP server when connected — it provides sandboxed execution, audit logging, and observability. When the MCP server is not available, fall back to the AWS CLI or shell as needed.
General Guidance
Before starting, ensure you have a clear understanding of the user persona, use case, and requirements:
STOP: Determine the users background and use case before proceeding:
- Are they new to Flink? New to Managed Service for Apache Flink?
- Are they familiar with Java development?
- Is the use case complex with lots of business logic? Or simple and declarative?
These will inform how to organize the project, and whether to use Flink Table API or DataStream API. In general, assume the DataStream API.
Example Workflow for New Applications
Sponsors
Details
- Repository
- github.com/aws/agent-toolkit-for-aws
- Categories
- Testing & QA, AI & Agent Building, Cloud & Infrastructure, CLI & Terminal
- First seen
- Jul 14, 2026
More from aws/agent-toolkit-for-aws
All 56- Creating Ec2 Image Builder Pipeline3.9K
- Aws Iam10.9K
- Aws Serverless10.9K
- Aws Observability10.7K
- Aws Containers10.1K
- Aws Cdk10.1K
- Aws Billing And Cost Management9.6K
- Aws Cloudformation9.4K
- Amazon Bedrock9K
- Aws Messaging And Streaming8.7K
- Aws Sdk Js V3 Usage8.5K
- Aws Sdk Python Usage8.3K
- Securing S3 Buckets7.4K
- Connecting To Data Source7.2K
- Creating Secrets Using Best Practices7.2K
- Exploring Data Catalog7.1K
- Querying Data Lake7.1K
- Storing And Querying Vectors7K
- Connecting Lambda To Api Gateway7K
- Aws Sdk Swift Usage7K
- Ingesting Into Data Lake7K
- Aws Amplify7K
- Creating Data Lake Table7K
- Finding Data Lake Assets7K