[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74671":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":15,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":23,"readmeContent":24,"aiSummary":25,"trendingCount":16,"starSnapshotCount":16,"syncStatus":26,"lastSyncTime":27,"discoverSource":28},74671,"taws","huseyinbabal\u002Ftaws","huseyinbabal","Terminal UI for AWS (taws) - A terminal-based AWS resource viewer and manager","",null,"Rust",2231,67,9,12,0,4,27.5,"MIT License",false,"master",[],"2026-06-12 02:03:26","\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Ftaws-logo.png\" alt=\"taws\" width=\"400\"\u002F>\n\u003C\u002Fp>\n\n# taws - Terminal UI for AWS\n\n**taws** provides a terminal UI to interact with your AWS resources. The aim of this project is to make it easier to navigate, observe, and manage your AWS infrastructure in the wild.\n\n---\n\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FLicense-MIT-blue.svg)](LICENSE)\n[![Rust](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Frust-1.70%2B-orange.svg)](https:\u002F\u002Fwww.rust-lang.org\u002F)\n\n---\n\n## Screenshots\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fscreenshot-ec2.png\" alt=\"EC2 Instances View\" width=\"800\"\u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"assets\u002Fscreenshot-lambda.png\" alt=\"Lambda Functions View\" width=\"800\"\u002F>\n\u003C\u002Fp>\n\n---\n\n## Features\n\n- **Multi-Profile Support** - Easily switch between AWS profiles\n- **Multi-Region Support** - Navigate across different AWS regions\n- **94+ Resource Types** - Browse and manage resources across 60+ AWS services\n- **Manual Refresh** - Refresh resources with a single keystroke\n- **Pagination** - Navigate through large resource lists with `]` \u002F `[` keys\n- **Keyboard-Driven** - Vim-like navigation and commands\n- **Resource Actions** - Start, stop, terminate EC2 instances directly\n- **Detailed Views** - JSON\u002FYAML view of resource details\n- **Filtering** - Filter resources locally with fuzzy matching, or by AWS tags (server-side) for supported resources\n- **Autocomplete** - Smart resource type autocomplete with fuzzy matching\n\n---\n\n## Installation\n\n### Homebrew (macOS\u002FLinux)\n\n```bash\nbrew install huseyinbabal\u002Ftap\u002Ftaws\n```\n\n### Scoop (Windows)\n\n```powershell\nscoop bucket add huseyinbabal https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Fscoop-bucket\nscoop install taws\n```\n\n### Download Pre-built Binaries\n\nDownload the latest release from the [Releases page](https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest).\n\n| Platform | Architecture | Download |\n|----------|--------------|----------|\n| **macOS** | Apple Silicon (M1\u002FM2\u002FM3) | `taws-aarch64-apple-darwin.tar.gz` |\n| **macOS** | Intel | `taws-x86_64-apple-darwin.tar.gz` |\n| **Linux** | x86_64 (musl) | `taws-x86_64-unknown-linux-musl.tar.gz` |\n| **Linux** | ARM64 (musl) | `taws-aarch64-unknown-linux-musl.tar.gz` |\n| **Windows** | x86_64 | `taws-x86_64-pc-windows-msvc.zip` |\n\n#### Quick Install (macOS\u002FLinux)\n\n```bash\n# macOS Apple Silicon\ncurl -sL https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest\u002Fdownload\u002Ftaws-aarch64-apple-darwin.tar.gz | tar xz\nsudo mv taws \u002Fusr\u002Flocal\u002Fbin\u002F\n\n# macOS Intel\ncurl -sL https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest\u002Fdownload\u002Ftaws-x86_64-apple-darwin.tar.gz | tar xz\nsudo mv taws \u002Fusr\u002Flocal\u002Fbin\u002F\n\n# Linux x86_64 (musl - works on Alpine, Void, etc.)\ncurl -sL https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest\u002Fdownload\u002Ftaws-x86_64-unknown-linux-musl.tar.gz | tar xz\nsudo mv taws \u002Fusr\u002Flocal\u002Fbin\u002F\n\n# Linux ARM64 (musl - works on Alpine, Void, etc.)\ncurl -sL https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest\u002Fdownload\u002Ftaws-aarch64-unknown-linux-musl.tar.gz | tar xz\nsudo mv taws \u002Fusr\u002Flocal\u002Fbin\u002F\n```\n\n#### Windows\n\n1. Download `taws-x86_64-pc-windows-msvc.zip` from the [Releases page](https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Freleases\u002Flatest)\n2. Extract the zip file\n3. Add the extracted folder to your PATH, or move `taws.exe` to a directory in your PATH\n\n### Using Cargo\n\n```bash\ncargo install taws\n```\n\n### Using Docker\n\n```bash\n# Run interactively\ndocker run --rm -it ghcr.io\u002Fhuseyinbabal\u002Ftaws\n\n# Launch with a specific profile (mount AWS credentials)\ndocker run --rm -it \\\n  -v ~\u002F.aws:\u002Froot\u002F.aws:ro \\\n  ghcr.io\u002Fhuseyinbabal\u002Ftaws --profile production\n\n# Launch in a specific region\ndocker run --rm -it \\\n  -v ~\u002F.aws:\u002Froot\u002F.aws:ro \\\n  ghcr.io\u002Fhuseyinbabal\u002Ftaws --region us-west-2\n\n# Using environment variables\ndocker run --rm -it \\\n  -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \\\n  -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \\\n  -e AWS_REGION=us-east-1 \\\n  ghcr.io\u002Fhuseyinbabal\u002Ftaws\n\n# Build locally\ndocker build -t taws .\ndocker run --rm -it -v ~\u002F.aws:\u002Froot\u002F.aws:ro taws\n```\n\n> **Note:** Use `-it` flags for interactive terminal support (required for TUI). Mount your `~\u002F.aws` directory as read-only to use your existing AWS credentials.\n\n### From Source\n\ntaws is built with Rust. Make sure you have Rust 1.70+ installed, along with a C compiler and linker.\n\n#### Build Dependencies\n\n| Platform | Install Command |\n|----------|-----------------|\n| **Amazon Linux \u002F RHEL \u002F Fedora** | `sudo yum groupinstall \"Development Tools\" -y` |\n| **Ubuntu \u002F Debian** | `sudo apt update && sudo apt install build-essential -y` |\n| **macOS** | `xcode-select --install` |\n| **Windows** | Install [Visual Studio Build Tools](https:\u002F\u002Fvisualstudio.microsoft.com\u002Fvisual-cpp-build-tools\u002F) |\n\n```bash\n# Clone the repository\ngit clone https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws.git\ncd taws\n\n# Build and run\ncargo build --release\n.\u002Ftarget\u002Frelease\u002Ftaws\n```\n\n---\n\n## Prerequisites\n\n- **AWS Credentials** - See [Authentication](#authentication) section below\n- **IAM Permissions** - Your AWS user\u002Frole needs appropriate read permissions for the services you want to browse. At minimum, you'll need `Describe*` and `List*` permissions.\n\n---\n\n## Authentication\n\ntaws uses a credential chain, trying each source in order:\n\n| Priority | Source | Description |\n|----------|--------|-------------|\n| 1 | Environment Variables | `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN` |\n| 2 | **AWS SSO** | If profile has SSO configured, uses SSO (prompts for login if needed) |\n| 3 | **AWS Console Login** | If profile has `login_session` configured, prompts for console login |\n| 4 | **Role Assumption** | If profile has `role_arn` + `source_profile`, assumes the role |\n| 5 | Credentials File | `~\u002F.aws\u002Fcredentials` |\n| 6 | Config File | `~\u002F.aws\u002Fconfig` |\n| 7 | IMDSv2 | EC2 instance metadata |\n\n### AWS SSO\n\ntaws supports AWS SSO. If your profile uses SSO and the token is expired, taws will prompt you to authenticate via browser.\n\nBoth SSO config formats are supported:\n- Modern: `sso_session` reference to `[sso-session X]` section\n- Legacy: `sso_start_url` directly in profile\n\nIf you already logged in via `aws sso login`, taws will use the cached token automatically.\n\n### AWS Console Login\n\ntaws supports AWS Console Login (`aws login`). If your profile uses `login_session` and credentials are expired, taws will prompt you to run `aws login` in another terminal.\n\n```ini\n[profile console-profile]\nlogin_session = my-login-session\n\n[login-session my-login-session]\nsso_start_url = https:\u002F\u002Fmy-portal.awsapps.com\u002Fstart\nsso_region = us-east-1\nsso_registration_scopes = sso:account:access\n```\n\nIf you already logged in via `aws login`, taws will use the cached credentials automatically.\n\n### IAM Role Assumption\n\ntaws supports assuming IAM roles using `role_arn` with either `source_profile` or `credential_source`. This is commonly used for:\n- Cross-account access (e.g., dev account assuming role in prod account)\n- Least-privilege access patterns\n- Chained role assumption\n- Container-based deployments (ECS, Lambda)\n\n#### Using source_profile\n\nReference another named profile for source credentials:\n\n```ini\n[profile base]\nregion = us-east-1\n\n[profile production]\nrole_arn = arn:aws:iam::123456789012:role\u002FProductionAccess\nsource_profile = base\nregion = us-west-2\n\n# Optional: external_id for cross-account trust\n[profile partner-account]\nrole_arn = arn:aws:iam::987654321098:role\u002FPartnerAccess\nsource_profile = base\nexternal_id = my-external-id\n```\n\n#### Using credential_source\n\nLoad source credentials from environment, EC2 metadata, or ECS container:\n\n```ini\n# For ECS tasks with task IAM roles\n[profile ecs-admin]\nrole_arn = arn:aws:iam::123456789012:role\u002FAdminRole\ncredential_source = EcsContainer\n\n# For EC2 instances with instance roles\n[profile ec2-admin]\nrole_arn = arn:aws:iam::123456789012:role\u002FAdminRole\ncredential_source = Ec2InstanceMetadata\n\n# For environments with AWS_ACCESS_KEY_ID\u002FAWS_SECRET_ACCESS_KEY set\n[profile env-admin]\nrole_arn = arn:aws:iam::123456789012:role\u002FAdminRole\ncredential_source = Environment\n```\n\n**Supported credential_source values:**\n\n| Value | Description |\n|-------|-------------|\n| `Environment` | Load from `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN` |\n| `Ec2InstanceMetadata` | Load from EC2 instance metadata (IMDSv2) |\n| `EcsContainer` | Load from ECS container credentials endpoint |\n\n**Supported options:**\n\n| Option | Required | Description |\n|--------|----------|-------------|\n| `role_arn` | Yes | ARN of the IAM role to assume |\n| `source_profile` | One of | Profile to use for source credentials |\n| `credential_source` | these | Where to load source credentials from |\n| `external_id` | No | External ID for cross-account trust policies |\n| `role_session_name` | No | Custom session name (default: `taws-session`) |\n| `duration_seconds` | No | Session duration in seconds (default: 3600) |\n| `region` | No | Region for STS endpoint |\n\n**Notes:**\n- Use exactly one of `source_profile` OR `credential_source` (not both)\n- Chained role assumption is supported (source_profile can also use role_arn)\n- Temporary credentials are cached and automatically refreshed before expiration\n- ECS container credentials require `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` or `AWS_CONTAINER_CREDENTIALS_FULL_URI` environment variables (set automatically by ECS)\n\n---\n\n## Quick Start\n\n```bash\n# Launch taws with default profile\ntaws\n\n# Launch with a specific profile\ntaws --profile production\n\n# Launch in a specific region\ntaws --region us-west-2\n\n# Enable debug logging\ntaws --log-level debug\n\n# Run in read-only mode (blocks all write operations)\ntaws --readonly\n\n# Use with LocalStack or custom endpoint\ntaws --endpoint-url http:\u002F\u002Flocalhost:4566\n\n# Or via environment variable\nAWS_ENDPOINT_URL=http:\u002F\u002Flocalhost:4566 taws\n```\n\n### Log File Locations\n\n| Platform | Path |\n|----------|------|\n| **Linux** | `~\u002F.config\u002Ftaws\u002Ftaws.log` |\n| **macOS** | `~\u002FLibrary\u002FApplication Support\u002Ftaws\u002Ftaws.log` |\n| **Windows** | `%APPDATA%\\taws\\taws.log` |\n\n### Shell Completion\n\ntaws supports shell completion for bash, zsh, fish, and PowerShell.\n\n```bash\n# Bash (add to ~\u002F.bashrc)\neval \"$(taws completion bash)\"\n\n# Zsh (add to ~\u002F.zshrc)\neval \"$(taws completion zsh)\"\n\n# Fish (add to ~\u002F.config\u002Ffish\u002Fconfig.fish)\ntaws completion fish | source\n\n# PowerShell (add to $PROFILE)\ntaws completion powershell | Out-String | Invoke-Expression\n```\n\nAfter adding the completion script, restart your shell or source the config file.\n\n---\n\n## Key Bindings\n\n| Action | Key | Description |\n|--------|-----|-------------|\n| **Navigation** | | |\n| Move up | `k` \u002F `↑` | Move selection up |\n| Move down | `j` \u002F `↓` | Move selection down |\n| Top | `gg` \u002F `Home` | Jump to first item |\n| Bottom | `G` \u002F `End` | Jump to last item |\n| Page up | `PgUp` \u002F `Ctrl+b` | Scroll up one page |\n| Page down | `PgDn` \u002F `Ctrl+f` | Scroll down one page |\n| **Pagination** | | |\n| Next page | `]` | Load next page of results |\n| Previous page | `[` | Load previous page of results |\n| **Views** | | |\n| Resource picker | `:` | Open resource type selector |\n| Describe | `Enter` \u002F `d` | View resource details |\n| Back | `Esc` \u002F `Backspace` | Go back to previous view |\n| Help | `?` | Show help screen |\n| **Actions** | | |\n| Refresh | `R` | Refresh current view (resets pagination) |\n| Filter | `\u002F` | Filter resources |\n| Region shortcuts | `0-5` | Quick switch to common regions |\n| Quit | `Ctrl-c` | Exit taws |\n| **EC2 Actions** | | |\n| Connect (SSM) | `c` | Open SSM shell session to instance |\n| Start instance | `s` | Start selected EC2 instance |\n| Stop instance | `S` | Stop selected EC2 instance |\n| Terminate | `Ctrl+d` | Terminate selected EC2 instance |\n\n---\n\n## Filtering\n\nPress `\u002F` to enter filter mode. taws supports two types of filtering:\n\n### Local Filtering (All Resources)\n\nType any text to filter resources locally by name, ID, or other visible attributes. Uses fuzzy matching.\n\n```\n\u002Fweb-server     # Filter by name containing \"web-server\"\n\u002Fi-0123         # Filter by instance ID\n```\n\n### AWS API Filtering (Server-Side)\n\nFor supported resources, you can filter using AWS API filters directly. This is more efficient for large resource lists as filtering happens server-side.\n\n**How to use:**\n1. Press `\u002F` to enter filter mode\n2. Type `F` and press `Tab` to autocomplete `Filters: `\n3. Enter filter key-value pairs: `Filters: owner=amazon, architecture=arm64`\n4. Press `Enter` to apply the filter (triggers AWS API call)\n5. Press `Esc` to clear the filter\n\n**Syntax:**\n```\nFilters: key=value, key2=value2\n```\n\n**Examples by Resource:**\n\n| Resource | Example Filters |\n|----------|----------------|\n| AMIs | `Filters: owner=amazon, architecture=arm64, state=available` |\n| EC2 Instances | `Filters: instance-state-name=running, tag:Environment=prod` |\n| EBS Volumes | `Filters: status=available, tag:Name=my-volume` |\n| EBS Snapshots | `Filters: status=completed, owner-id=self` |\n\n**Common Filter Keys:**\n\n| Filter Key | Description | Example Values |\n|------------|-------------|----------------|\n| `owner` | AMI owner (AMIs only) | `amazon`, `self`, `aws-marketplace`, `\u003Caccount-id>` |\n| `architecture` | CPU architecture | `arm64`, `x86_64` |\n| `state` \u002F `status` | Resource state | `available`, `running`, `stopped` |\n| `tag:\u003Ckey>` | Filter by tag | `tag:Environment=production` |\n\n> **Note:** When you enter filter mode on a supported resource, taws shows available filter keys for that resource in the status bar.\n\n---\n\n## Resource Navigation\n\nPress `:` to open the resource picker. Type to filter resources:\n\n```\n:ec2          # EC2 Instances\n:volumes      # EBS Volumes\n:snapshots    # EBS Snapshots\n:amis         # AMIs (Amazon Machine Images)\n:lambda       # Lambda Functions\n:s3           # S3 Buckets\n:rds          # RDS Instances\n:iam-users    # IAM Users\n:eks          # EKS Clusters\n```\n\nUse `Tab` to autocomplete and `Enter` to select.\n\n---\n\n## Supported AWS Services\n\ntaws supports **30 AWS services** with **51 resource types** covering 95%+ of typical AWS usage:\n\n| Category | Service | Resources |\n|----------|---------|-----------|\n| **Compute** | EC2 | Instances, Volumes, Snapshots, AMIs |\n| | Lambda | Functions |\n| | ECS | Clusters, Services, Tasks |\n| | EKS | Clusters |\n| | Auto Scaling | Auto Scaling Groups |\n| **Storage** | S3 | Buckets |\n| **Database** | RDS | Instances, Snapshots |\n| | DynamoDB | Tables |\n| | ElastiCache | Clusters |\n| **Networking** | VPC | VPCs, Subnets, Security Groups |\n| | ELBv2 | Load Balancers, Listeners, Rules, Target Groups, Targets |\n| | Route 53 | Hosted Zones |\n| | CloudFront | Distributions |\n| | API Gateway | REST APIs |\n| **Security** | IAM | Users, Groups, Roles, Policies, Access Keys |\n| | Secrets Manager | Secrets |\n| | KMS | Keys |\n| | ACM | Certificates |\n| | Cognito | User Pools |\n| **Management** | CloudFormation | Stacks |\n| | CloudWatch | Log Groups |\n| | CloudTrail | Trails |\n| | SSM | Parameters |\n| | STS | Caller Identity |\n| **Messaging** | SQS | Queues |\n| | SNS | Topics |\n| | EventBridge | Event Buses, Rules |\n| **Containers** | ECR | Repositories |\n| **DevOps** | CodePipeline | Pipelines |\n| | CodeBuild | Projects |\n| **Analytics** | Athena | Workgroups |\n\n> **Missing a service?** [Start a discussion](https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Fdiscussions\u002Fnew?category=ideas) to propose adding it!\n\n---\n\n## Configuration\n\nSee [Authentication](#authentication) for credential setup.\n\n### Environment Variables\n\n| Variable | Description |\n|----------|-------------|\n| `AWS_PROFILE` | Default AWS profile to use |\n| `AWS_REGION` | Default AWS region |\n| `AWS_DEFAULT_REGION` | Fallback region (if `AWS_REGION` not set) |\n| `AWS_ACCESS_KEY_ID` | AWS access key |\n| `AWS_SECRET_ACCESS_KEY` | AWS secret key |\n| `AWS_SESSION_TOKEN` | AWS session token (for temporary credentials) |\n| `AWS_SHARED_CREDENTIALS_FILE` | Custom path to credentials file (default: `~\u002F.aws\u002Fcredentials`) |\n| `AWS_CONFIG_FILE` | Custom path to config file (default: `~\u002F.aws\u002Fconfig`) |\n| `AWS_ENDPOINT_URL` | Custom endpoint URL (for LocalStack, etc.) - also used for STS AssumeRole |\n| `AWS_CA_BUNDLE` | Custom CA certificate bundle (PEM format) for corporate SSL inspection |\n| `SSL_CERT_FILE` | Alternative to `AWS_CA_BUNDLE` for custom CA certificates |\n\n### Corporate Proxy \u002F SSL Inspection\n\nIf you're behind a corporate proxy with SSL inspection, taws may fail to connect to AWS services because the proxy's CA certificate is not trusted by default.\n\nTo fix this, set `AWS_CA_BUNDLE` or `SSL_CERT_FILE` to point to your corporate CA certificate bundle:\n\n```bash\n# Windows\nset AWS_CA_BUNDLE=C:\\path\\to\\corporate-ca-bundle.pem\ntaws\n\n# Linux\u002FmacOS\nexport AWS_CA_BUNDLE=\u002Fpath\u002Fto\u002Fcorporate-ca-bundle.pem\ntaws\n```\n\nThe PEM file can contain multiple certificates (certificate chain). taws will load all certificates from the bundle and add them to the trusted root certificates.\n\n**Note:** This is the same environment variable used by AWS CLI, so if AWS CLI works with your CA bundle, taws should work too.\n\n---\n\n## SSM Connect (EC2 Shell Access)\n\nPress `c` on a running EC2 instance to open an interactive shell session via AWS Systems Manager.\n\n**Requirements:**\n- [session-manager-plugin](https:\u002F\u002Fdocs.aws.amazon.com\u002Fsystems-manager\u002Flatest\u002Fuserguide\u002Fsession-manager-working-with-install-plugin.html) must be installed\n- EC2 instance must have SSM Agent running\n- Instance must be running (not stopped\u002Fterminated)\n- Linux instances only (Windows not supported via shell)\n\n**Note:** When you exit the shell session (`exit`), you'll return to taws.\n\n---\n\n## Known Issues\n\n- Some resources may require specific IAM permissions not covered by basic read-only policies\n- Total resource count is not displayed due to AWS API limitations (most AWS APIs don't return total count)\n- Some global services (IAM, Route53, CloudFront) always use us-east-1\n\n---\n\n## Contributing\n\nContributions are welcome! Please see our [Contributing Guide](CONTRIBUTING.md) for details.\n\n**Important:** Before adding a new AWS service, please [start a discussion](https:\u002F\u002Fgithub.com\u002Fhuseyinbabal\u002Ftaws\u002Fdiscussions\u002Fnew?category=ideas) first.\n\n---\n\n## Acknowledgments\n\n- Inspired by [k9s](https:\u002F\u002Fgithub.com\u002Fderailed\u002Fk9s) - the awesome Kubernetes CLI\n- Built with [Ratatui](https:\u002F\u002Fgithub.com\u002Fratatui-org\u002Fratatui) - Rust TUI library\n- Uses [aws-sigv4](https:\u002F\u002Fgithub.com\u002Fawslabs\u002Faws-sdk-rust) for request signing\n\n---\n\n## License\n\nThis project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.\n\n---\n\n\u003Cp align=\"center\">\n  Made with ❤️ for the AWS community\n\u003C\u002Fp>\n","taws 是一个基于终端的 AWS 资源查看和管理工具。它通过提供一个多配置文件、多区域支持的界面，让用户能够轻松浏览和操作超过 94 种 AWS 资源类型，涵盖 60 多个 AWS 服务。taws 的技术特点包括手动刷新、分页导航、键盘驱动操作（类似 Vim）、资源直接操作（如启动或停止 EC2 实例）、详细视图展示（JSON\u002FYAML 格式）、本地模糊匹配过滤以及智能自动补全等。该工具非常适合需要频繁与 AWS 交互的开发者或运维人员，在日常管理和监控 AWS 基础设施时使用。",2,"2026-06-11 03:50:20","high_star"]