opensite-ai/opensite-skills / aws-sdk-python-usage
aws-sdk-python-usage
UnverifiedAWS SDK for Python (boto3/botocore) development patterns. You MUST use this skill when writing Python code that uses AWS services via boto3 or botocore. This includes creating service clients or resources, configuring sessions and credentials, handling errors with ClientError, using paginators and waiters, S3 file transfers and presigned URLs, DynamoDB table operations, and any boto3/botocore client configuration. Use this skill whenever Python code imports boto3 or botocore, or when the user asks about AWS operations in Python.
| File | Kind | Size |
|---|---|---|
| .aws-skill-metadata | other | 18 B |
| SKILL.md | skill md | 8.0 KB |
| references/configuration.md | markdown | 3.7 KB |
| references/credentials.md | markdown | 3.7 KB |
| references/dynamodb.md | markdown | 8.4 KB |
| references/error-handling.md | markdown | 4.5 KB |
| references/pagination.md | markdown | 3.0 KB |
| references/s3.md | markdown | 5.1 KB |
| references/waiters.md | markdown | 3.3 KB |
references/error-handling.md
View on GitHub# Error Handling Reference
## Core Principle
Only catch an exception when you have an actionable response: return a fallback, retry, take a different code path. If the only thing you'd do is print the error, don't catch it -- let it propagate. The caller (or a top-level handler) is in a better position to decide what to do.
## ClientError Anatomy
`botocore.exceptions.ClientError` is the base exception for all AWS API errors:
```python
from botocore.exceptions import ClientError
try:
client.describe_instances(InstanceIds=["i-nonexistent"])
except ClientError as e:
error = e.response["Error"]
metadata = e.response["ResponseMetadata"]
error["Code"] # "InvalidInstanceID.NotFound"
error["Message"] # "The instance ID 'i-nonexistent' does not exist"
metadata["HTTPStatusCode"] # 400
metadata["RequestId"] # AWS request ID for support cases
```
## Service-Specific Exceptions
Each client exposes typed exceptions generated from the service model. These are subclasses of `ClientError`, so a `ClientError` catch still works as a fallback:
```python
s3 = boto3.client("s3")
try:
s3.get_object(Bucket="bucket", Key="key")
except s3.exceptions.NoSuchKey:
return None # actionable: missing key is a valid case
```
List available exceptions for a client:
```python
print([e for e in dir(s3.exceptions) if not e.startswith("_")])
```
## Common botocore Exceptions
```python
from botocore.exceptions import (
ClientError, # AWS API returned an error response
NoCredentialsError, # no credentials found in the chain
PartialCredentialsError, # incomplete credentials (e.g. key without secret)
NoRegionError, # no region configured
ParamValidationError, # invalid parameters before request is sent
EndpointConnectionError, # could not connect to the endpoint
ConnectTimeoutError, # connection timed out
ReadTimeoutError, # read timed out waiting for response
WaiterError, # waiter reached max attempts without success
)
```
`ParamValidationError` is raised locally before any network request -- it means the parameters failed botocore's client-side validation.
## Error Handling Patterns
### Actionable catch: convert to return value
```python
def get_item(table, key: dict) -> dict | None:
response = table.get_item(Key=key)
return response.get("Item") # None if missing, no exception needed
def head_object(client, bucket: str, key: str) -> dict | None:
try:
return client.head_object(Bucket=bucket, Key=key)
except client.exceptions.ClientError as e:
if e.response["ResponseMetadata"]["HTTPStatusCode"] == 404:
return None
raise
```
### Actionable catch: conditional put race
```python
try:
table.put_item(
Item=new_item,
ConditionExpression=Attr("pk").not_exists(),
)
except table.meta.client.exceptions.ConditionalCheckFailedException:
# Another writer got there first -- fetch what they wrote
return table.get_item(Key={"pk": new_item["pk"]})["Item"]
```
### Actionable catch: create-if-not-exists
```python
try:
client.create_bucket(Bucket="my-bucket")
except client.exceptions.BucketAlreadyOwnedByYou:
pass # already exists, that's fine
```
### Top-level catch-all in main()
Business logic functions should let exceptions propagate. The `main()` function is the right place for a generic catch-all that presents errors cleanly to the user. Keep the catch-all simple -- just `ClientError`. Other exceptions like `NoCredentialsError` already have clear messages and can propagate naturally:
```python
from botocore.exceptions import ClientError
def main() -> int:
try:
do_the_work()
return 0
except ClientError as e:
print(f"Error: {e}", file=sys.stderr)
return 1
if __name__ == "__main__":
sys.exit(main())
```
### What NOT to do
```python
# Wrong: catching just to print and swallow
try:
client.describe_table(TableName=name)
except client.exceptions.ResourceNotFoundException:
print("Table not found") # swallowed -- caller has no idea it failed
except NoCredentialsError:
print("No credentials") # swallowed
except EndpointConnectionError:
print("Can't connect") # swallowed
# Wrong: sys.exit() from a business logic function
def process_queue(queue_url):
if not queue_url:
print("No queue URL provided")
sys.exit(1) # untestable, unusable as library code
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |