aws/agent-toolkit-for-aws

managing-glue-jobs

Guides AWS Glue customers through automatic version upgrades (auto upgrade, GlueVersion = auto) for Spark ETL jobs, step by step as the AWS Glue user guide describes: assess jobs, confirm they are safe to retry, turn on auto upgrade, set up email notificati…

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill managing-glue-jobs

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

AWS Glue auto upgrade

This skill follows Automatic version upgrades for AWS Glue jobs in the AWS Glue User Guide.

Journey

Each step names the file to read. Stop marks a point where you wait for the user's decision.

StepWhat happensReadStop
1. AssessYou check which jobs can use auto upgrade. Read-only.assess-and-turn-on.md—
2. Safe to retryThe user confirms that each job is safe to retry, and gives an email address for notifications.sameStop
3. NotificationsIf the user gave an address, you set up the emails first, so no approval email is missed.notifications.md—
4. Turn onYou set GlueVersion to auto with a full job update.assess-and-turn-on.md—
5. ReviewDays later, you show the eligibility summary and what to check.approval.mdStop
6. Approve or declineYou record the decision for each job that the user names, or decide each job on the user's blocking-issue condition.same—
7. Monitor and resultsYou report status and the auto upgrade evaluation summary.same—

Steps 1 to 4 can run in one conversation. A job that runs often can reach the approval request within an hour, so set up emails before turning on jobs. Step 5 starts after AWS Glue requests approval. Never approve in the same turn that turns on auto upgrade.

Tools

The skill uses only the AWS CLI (version 2, with the auto upgrade commands). It ships no scripts. Run each command exactly as the reference file shows it, with --region <region> --no-cli-pager. Add --profile <profile> when the user names a profile.

The AWS MCP server is recommended for working with AWS, but this skill doesn't require it. Run the commands in this skill with the AWS CLI, because the auto upgrade operations need a current AWS CLI.

Check the CLI once per session. This call makes no AWS request:

bash
aws glue get-job-upgrade-analysis --generate-cli-skeleton > /dev/null

If it fails, reply: "Your AWS CLI version doesn't support auto upgrade. To continue, update the AWS CLI to the latest version."

The assessment uses the generate_assessment tool of the spark-upgrade MCP server (assess-and-turn-on.md explains the setup). Permissions for each step are in permissions.md.

Rules

  1. Change only what the user confirmed. Before any call that changes something (update-job, create-job, start-job-upgrade-analysis, create-topic, set-topic-attributes, put-rule, put-targets, subscribe), say what will change. Run it only for jobs and resources that the user confirmed in this conversation.
  2. One decision per job, from the user's instruction. Record a decision only when the user names the job and the decision after you show its review, or when the user decides on the blocking-issue condition, for named jobs or for every waiting job: approve if the summary lists no blocking issue, decline if it lists at least one, or both. Act on that condition only if, in this turn, the job's status is WAITING_FOR_CONSENT and you read its eligibility summary. Never decide on a schedule, on a condition you can't check from the summary, or for a job that the instruction doesn't cover. A reply such as "no", "not now" or "later" isn't a decline: record nothing, and give the decline prompt.
  3. No secrets in the chat. Never repeat job argument values in a reply. Never print, store, or quote a summary link: the links are presigned, work for 1 hour, and are read only inside the one command in approval.md.
  4. No IAM changes or installs. Tell the user what to grant or install.
  5. No scripts. Write any temporary file inside the one command that uses it, and delete it in the same command.

How to reply

  • Answer first. The first sentence states the result.
  • Name the actor. Each sentence names who acts: AWS Glue or you. Don't use "we" or chatty words.
  • Use the user guide's terms. Auto upgrade, eligibility summary, auto upgrade evaluation summary, approve, decline, previous version, safe to retry, subsequent job runs. Format GlueVersion, MaxRetries, and auto as code.
  • Keep it short. Use present tense and active voice, with sentences of about 15 words and never more than 25. Put one sentence before each table or list.
  • No internal details. Don't show raw status values, analysis IDs, run counts, or service-internal names.
  • Show write modes at approval. One table row per job with its recorded write mode (append, another mode, Not recorded, or overwrite) and paths. The write mode describes what AWS Glue recorded; it never says a job is safe.
  • One question, at the end. End with the exact text that the user can enter, in code format.
dallo stesso repository

Altri Skills

Tutti gli Skills
aws
Ufficiale

deploying-containers-to-amazon-lightsail

Deploys, hosts, or runs a container or Docker app on Amazon Lightsail Container Service and returns a live, managed HTTPS URL at a flat monthly price — no cluster, VPC, load balancer, or registry to set up. Used when deploying a container image to Lightsail from a local Docker build, a public registry image, or a GitHub repo, or when a Lightsail container deployment fails or won't serve — including when the request doesn't name Lightsail but asks to run one always-on container behind a public UR

Installazioni / 1h
2
GitHub Stars
3,5K
Aggiornato
20 nov
aws
Ufficiale

managing-data-asset-access

Grants, requests, audits and removes access to data assets in an AWS data catalog (the Amazon SageMaker Catalog supported by Amazon DataZone) through catalog subscriptions over published listings. Covers requesting a subscription, approving or rejecting requests with a recorded decision, sharing a listing with a project, revoking one or many subscriptions, and confirming grant settlement. Triggers on: give another team access to a table, request access to a dataset, approve or reject an access r

Installazioni / 1h
2
GitHub Stars
3,5K
Aggiornato
20 nov
aws
Ufficiale

managing-data-catalog

Writes and curates business metadata in an AWS data catalog: the Amazon SageMaker Catalog (Amazon DataZone), or the AWS Glue Data Catalog. Detects which catalog platform an account uses before writing. Triggers on: add a description to a table, document a dataset, write a README, set an owner, add column comments, tag with a glossary term, create a business glossary, create a metadata form, publish an asset, create a data product, run the data source crawl, delete a catalog asset, attach a conve

Installazioni / 1h
2
GitHub Stars
3,5K
Aggiornato
20 nov
aws
Ufficiale

amazon-aurora-mysql

Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override de

Installazioni / 1h
2
GitHub Stars
3,5K
Aggiornato
20 nov