Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

302
active users

veganism.social: AboutStatusPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.0-alpha.5+vegan

#s3

2 posts2 participants0 posts today
Public
Jonathan Matthews

I'm looking for #data on #CloudStorage providers, in an effort to:
a) sort out where I put my #backups, and
b) not trawl the internet to aggregate this data myself!

I'm looking for basic info (pricing; access protocols; hosting locations; data sovereignty), and also facts about the provider such as public/private ownership, tax residency, and ultimate beneficial ownership.

I'm more than happy to glue disparate datasets together: do you have any pointers? #opendata #storage #s3 #rclone #restic

Public
Jake Coppinger

Thanks to @camwilson, @masek & Crikey for bringing the SMH/AFR subscriber S3 bucket breach into light and getting it fixed.

First announced at infosec.exchange/@bucketchalle

#crikey:
> Last year, Nine bragged about having first-party data including “demographic, content consumption and behavioural information” on 22 million users, and combining that with third party data, to create “rich, detailed, real-time profiles of audience members”.

#s3 #bucket #smh #afr #auspol

crikey.com.au/2025/03/27/sydne

Infosec Exchangebucketchallenge (@bucketchallenge@infosec.exchange)Tonight I found a #s3 #bucket from down under upside down and open. It spills a lot of jucy customer data including names, addresses and email IDs. The responsible disclosure was just sent to the company "owning" the data, but I guess this is the work of some sub contractor. I kindly asked for updates, otherwise I'll escalate that bucket to other agencies to make it go offline.
Public
Helio Loureiro

Plot twist: the issue was... elasticsearch.

Java was crashing when I was setting up the S3.

I raised a single VM on my laptop and it did work to send the snapshot to minio. Something caused a Java crash on cluster nodes.

So I rebooted each node in sequence, waiting for them to join the cluster before starting the reboot in the next one.

And problem solved.

#ElasticSearch
#S3
#Minio

Public *
𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕

Garage - An open-source distributed object storage service

Does any of you know about this and also use it professionally and if so in what context and how? Honestly, I'm standing up a little.

📦 garagehq.deuxfleurs.fr

garagehq.deuxfleurs.frGarage - An open-source distributed object storage serviceAn open-source distributed storage service you can self-host to fullfill many needs.
#garage#rustlang#opensource
Public *
bucketchallenge

Tonight I found a #s3 #bucket from down under upside down and open. It spills a lot of juicy customer data including names, addresses and email IDs.

The responsible disclosure was just sent to the company "owning" the data, but I guess this is the work of some sub contractor. I kindly asked for updates, otherwise I'll escalate that bucket to other agencies to make it go offline.

Public
Tamás

What is the ExpiredToken error with S3 signed URLs and how to avoid it

S3 signed URLs allow implementing file downloads in a serverless environment. In a nutshell, it works by:

* the user wants to download a file
* the backend signs a URL
* the user then uses the URL to download the file directly from S3

A common misconception is that the URL is a simple link to a file. But it's a bit more complicated than that.

A signed URL is "X is doing Y", where:

* X is an identity, usually a Lambda execution role, but can be an IAM user or other roles
* Y is an action, in this case "get this object from this S3 bucket"

The signature has an expiration time and it gives a "Signature expired" error when used after that.

```
https://terraform-....s3.eu-central-1.amazonaws.com/file1?
x-id=GetObject&
X-Amz-Date=20230808T074548Z&
X-Amz-Expires=900&
...
```

But the identity itself can also expire. IAM roles give temporary credentials that can only be used up until they expire.

```json
{
"Credentials": {
"SecretAccessKey": "...",
"SessionToken": "...",
"Expiration": "2016-03-15T00:05:07Z",
"AccessKeyId": "..."
}
}
```

So, what happens when the signature is still valid but the credentials that signed it are expired? That's the `ExpiredToken` error.

How to avoid it?

Make sure that when you sign a URL then the signature expires before the credentials. In the common case of a Lambda signer that means using 15 minutes or less for the expiration.

#aws #s3 #signedurls #expiredtoken

Originally published [on my blog](advancedweb.hu/shorts/what-is-)

advancedweb.huWhat is the ExpiredToken error with S3 signed URLs and how to avoid it
VegansExploreLive feeds
About