القائمة
Generate Terraform for AWS ECR repositories and EKS pull access needed by KAS/NVCF. Use after eks-cluster or eks-nodes and before ecr-mirror; this skill creates repositories only and does not mirror images.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Orchestrate an end-to-end NVIDIA self-managed streaming stack across AWS or Azure. Use when planning, generating, sequencing, deploying, or validating the full path from CSP base infrastructure through NVCF self-managed control plane, NVCF auxiliary services, caches, storage APIs, and post-deploy readiness gates. Trigger when the user asks for orchestration, full-stack setup, bring-up order, runbook, dependency sequencing, AWS/Azure streaming deployment, csp-infra plus NVCF, caches, or storage API coordination. Do not use for a single component task when the user explicitly asks only for one child skill.
Deploy DDCS as a shader cache for Kit/write-render-worker on GKE. Produces Kubernetes manifests, the Helm values override for write-render-worker (drivercachewrapper + UJITSO), and optionally runs a proof-of-life test. Use when setting up DDCS for MEGA shader caching (replacing GX cache).
Deploy NVIDIA Omniverse Content Cache (OVCC) alongside a MEGA simulation stack. Covers evaluation, sizing (NGINX queue-depth model), configuration for GCS/S3/Azure backends, Helm install from NGC (chart ovcontentcache v4.0.4), TLS setup, in-place upgrade from UCC 3.0.3, and wiring to write-render-worker and storage-service. MEGA does not use Nucleus; always disable it. Use when deploying OVCC for MEGA — whether exploring fit, sizing replicas, or ready to install.
Use for installing, debugging, or modifying NVCF GXCache across self-managed Kubernetes environments. Trigger on explicit GXCache, helm-gxcache, gxcache-init, gxcache-webhook, distributed shader cache, NVCA cache feature gates, or GXCache provider adaptation for Kubernetes clusters.
Generate the AWS network and IAM foundation for a KAS/NVCF EKS deployment: VPC, public/private subnets, route tables, Internet/NAT gateways, and base IAM/tagging inputs. Use as Stage 01 of aws-infra before eks-cluster.
Orchestrate the AWS KAS/NVCF EKS foundation by delegating to the component AWS infrastructure skills: aws-tf-conventions, aws-iam-vpc, eks-cluster, eks-nodes, eks-storage, ecr, eks-gpu-operator, eks-validate, and optionally ecr-mirror. Use when setting up, reviewing, or tearing down the full AWS foundation end-to-end; not for runtime installation, functions, or stream validation.
| name | ecr |
| description | Generate Terraform for AWS ECR repositories and EKS pull access needed by KAS/NVCF. Use after eks-cluster or eks-nodes and before ecr-mirror; this skill creates repositories only and does not mirror images. |
| version | 1.0.0 |
| author | NVIDIA Omniverse Streaming |
| tags | ["aws","ecr","terraform","registry"] |
| tools | ["Shell","Read","Write"] |
Generate Terraform for ECR repositories under a stable cluster prefix, plus repository outputs and pull permissions needed by EKS nodes or pod identity.
This skill does not copy images or charts. Use ecr-mirror for NGC to ECR
mirroring after repositories and permissions are ready.
Required:
| Input | Notes |
|---|---|
AWS_ACCOUNT_ID | AWS account that owns the target registry. |
AWS_REGION | Target ECR region. |
CLUSTER_NAME | Default ECR repository prefix. |
Optional:
| Input | Default |
|---|---|
TARGET_REPOSITORY | ${CLUSTER_NAME} |
| repository names | Derived from the manifest or declared by the caller |
| scan on push | true |
| encryption | AES256 unless a KMS key is provided |
Create repositories with this naming convention:
${TARGET_REPOSITORY}/${image-or-chart-name}
Do not mirror to the registry root. Stop if TARGET_REPOSITORY is empty.
For EKS pulls, confirm the node role or pod identity has ECR read access:
ecr:GetAuthorizationToken
ecr:BatchCheckLayerAvailability
ecr:GetDownloadUrlForLayer
ecr:BatchGetImage
Check for collisions before creating repositories:
aws ecr describe-repositories --region "$AWS_REGION" \
--query "repositories[?starts_with(repositoryName, '${CLUSTER_NAME}/')].repositoryName"
If repositories already exist with the cluster prefix, stop and ask whether to adopt, clean up, or choose a new prefix.
Expose values later skills can consume:
output "ecr_registry" {
value = "${var.aws_account_id}.dkr.ecr.${var.aws_region}.amazonaws.com"
}
output "ecr_repository_prefix" {
value = var.target_repository
}
${TARGET_REPOSITORY}/....ecr-mirror remains the only skill that copies images/charts.