home / skills / partme-ai / full-stack-skills / cloud-aliyun-oss

cloud-aliyun-oss skill

This skill provides guidance for Alibaba Cloud OSS, including bucket creation, access control, and object storage management.

npx playbooks add skill partme-ai/full-stack-skills --skill cloud-aliyun-oss

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

687 B

---
name: cloud-aliyun-oss
description: Provides comprehensive guidance for Alibaba Cloud OSS including bucket creation, object storage, access control, and OSS management. Use when the user asks about Alibaba Cloud OSS, needs to store files in OSS, configure OSS buckets, or work with Alibaba Cloud storage.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- [待完善：根据具体工具添加使用场景]

## How to use this skill

[待完善：根据具体工具添加使用指南]

## Best Practices

[待完善：根据具体工具添加最佳实践]

## Keywords

[待完善：根据具体工具添加关键词]

Overview

This skill provides practical, end-to-end guidance for working with Alibaba Cloud Object Storage Service (OSS). It covers creating and configuring buckets, uploading and managing objects, setting access control policies, and operational tasks like lifecycle rules and monitoring. Use it to get actionable steps, code snippets, and configuration recommendations for real-world OSS workflows.

How this skill works

The skill inspects user intent about OSS tasks and returns targeted instructions, sample commands, and code examples (Python and CLI) for bucket and object operations. It explains access control models (ACLs, RAM policies, signed URLs), storage classes, and lifecycle management. It also highlights common pitfalls and recovery options for permissions and data availability.

When to use it

Creating or configuring OSS buckets for new projects
Uploading, downloading, or synchronizing files to OSS from applications
Setting up access control, signed URLs, or cross-account access
Configuring lifecycle rules, versioning, or storage classes to optimize costs
Troubleshooting permission errors, CORS, or object retrieval issues

Best practices

Use least-privilege RAM policies for applications and avoid sharing root credentials
Enable bucket versioning and lifecycle rules to protect and manage storage costs
Choose the appropriate storage class (Standard, Infrequent Access, Archive) based on access patterns
Apply CORS and object metadata correctly for browser uploads and downloads
Use signed URLs for temporary, secure access instead of making buckets public

Example use cases

Web app storing user uploads to an OSS bucket with signed URLs for secure downloads
Automated nightly backup of database dumps to an Infrequent Access bucket with lifecycle transition to Archive
Static website hosting on OSS with proper CORS and cache-control headers
Cross-account data sharing using RAM roles and bucket policies for analytics pipelines
CI/CD pipeline uploading build artifacts to OSS and cleaning old artifacts via lifecycle rules

FAQ

How do I grant an application permission to upload to a bucket?

Create a RAM role or user with a policy granting PutObject and ListBucket for the specific bucket, then use temporary credentials or access keys in the application. Prefer temporary credentials (STS) for enhanced security.

When should I use signed URLs instead of making a bucket public?

Use signed URLs when you need time-limited, controlled access to objects. Public buckets suit truly public content; signed URLs prevent unauthorized persistent access and are better for private or paid content.