New Supplier: AWS #10
Description
Supplier Name
Amazon Web Services, Inc
Data Processor
Yes
Minimum Term Length
12 months (Dinesh bought Reserved Instances by mistake)
Supplier Site
Internal Contact
Gilfoyle
T&Cs
https://aws.amazon.com/service-terms/
Security Documents URL
https://aws.amazon.com/security/
Vendor/Service Usage Context
We are temporarily using S3 buckets to stage encrypted file shards before they are distributed to the decentralized network (PiperNet).
Use Case 1: Overflow storage when the user devices (phones/fridges) in the mesh network go offline.
Use Case 2: Hosting the "PiperChat" legacy logs (compliance requirement).
Use Case 3: Dinesh needs an EC2 instance to run his "Tesla Battery Optimization" script, which I am 90% sure is just mining crypto.
Constraint: This is a centralized point of failure. If Bezos sneezes, our redundancy drops by 14%. We need to migrate off this as soon as the Anton cluster is fully upgraded.
Data Types Involved
Encrypted binary blobs (Middle-out compressed). We do NOT store the private keys on AWS (that would be suicide).
Server access logs (IP addresses, timestamps).
Dinesh's personal location history (apparently).
How will the supplier be paid?
Invoice
Reviewer
Jared
Documents for Analysis
🤖 Status:
- Spidered 1 seed URLs.
- Processed 6 total documents.
Missing something?
- Drag & Drop a PDF into a comment below.
- Or Paste Text in a comment with the header:
### Manual Document: [Doc Name] - Add the label
refresh-documentsto retry.
🌐 Scraped Documents
- Existing_File:
webpage(Source: https://aws.amazon.com/service-terms/)
🗄️ Existing / Restored Files
- Legal:
issue-10-Amazon_Web_Services,_Inc-eula.txt(Restored) - Legal:
issue-10-Amazon_Web_Services,_Inc-manage-account-payment.html#manage-account-tax-lin.txt(Restored) - Legal:
issue-10-Amazon_Web_Services,_Inc-Nvidia-3P-Notice.txt(Restored) - Legal:
issue-10-Amazon_Web_Services,_Inc-policy.txt(Restored) - Legal:
issue-10-Amazon_Web_Services,_Inc-ZRPLWLL6_p=0.txt(Restored)