How do I install the Config skill?

Run npx skillmds@latest add tomevault-io/config-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Config safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Config?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Config free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Config?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Config by tomevault-io — Agent Skill

Name: Config
Author: tomevault-io

Config

Reads and modifies Elastic Beanstalk environment configuration including environment variables, scaling, instance types, and tags. Use when user says "show config", "change settings", "environment variables", "eb config", "eb setenv", "eb printenv", "eb scale", "change instance type", "configure scaling", "HTTPS listener", "config template", or "tags". For environment creation use environment skill. For SSL setup use eb-infra skill. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Configuration

Read, update, and manage Elastic Beanstalk environment configuration using the EB CLI.

When to Use

View or edit environment configuration
Set or view environment variables
Scale instances
Save/apply configuration templates
Manage environment tags
Configure HTTPS, scaling, instance type, enhanced health

When NOT to Use

Creating environments → use environment skill
SSL certificate management → use eb-infra skill
Deploying code → use deploy skill
Secrets Manager / SSM → use eb-infra skill

Interactive Config Editor

Note: eb config opens an interactive editor ($EDITOR). For non-interactive use, prefer aws elasticbeanstalk describe-configuration-settings to read and aws elasticbeanstalk update-environment --option-settings to write.

eb config
eb config <env-name>

Environment Variables

eb printenv                              # View
eb printenv <env-name>                   # View specific env
eb setenv KEY1=value1 KEY2=value2        # Set
eb setenv KEY1=                          # Remove

Quick Scale

eb scale <number>
eb scale <number> <env-name>

Save/Apply Configuration Templates

eb config save --cfg <config-name>       # Save current config
eb config --cfg <config-name>            # Apply saved config
eb config get <config-name>              # Download saved config to .elasticbeanstalk/
eb config put <config-name>              # Upload local config to S3

Validate Configuration Before Applying

aws elasticbeanstalk validate-configuration-settings \
  --application-name <app-name> \
  --environment-name <env-name> \
  --option-settings file://options.json \
  --output json

Tag Management

eb tags --list                           # List tags
eb tags --add "Team=backend,Env=prod"    # Add
eb tags --update "Env=staging"           # Update
eb tags --delete "OldTag"                # Delete

Common Configuration Tasks

HTTPS listener:

aws:elbv2:listener:443:
  ListenerEnabled: 'true'
  Protocol: HTTPS
  SSLCertificateArns: arn:aws:acm:region:account:certificate/cert-id

Scaling:

aws:autoscaling:asg:
  MinSize: '2'
  MaxSize: '10'
aws:autoscaling:trigger:
  MeasureName: CPUUtilization
  UpperThreshold: '70'

Instance type:

aws:autoscaling:launchconfiguration:
  InstanceType: t3.medium

Enhanced health:

aws:elasticbeanstalk:healthreporting:system:
  SystemType: enhanced

Platform Gotchas

AL2023/AL2 Node.js: The aws:elasticbeanstalk:container:nodejs namespace (NodeCommand, NodeVersion, etc.) is NOT supported on Amazon Linux 2 or AL2023. It only works on legacy Amazon Linux 1 (AMI). On AL2/AL2023, use a Procfile instead:

# Procfile
web: node app.js

Composability

Deploy after config change: Use deploy skill
Check status: Use status skill
Create new environment: Use environment skill
SSL/secrets/database config: Use eb-infra skill

Additional Resources

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: config-4description: Reads and modifies Elastic Beanstalk environment configuration including environment variables, scaling, instance types, and tags. Use when user says "show config", "change settings", "environment variables", "eb config", "eb setenv", "eb printenv", "eb scale", "change instance type", "configure scaling", "HTTPS listener", "config template", or "tags". For environment creation use environment skill. For SSL setup use eb-infra skill. Use when this capability is needed.---# ConfigurationRead, update, and manage Elastic Beanstalk environment configuration using the EB CLI.## When to Use- View or edit environment configuration- Set or view environment variables- Scale instances- Save/apply configuration templates- Manage environment tags- Configure HTTPS, scaling, instance type, enhanced health## When NOT to Use- Creating environments → use `environment` skill- SSL certificate management → use `eb-infra` skill- Deploying code → use `deploy` skill- Secrets Manager / SSM → use `eb-infra` skill---## Interactive Config Editor> **Note:** `eb config` opens an interactive editor (`$EDITOR`). For non-interactive use, prefer `aws elasticbeanstalk describe-configuration-settings` to read and `aws elasticbeanstalk update-environment --option-settings` to write.```basheb configeb config <env-name>```## Environment Variables```basheb printenv # Vieweb printenv <env-name> # View specific enveb setenv KEY1=value1 KEY2=value2 # Seteb setenv KEY1= # Remove```## Quick Scale```basheb scale <number>eb scale <number> <env-name>```## Save/Apply Configuration Templates```basheb config save --cfg <config-name> # Save current configeb config --cfg <config-name> # Apply saved configeb config get <config-name> # Download saved config to .elasticbeanstalk/eb config put <config-name> # Upload local config to S3```## Validate Configuration Before Applying```bashaws elasticbeanstalk validate-configuration-settings \ --application-name <app-name> \ --environment-name <env-name> \ --option-settings file://options.json \ --output json```## Tag Management```basheb tags --list # List tagseb tags --add "Team=backend,Env=prod" # Addeb tags --update "Env=staging" # Updateeb tags --delete "OldTag" # Delete```## Common Configuration Tasks**HTTPS listener:**```yamlaws:elbv2:listener:443: ListenerEnabled: 'true' Protocol: HTTPS SSLCertificateArns: arn:aws:acm:region:account:certificate/cert-id```**Scaling:**```yamlaws:autoscaling:asg: MinSize: '2' MaxSize: '10'aws:autoscaling:trigger: MeasureName: CPUUtilization UpperThreshold: '70'```**Instance type:**```yamlaws:autoscaling:launchconfiguration: InstanceType: t3.medium```**Enhanced health:**```yamlaws:elasticbeanstalk:healthreporting:system: SystemType: enhanced```## Platform Gotchas**AL2023/AL2 Node.js:** The `aws:elasticbeanstalk:container:nodejs` namespace (NodeCommand, NodeVersion, etc.) is **NOT supported** on Amazon Linux 2 or AL2023. It only works on legacy Amazon Linux 1 (AMI). On AL2/AL2023, use a `Procfile` instead:```# Procfileweb: node app.js```---## Composability- **Deploy after config change**: Use `deploy` skill- **Check status**: Use `status` skill- **Create new environment**: Use `environment` skill- **SSL/secrets/database config**: Use `eb-infra` skill## Additional Resources- [Configuration Options](../_shared/references/config-options.md)- [Cost Optimization](../_shared/references/cost-optimization.md)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/shinmc) — claim your Tome and manage your conversions.

Frequently asked questions