Amazon S3

“I've used it in production to self-host Australia-only maps on S3.”

“I always download precompiled binaries from trusted sources (for example, the team's S3 storage)”

“you're dealing with the real SQS, S3, etc, and if you have integration problems there, they're actually real things you need to fix for it to work in prod”

“substitute Docker containers for RDS and MinIO for S3”

“from the job orchestration with Nomad to the S3 optimizations and the Typst migration”

“an older one built on top of Redis, and a newer one built on PG + S3”

“Push to ECR/S3 by human.”

“For backups, I added a nightly cron job which exports my SQLite db to a write-only S3 bucket.”

“Simply syncing SQLite files across S3 sufficed since the engine itself had a more severe write lock on indexing”

“We use AWS S3 to generate a signed url so only temporary access is enabled.”

“periodically checking S3 for an updated database, it probably is.”

“it's cheaper than 20k a month in S3 bills.”

“For us, we run 2 stacks. One that basically cannot/should-not be deleted/refactored. VPC, RDS, critical S3 buckets”

“s3 and its equivalent of flat files is what we've migrated to as a data store.”

“we have built a simple event system in top of lambda functions, sqs, s3, eventbridge etc”

“Previously we wrote the S3 file system, so it's not like this was our first rodeo.”

“99% of our workload is write heavy and is still on S3.”

“we make our own solution variously on platform agnostic primitives like S3 (or S3 API-compatible options)”

“we use a home-grown version of this [1] to proxy large payloads to S3.”

“When we egress from S3 to our on-prem cluster, that's a cost.”

“we migrated one of our service from S3 to Cloudflare Images”

“Queue upload events via SQS, upload files to s3, scale consumers based on queue length with keda”

“it does require a lot of metadata to orchestrate all the different concurrent operations over S3.”

“I had a few hundred GB of nice special-snowflake json in my S3 bucket.”

“We fail with things like S3 usage, but there are alternatives we could realistically switch to”

“We use partitioning across files (and folder structure in s3) to lazily scan only the bits of data we need”

“For example: we use s3 right now, but we've built the storage server so that it can be extended”

“We migrated from S3 to Minio, an S3-compatible storage. However, we mostly store backups (6-8 TB) there”

“For S3, we've switched to Wasabi which very nicely uses the identical API.”

“We switched to DO Spaces because of the lower bandwidth and storage fees.”

“The jobs fetch the database from S3, update with the latest deltas and write out the database”

“backups in S3 Glacier and rsync.net”

“We use S3 for some static assets, and with layers of caching on top, I think we are rarely affected by outages.”

“I opted for stashing and archiving into GCS / S3 directly”

“a blind S3 GET of one blob, for each database”

“The DB pods push their WALs to S3 and I have script to spawn a new PG from S3 using PITR.”

“We run dynamic image resizing (have a couple million image high quality originals in S3”

“I need to get images from S3, and write them into several formats”

“the long term savings to be significant versus leaving these objects in S3.”

“They wanted a queue, various different sized workers in auto-scaling group with metrics... And probably an s3 bucket.”

“We use Amazon S3 for hosting images, but we have made it easy to switch in case there will be problems”

“deciding how to store business data at rest on s3”

“S3 (Minio), and SES”

“These are the services we used.”

“I started using 'aws s3 sync --delete' nowadays after having issues with pre cleanup required for 'cp'.”

“I can copy it to our documentation aws bucket in continuous integration.”

“s3 buckets used for the Lambda zip files and state”

“We use S3 to store de-identified data and the index to query data we have in S3”

“The main cloud services I use at work are: 1. S3/Azure Blob Store”

“dumps a database, encrypts it and sends it to S3 to be investigated by developers.”

“shipping postgres wal logs to S3 every 10 seconds.”

“weights uploaded to S3. Dockerfile with a tiny little web server gets deployed”

“ZIPs the final code to an S3 bucket.”

“we do a backup of the DNS configuration on Cloudflare and save it on S3”

“Insure that ingestion / S3 jobs were stabilized”

“kinesis takes the log to s3 where it's transformed in batches with lambda then data is moved to Redshift.”

“ancillary services like S3 hosting/bandwidth”

“Most of the time we have to export the logs to S3, download them and do some manual grepping.”

“Backups are stored on a service we run using S3”

“I implemented an abstraction (similar to go-cloud's) between S3 and GCS because of that”

“the standard auxiliary services like CW, SNS, Route53, S3, CF, X-Ray, etc.”

“(+S3+Cloudfront for web page hosting)”

“In real applications we need to use social login, share, google maps, shopify buy SDK, S3, Azure speech API and so on.”

“we use SQS to listen for S3 events and would love to switch to AMQ”

“Yes, we had downtime when S3 died last year. So did half the Internet.”

“name of backup S3 bucket for services in dev environment”

“we harvest these Redis Strings into object storage (both NAS and S3 endpoints) with Postgres storing the metadata”

“From there it is a nightly cron to rsync select directories in own cloud to S3.”

“We were using it for parallel file processing (S3->lambda for CPU-heavy task->return a few numbers in a JSON).”

“When we switched from Amazon S3 to b2, we lost the ability to do signed requests”

“we have 11 or so S3 buckets that back Cloudfront distributions for static content”

“All assets are also uploaded to S3.”

“reducing overall costs for AWS S3 traffic.”

“that fact is dumped onto an S3 bucket, somewhere.”

“Images are hosted on Amazon S3, we also queue uploads to S3 with SQS.”

“we keep the values (files AND environment variables) in S3 and download them at deploy time”

“AWS S3 for static storage + Route 53 for static websites”

“The grunt-aws module makes deploying to S3 and cloudfront a breeze.”

“We've never needed to restore a node from an s3 backup in 5 years of running in production.”

“my service connects to S3 to store/retrieve files. The access key, secret key and even the bucket name are all passed as ENV variables”

“We use an S3-backed private docker registry to store our images/repositories.”

“Guide images are pushed to S3 by Celery”

“set up an S3 bucket as a "local" pip mirror for our EC2 infrastructure”

“raw user events (collected in S3 from web, Lua, Arduino etc clients)”

“encrypt all of my personal files before I back them up to S3/dropbox/whatever”

“I had been using jekyll for a while. Then I decided to piece together how to replicate what the obama campaign did using s3 and cloudfront”

“ended up using node to handle file uploads, validations, image processing, S3 storage and video encoding”

“we just do an S3 base backup of our entire data (which uploads at 65 MB/s from within EC2) fairly infrequently”

“In Rails I use the s3_swf_upload gem to allow folks to upload directly to our S3 buckets.”

“We use S3 to store the raw documents, but CouchDB for the metadata and the results of our algorithms.”

“* File Hosting: S3”

“We log everything to files on local storage. Then we use a command line tool to periodically sync these to S3. Each instance gets its own folder.”

“a Rails app I built to track documents (Stored on S3) associated with machines in production”

“There's a separate management script that pushes the renamed files to S3 - I run that before doing a deploy.”

“we switched everything over to S3. Everything should be much faster now.”

“We push original high resolution versions of photos/graphics to S3.”

“I'm using it with the S3 backend.”

“I've even started using it on two of my own personal servers, storing encrypted backups on Amazon S3.”

“And there is meta data extraction and uploading to S3.”