opentofu-ecr-provision

Provision AWS ECR repositories with GitHub Actions OIDC integration and S3 Terraform state.

4|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/darellchua2/opencode-config-template --skill opentofu-ecr-provision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opentofu-ecr-provision
Source: https://github.com/darellchua2/opencode-config-template/tree/main/skills/opentofu-ecr-provision
Command: npx skills add https://github.com/darellchua2/opencode-config-template --skill opentofu-ecr-provision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provision AWS ECR repositories with GitHub Actions OIDC integration following BETEKK standards.

Core Features & Use Cases

  • ECR Repository Creation with proper configuration and lifecycle policies
  • GitHub OIDC Integration to set up IAM roles for GitHub Actions to push/pull images
  • State Management: configure S3 backend for Terraform state management
  • IAM Role Patterns: implement standardized roles with OIDC trust relationships
  • Variable Naming: follow BETEKK naming conventions for consistency
  • Modular Structure: use reusable modules for ECR and IAM resources
  • Best Practices: security, tagging, and high-availability considerations

Quick Start

Use this skill to provision a new ECR repository and configure GitHub Actions OIDC integration for a sample service.

Frequently Asked Questions about opentofu-ecr-provision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision AWS ECR with GitHub Actions OIDC integration?

To provision AWS ECR with GitHub Actions OIDC, you create repositories with lifecycle policies and configure IAM roles with OIDC trust relationships so GitHub Actions can push and pull images securely.

How do I manage Terraform state when provisioning ECR repositories?

Managing Terraform state for ECR provisioning requires configuring an S3 backend to securely store and manage your infrastructure-as-code state files across deployments.

Do I need specific IAM role patterns for GitHub Actions to access ECR?

Yes, you need standardized IAM roles configured with OIDC trust relationships to securely grant GitHub Actions the necessary permissions to push and pull ECR container images without long-lived credentials.

Can I use a modular Terraform structure to provision ECR and IAM resources?

Yes, you can use reusable Terraform modules to provision ECR and IAM resources, ensuring consistent variable naming conventions and standardized infrastructure patterns across new service deployments.

What is the best way to standardize ECR configuration for new service deployments?

The best way to standardize ECR configuration is applying modular Terraform structures with consistent variable naming, S3 state management, and standardized IAM roles with GitHub OIDC trust relationships.

Does GitHub Actions OIDC integration work with S3-based Terraform state for ECR migrations?

Yes, GitHub Actions OIDC integration works alongside S3-based Terraform state management to securely handle ECR migrations and new service deployments using standardized IAM roles and modular configurations.