aws-cloud-services_skill

This skill helps you design, deploy, and manage AWS cloud infrastructure using S3, Lambda, DynamoDB, IAM, CloudFormation, and best practices.
  • Shell

40

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill manutej/luxor-claude-marketplace --skill aws-cloud-services

  • .summary.txt3.4 KB
  • EXAMPLES.md44.4 KB
  • README.md15.9 KB
  • SKILL.md40.3 KB

Overview

This skill provides a comprehensive, practical guide and tooling patterns for building, deploying, and operating applications on Amazon Web Services. It covers core services—S3, Lambda, DynamoDB, EC2, RDS, IAM, and CloudFormation—plus secure credential handling, SDK best practices, and enterprise architecture patterns. You get concrete operations, code patterns, and deployment approaches that speed up development and reduce operational risk.

How this skill works

The skill explains what to configure and how to interact with AWS services using the AWS SDK (JavaScript v3) and CLI patterns. It includes common code snippets for uploads, downloads, presigned URLs, multipart uploads, Lambda handlers, IAM policy examples, credential resolution, and region/endpoint configuration. It highlights operational workflows like infrastructure-as-code via CloudFormation, least-privilege IAM design, and multipart/large-file handling for S3.

When to use it

  • Building scalable web or mobile backends on AWS
  • Creating serverless APIs and event-driven pipelines with Lambda
  • Storing, serving, and protecting files at scale with S3
  • Designing NoSQL solutions or single-table patterns with DynamoDB
  • Provisioning and managing compute with EC2 or managed databases with RDS
  • Automating deployments, multi-account architecture, and security controls with CloudFormation and IAM

Best practices

  • Apply least-privilege for IAM: start with no access and add permissions incrementally
  • Never hardcode credentials; prefer IAM roles, environment variables, or Secrets Manager
  • Use SDK v3 modular clients and command pattern for smaller bundles and better typing
  • Use presigned URLs for client uploads/downloads to avoid exposing credentials
  • Use multipart upload for large S3 objects and abort incomplete uploads to avoid charges
  • Define regions and endpoints explicitly for predictable latency and compliance

Example use cases

  • Serverless image processing pipeline: S3 upload -> Lambda thumbnail generator -> DynamoDB metadata store
  • Web app file handling: presigned S3 upload URLs and lifecycle policies to control cost
  • Data pipeline: ingest logs into S3, process with Lambda or AWS Batch, store aggregates in RDS or DynamoDB
  • CI/CD: CloudFormation templates to deploy stacks, roles, and networking across accounts
  • Migration: lift-and-shift portions to EC2 or RDS while re-architecting new features as Lambda microservices

FAQ

Use the shared credentials file (~/.aws/credentials), environment variables, or an SSO/STS flow. Avoid embedding keys in code and rotate keys regularly.

When should I choose Lambda vs EC2?

Choose Lambda for short-lived, event-driven workloads and rapid scaling with minimal ops. Use EC2 for long-running processes, custom OS-level control, or when you need full control over infrastructure.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
aws-cloud-services skill by manutej/luxor-claude-marketplace | VeilStrat