Failed save logs in AWS S3 Bucket (File Storage)

On-Premise
1

Configuration file (config.yml) :

################

#File storage #

################

#Uploaded media uses these filestore settings. The available

#backends are either filesystem or s3.

#filestore.backend: ‘filesystem’

#filestore.options:

#location: ‘/data/files’

#dsym.cache-path: ‘/data/dsym-cache’

#releasefile.cache-path: ‘/data/releasefile-cache’

filestore.backend: ‘s3’

filestore.options:

access_key: ‘AK****’

secret_key: ‘Ui****’

bucket_name: ‘bucket-name’

system.internal-url-prefix: ‘https://my-domain’

symbolicator.enabled: true

symbolicator.options:

url: “http://symbolicator:3021”

transaction-events.force-disable-internal-project: true

Expectation :
Kind of logs file will be saved in my S3 Bucket

Problem :
My S3 Bucket is empty, when app logs is keep streaming in Sentry. I also tested my access & secret key using aws-cli in Sentry Instance by list and putObject, and it worked. There is no problem with access & secret key.

Question :
Why logs is not saved in S3 Bucket? (Still empty)

2

I’m not sure what gave you the impression that logs would go to S3 with this configuration. That’s not what filestore does.

filestore is used for file uploads. So things like uploading sourcemaps, avatars, minidumps, etc.

3

Thanks, Matt! Sorry for misunderstanding for the use of S3 filestore.
Another questions :

  1. So, all logs will be saved in postgres. I’m planning to use Amazon RDS. What should i fill in ENGINE & NAME below configuration? (sentry.conf.py)

DATABASES = {
“default”: {
“ENGINE”: “sentry.db.postgres”,
“NAME”: “postgres”,
“USER”: “postgres”,
“PASSWORD”: “”,
“HOST”: “postgres”,
“PORT”: “”,
}
}

  1. As S3 is used to save file upload, Why i failed when upload avatars? The question is already here :
    Can not change avatar in sentry on premise
4

I don’t know what you’d need to put in there. It’s your RDS credentials.

Logs are also not primarily stored in Postgres. They are also stored in Clickhouse.

I didn’t respond to the other one earlier because there’s no information to go by. I said that now on the other issue.

5

To fill in some gaps, ENGINE can’t change. We only support Postgres. And NAME corresponds to the name of the database.

6

Thanks, Matt!
We already create lots of project, team, and user in current sentry.
Can we get all of that data by exporting current postgres? We can skip the logs.

7

Yeah, that’s all in Postgres.