auto-provision

Provision AWS infrastructure resources from infra.json with idempotent behavior.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill auto-provision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-provision
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-automation/skills/auto-provision
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill auto-provision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the provisioning of AWS resources required by AI automation agents, based on infra.json, with idempotent behavior and audit logging.

Core Features & Use Cases

  • Idempotent resource provisioning: Creates or skips DynamoDB, SQS, S3, SNS, IAM, Lambda, and API Gateway resources according to infra.json.
  • Infra.json synchronization: Updates infra.json with ARNs and IDs to keep deployment pipelines aligned.
  • Provision-deploy workflow: Supports end-to-end provisioning followed by code deployment steps in the /auto-pipelines workflow.

Quick Start

Run /auto-provision to provision all resources defined in infra.json and prepare the environment for deployment.

Frequently Asked Questions about auto-provision

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

FAQPage Schema
How do I provision AWS infrastructure for AI automation agents?

You provision AWS infrastructure for AI automation by running a command that reads a central infra.json file to create DynamoDB, SQS, S3, SNS, IAM, Lambda, and API Gateway resources with idempotent behavior.

What is idempotent AWS resource provisioning and why is it needed?

Idempotent AWS resource provisioning creates required infrastructure or safely skips existing resources to avoid duplication, ensuring AI automation environments can be replicated across regions without causing deployment errors.

How do I configure DynamoDB, Lambda, and API Gateway for replicated environments?

You configure these AWS resources by defining the required tables, functions, and API wiring within a central infra.json file, which the provisioning process reads to deploy consistent environments across multiple regions.

Can I synchronize AWS resource ARNs with my deployment pipeline configuration?

Yes, the provisioning process updates infra.json with the ARNs and IDs of newly created resources, keeping your deployment pipelines aligned with the actual AWS infrastructure state automatically.

Does AWS infrastructure provisioning work for multi-region AI environments?

Yes, this provisioning approach specifically targets repositories requiring replicated environments across regions, handling existing resources gracefully to ensure ready-to-deploy pipelines in each targeted region.

Why do I need an SQS dead-letter queue and SNS topics for Lambda automation?

An SQS DLQ captures failed Lambda event processing to prevent data loss, while SNS topics enable decoupled event-driven communication, both provisioned automatically to support reliable AI automation workflows.