AWS Data Processing Plan
FortgeschrittendataMindestens 64K Kontext
Plans governed data-processing workflows across AWS Glue, EMR, EMR Serverless, Athena, S3, and IAM. Produces catalog, compute, orchestration, data-quality, encryption, cost, and observability decisions with read-only discovery first and explicit approval before resource changes.
Anwendungsfälle
- Choosing between Glue, EMR, EMR Serverless, and Athena
- Planning governed catalogs and ETL workflows
- Auditing data-processing IAM and encryption
- Estimating cost and operational controls before rollout
Beispiel-Prompt
Design an AWS data-processing plan for this workload. Sources: [systems, formats, sizes, arrival pattern] Consumers: [queries, dashboards, ML, exports] Constraints: [latency, region, retention, compliance, budget] Produce: 1. A service-selection decision for Glue, EMR, EMR Serverless, Athena, and S3. 2. Catalog, partitioning, schema-evolution, and data-quality rules. 3. Read-only discovery steps before any mutation. 4. IAM, encryption, network, and sensitive-data controls. 5. Cost model, quotas, metrics, and failure recovery. 6. A staged implementation plan with acceptance tests.
Empfohlene Modelle
Kompatible Werkzeuge
claude-codecursorkirogemini-cliany
Modalitäten
Eingabe: text, code, file
→Ausgabe: text, code
Ähnliche Skills
Autor
OpenModels Community
Herausgeber
Verifizierte QuelleOpenModels Community
Aus der verlinkten Quelle adaptiert