'aws' 검색 결과

ClawSweeper로 OpenClaw의 이슈와 PR을 점검합니다. 보고서 확인, 수정 작업 생성, GitHub Actions 조사와 권한 및 검증 조건에 따른 자동 수정·병합을 지원합니다.

• 이슈와 PR 점검 보고서를 확인할 때
• 기존 보고서로 수정 작업을 만들 때
• GitHub Actions 실패를 조사할 때

Deploy and operate AI agents with AWS Bedrock AgentCore. Choose services for hosting agents, connecting external APIs, managing credentials and conversation state, monitoring activity, and assessing agent quality through automated evaluations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan an agent deployment on AgentCore
• Expose a REST API as an agent tool through MCP
• Configure credentials and access controls

Build and deploy AWS Lambda functions without managing servers. Guidance covers APIs, scheduled jobs, event triggers, permissions, shared dependencies, and performance tuning, with code and command examples for deployment and troubleshooting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building lightweight APIs with API Gateway or function URLs
• Running scheduled jobs with EventBridge
• Processing S3 uploads or SQS messages

Assess an AWS resource using CloudWatch logs and metrics, the measurements that describe its behavior. Investigate failures and performance issues, classify their severity, and produce a remediation report with staged actions, CLI commands, and monitoring recommendations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate Lambda errors and throttling
• Examine RDS performance and connection issues
• Check ECS task counts and service health

Set up decoy credentials, storage, and secrets across AWS, Azure, and GCP to detect suspicious access. Connect audit logs to security alerts, verify detection, and document permissions, resource inventories, and maintenance plans.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Detecting use of leaked cloud credentials
• Monitoring suspicious access to decoy storage and secrets
• Extending on-premises deception coverage to cloud environments

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing GitHub repository access requests from Slack
• Preparing AWS IAM permissions for a specific task
• Routing sensitive access requests for additional review

Monitor daily AWS spending by service and account, compare it with historical baselines, and send Slack alerts with cost differences and likely causes. Known planned increases are excluded, and cloud resources remain unchanged.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Detecting unusual increases in daily AWS spending
• Investigating cost spikes by service and account
• Excluding planned or seasonal spending increases

Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrate workloads from Heroku to AWS. Triggers on: migrate from Heroku, Heroku to AWS, move off Heroku, migrate Heroku Postgres to RDS, migrate Heroku Redis to ElastiCache, migrate Heroku Kafka to MSK, migrate dynos to Elastic Beanstalk, migrate dynos to Fargate, migrate Heroku Private Space, Heroku to ECS, leave Heroku, what-if workshop, compare migration scenarios, workshop mode. Runs a 6-phase process: discover Heroku resources live via the authenticated Heroku CLI (read-only, consent-gated) and/or from Terraform, Procfile/app.json, and billing exports, then clarify, design, estimate costs, generate artifacts, and collect feedback. Clarify must finish before Design, Estimate, or Generate. An optional post-Estimate what-if workshop reprices region/HA/compute/Graviton scenarios. Do not use for: GCP migrations (see gcp-to-aws), Azure migrations (see azure-to-aws), AWS-to-Heroku reverse migration, general AWS architecture advice without migration intent, or Heroku-to-Heroku refactoring.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Interactive discovery + implementation workflow that gathers requirements through picker-based questions (intent, scope, constraints, preferences), scans the codebase for what it can already infer, then writes an AWS architectural scaffold and implementation directly into the project. Use when the user wants to build a new app, scaffold a project, or expand/refactor an existing one on AWS — anything that calls for a structured discovery flow followed by code changes, not a one-off lookup. Do not use for: factual lookups about AWS Activate / programs / credits, requests for a single copy-paste prompt, non-AWS architectural work, architecture advice/recommendations without code changes (see architect-for-startups), a new idea centered on an AI agent — runtime selection, agentic architecture, or an agent POC (see agent-advisor), or migrating an existing GCP/Azure/Heroku workload or an LLM SDK rewrite (see gcp-to-aws / azure-to-aws / heroku-to-aws / llm-to-bedrock).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides building full-stack applications with AWS Blocks — an Infrastructure-from-Code framework. Applies when creating APIs, selecting Building Blocks (KVStore, DistributedTable, Database, AuthBasic, AuthCognito, Realtime, AsyncJob, FileBucket, etc.), running local development, or deploying AWS Blocks applications. Also covers AWS Blocks topics with validated, version-specific patterns that prevent common mistakes. Triggers when user mentions AWS Blocks; project has aws-blocks/ directory; code imports @aws-blocks packages.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework. Use when writing or editing sst.config.ts, building infra/ modules (sst.aws.Function/Bucket/Dynamo/Cron/Service/Router, sst.Secret, sst.Linkable, raw aws.* Pulumi resources), wiring resource links, scoping IAM, or running sst deploy/dev/diff/remove. Essential when the user mentions SST, sst.config.ts, $config, $transform, $interpolate, sst.aws.*, sst.Secret, Pulumi/Ion, "sst deploy", a failed SST deploy (ConflictException on a resource-type change, "Identifier '__filename' has already been declared", MalformedPolicyDocument on an Output<T>), or wants to scaffold/troubleshoot AWS infrastructure with SST. Also use when a request to "deploy my AWS stack" or "add a Lambda/bucket/table" is made in a repo that already contains an sst.config.ts (using $config) or an sst dependency. Do NOT use when the task is primarily AWS CDK, Terraform, raw CloudFormation, or SAM with no SST present — those have their own tooling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide HyperFrames video projects from setup through layout checks, editable previews, and video output. Covers command-line workflows, environment troubleshooting, and distributed rendering on AWS Lambda, which splits video rendering work across cloud functions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a HyperFrames video project
• Checking text overflow and scene display
• Exporting a video after reviewing it in Studio

Deploy container applications on AWS using ECS and Fargate, which runs containers without managing servers. Covers image publishing, task configuration, load balancing, automatic scaling, deployment updates, and troubleshooting failed or unhealthy containers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy Docker applications on Fargate
• Configure load balancing and automatic scaling
• Investigate failed tasks and health checks

Identify unused AWS resources, estimate potential savings, and prepare cleanup scripts with preview steps. Covers storage retention policies and scheduled cleanup so teams can review dependencies before removing resources and track the resulting savings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Inventory unused resources and estimate savings
• Prepare cleanup scripts for EBS volumes and Elastic IPs
• Review S3 versions and storage retention rules

Provision and manage Amazon RDS relational databases on AWS. Follow guidance for backups, recovery, security, monitoring, multi-zone redundancy, and read replicas—database copies that handle read traffic—with AWS CLI commands and a Terraform configuration example.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy a managed PostgreSQL or MySQL database
• Configure multi-zone redundancy and read replicas
• Set up backups and restore to a specific point in time

Audit AWS, Azure, and GCP configurations against CIS Benchmarks, security configuration guidelines. Use automated scan results to identify failed checks, prioritize fixes, report compliance by area, and establish ongoing monitoring for configuration changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running an initial cloud security configuration audit
• Preparing CIS-related evidence for SOC 2 or ISO 27001 audits
• Prioritizing fixes for failed security checks

Analyze access logs from AWS S3, GCS, and Azure Blob Storage to spot unusual downloads, unfamiliar IP addresses, and request spikes. Compare activity with normal patterns and prioritize findings for suspected data theft investigations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating suspected data theft from cloud storage
• Finding bulk downloads outside normal working hours
• Checking unfamiliar IP addresses and sudden request spikes

Build AWS applications with managed services that reduce server administration. Follow patterns for Lambda functions, HTTP APIs, database access, and queued background processing, with guidance on deployment and delays when functions first start.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build HTTP APIs with Lambda and API Gateway
• Read and write application data in DynamoDB
• Process SQS messages with retries and a dead-letter queue

Guide server-side Zoom integrations using Zoom Rivet SDK in JavaScript or TypeScript. Consult patterns for authentication, incoming event notifications, typed API calls, multiple modules, and webhook processing on AWS Lambda.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing Zoom authentication and token handling
• Building a Team Chat bot with API integration
• Combining multiple Zoom modules in one server

Deploy QM to Fly.io or AWS, set up administrator access, and configure connectors. The workflow covers model provider and sign-in choices, optional Slack activation, automated live checks, and a manual web acceptance check.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploying QM to Fly.io or AWS
• Setting up initial administrator access
• Configuring connectors and optional Slack access

Deploy the QM package from an organization-owned deployment repository to Fly.io or AWS. Set up an administrator, choose a model provider and sign-in method, configure connectors, and optionally activate Slack, with acceptance checks before handoff.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy QM to Fly.io or AWS
• Set up an initial QM administrator
• Configure a model provider and sign-in method

Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact. Covers CodePipeline V2 (triggers, variables, execution modes, cross-account), buildspec.yml (caching, VPC, Docker), CodeDeploy strategies (blue/green, canary, linear), CodeArtifact (private package registries, auth tokens, cross-account), and source connections (GitHub, GitLab, Bitbucket). Applies when CodePipeline, CodeBuild, CodeDeploy, CodeConnections, CodeArtifact, buildspec.yml, appspec.yml, or CI/CD pipeline orchestration is referenced. Does NOT cover: ECS Fargate services or task definitions (use aws-containers), CDK Pipelines or cdk deploy (use aws-cdk), sam deploy (use aws-serverless), Amplify deployments (use aws-amplify), or GitHub Actions/GitLab CI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Adds user authentication to web and mobile apps with Amazon Cognito (user pools and identity pools) and the AWS Amplify client auth libraries. Covers sign-up/sign-in flows and the login page (Cognito-hosted UI / managed login), MFA, password policies, OAuth 2.0 / OIDC flows (auth-code + PKCE, client credentials), social/SAML federation, tokens (ID/access/refresh, rotation, revocation, storage), Cognito Lambda triggers, identity pools (temp AWS creds), and gating API Gateway (or ALB) routes to signed-in users via Cognito/JWT authorizers. Applies when adding a login or sign-up page, configuring a user pool or app client, choosing user pool vs identity pool, wiring social/SAML, refreshing tokens, requiring sign-in on an API Gateway or ALB, or debugging redirect_uri/token/MFA/CORS/federation errors. Does NOT cover Amplify Gen2 backend definitions (defineAuth, npx ampx → aws-amplify), IAM/STS/Identity Center (→ aws-iam), or API Gateway/Lambda resource config beyond the authorizer (→ aws-serverless).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.