Automate AWS CLI and Terraform provisioning patterns for multi-account environments.
npx skills add https://github.com/mtaku3/nix-config --skill aws-ecosystem
Please help me install this Agent Skill. Skill: AWS Ecosystem Source: https://github.com/mtaku3/nix-config/tree/main/modules/home/app/dev/claude-code/skills/aws-ecosystem Command: npx skills add https://github.com/mtaku3/nix-config --skill aws-ecosystem
The AWS ecosystem guidance consolidates configuration patterns, authentication flows, and IaC best practices to reduce setup time and misconfigurations when working with AWS CLI and Terraform.
Use Case: When migrating multiple accounts or deploying infrastructure across environments, apply these patterns to ensure consistent authorization, region handling, and state management.
Use the AWS ecosystem skill to audit and align your AWS CLI and Terraform setup with the patterns described in SKILL.md.
High-intent search queries and answers about installing and using this skill.
To configure AWS CLI SSO for Terraform, use AWS CLI v2 with SSO support to set up profile switching and token refresh, then apply Terraform AWS provider configurations for cross-account access via assume_role. This ensures consistent authorization across multi-account environments.
The best way to manage Terraform remote state in AWS is using S3 backends with DynamoDB locking. This pattern secures state files and prevents concurrent modification conflicts during infrastructure provisioning across development, staging, and production environments.
Yes, you can use OIDC federation for AWS authentication in CI/CD pipelines. This pattern eliminates long-lived credentials by implementing secure credential handling via IAM roles or credential_process, ensuring least privilege access for automated infrastructure deployments.
Yes, AWS CLI v2 is required for SSO support with Terraform workflows. The AWS ecosystem patterns depend on v2's native SSO authentication, profile switching, and token refresh capabilities to establish secure credential handling for infrastructure provisioning.
To apply default_tags in Terraform AWS provider configurations, define them within the provider block to ensure consistent tagging across all resources. This pattern reduces misconfigurations and maintains governance when deploying infrastructure across multiple AWS accounts and environments.
motoki317Configure AWS CLI profiles, SSO authentication, and Terraform AWS Provider infrastructure.
kid-sidAutomate Terraform infrastructure management with reusable modules and drift detection.
pypeadayAutomate creation and validation of least-privilege AWS IAM policies.
seb1nDefine, deploy, and manage cloud infrastructure with Terraform, Pulumi, CloudFormation, and AWS CDK.
