Search across all documentation pages
13 pages in this section.
Why EC2, Lambda, S3, RDS/Aurora, DynamoDB, IAM, VPC, CloudWatch, SNS, and SQS are the ten services almost every SDK project touches first, and how they fit together.
A single guided tour that touches all ten core services - IAM, S3, DynamoDB, RDS, SQS, SNS, Lambda, EC2, VPC, and CloudWatch - with one minimal SDK call each.
Launch, wait for, describe, and terminate an EC2 instance programmatically - a full lifecycle in both boto3 and AWS SDK for JavaScript v3, using waiters instead of polling.
Create, invoke, update, and delete an AWS Lambda function from the SDK - package a zip inline, wait for it to become active, and read its output in both boto3 and SDK v3.
Create a bucket, put and get objects, list a prefix, and clean up - a full S3 lifecycle in both boto3 and AWS SDK v3, including the us-east-1 LocationConstraint gotcha.
Provision an RDS PostgreSQL instance with the SDK, wait for it to become available, read its endpoint, then connect with a normal SQL driver - plus how Aurora differs.
Create a DynamoDB table, then put, get, and query items using the document interface in both boto3 and AWS SDK v3 - plain objects instead of typed attribute values.
Create a scoped, least-privilege policy and a role with a trust policy, attach them via the SDK, verify, and clean up - the identity building blocks in both boto3 and SDK v3.
Create a VPC, a subnet, and a security group with the SDK, add an ingress rule, then tear it all down in the right order - both boto3 and AWS SDK v3, using the ec2 client.
Publish a custom CloudWatch metric, create an alarm that watches it and notifies an SNS topic, then read and delete the alarm - in both boto3 and AWS SDK v3.
Create an SNS topic, subscribe an email and an SQS queue, publish a message that fans out to both, then clean up - in both boto3 and AWS SDK v3.
Create an SQS queue, then send, receive, and delete a message with the SDK - long polling, visibility timeout, and the receive-then-delete contract in boto3 and SDK v3.
A checklist for safely standing up a new project on the ten core AWS services - identity, networking, data, compute, messaging, and observability, from the SDK.