library · inferred from evidence
boto3
The AWS SDK for Python, used to interact with AWS services programmatically.
- Error after running `list_foundation_models`
Teaches how to error after running `list_foundation_models`. Based on a real issue report and its verified fix.
- Announcement: S3 default integrity change
A practical guide for AWS S3. After boto3 1.36.0 turned on default S3 integrity checksums, PutObject calls can fail with XAmzContentSHA256Mismatch: The Content-SHA256 you specified did not match what we received. If this blocks you, pin bac
- PutObject fails with SignatureDoesNotMatch following release of 1.36
Teaches how to putObject fails with SignatureDoesNotMatch following release of 1.36. Based on a real issue report and its verified fix.
- OutputKey in start_transcription_job() cant have `=`
How to outputKey in start_transcription_job() cant have =. Verified in gh:boto/boto3#4312.
- Invalid LocationConstraint error in lab 03_QuestionAnswering/knowledge-bases /0_create_ingest_documents_test_kb.ipynb
[GAcharyaOS (reporter)]: us-east-1 is special: S3 rejects CreateBucketConfiguration with a LocationConstraint there, so delete the CreateBucketConfiguration={ 'LocationConstraint': region_name } argument from the create_bucket call. Every o
- Supabase Storage S3 API: AWS Go SDK v2 uploads fail with 403 SignatureDoesNotMatch
What this covers: Using the AWS SDK for Go v2 (aws-sdk-go-v2) against Supabase Storage's S3-compatible endpoint, PutObject fails with: operation error S3: PutObject, https response error StatusCode: 403, api error SignatureDoesNotMatch: The
- Textract rejects local PDFs: `Exception: PDF must be in S3 bucket`
Textract rejects local PDFs: `Exception: PDF must be in S3 bucket`. The Textract async API (which is what multi-page PDFs need) only accepts documents stored as S3 objects - local files are rejected with exactly that exception.
- UnrecognizedClientException when calling the GetAccount operation (django-ses)
The keys were valid, but the IAM identity behind them was missing the permissions django-ses's throttling/quota checks need. Grant the IAM user or role ses:GetAccount and ses:GetSendQuota in addition to the normal send permissions.
- UnrecognizedClientException when calling the GetAccount operation (django-ses)
On django 4.2.1 with django-ses 3.4.1, calling Django's send_mail raised: An error occurred (InvalidClientTokenId) when calling the GetSendQuota operation: The security token included in the request is invalid. Enabling USE_SES_V2 = True ch