To avoid having to type in the endpoint URL every time, you can configure the ~/.aws/credentials
file as follows (docs):
[default]
aws_access_key_id=tid_xxx
aws_secret_access_key=tsec_xxx
endpoint_url=https://fly.storage.tigris.dev
To avoid having to type in the endpoint URL every time, you can configure the ~/.aws/credentials
file as follows (docs):
[default]
aws_access_key_id=tid_xxx
aws_secret_access_key=tsec_xxx
endpoint_url=https://fly.storage.tigris.dev
I still use AWS for certain things like SES, would it make sense to have a secondary fly/tigris specific fallback variables?
The drawback of doing that is then there will be some friction as the s3 SDKs will require some additional configuration to pass the access key and secret. But let me think about it more.
In the meantime you can also do something like this:
[tigris]
aws_access_key_id=tid_xxx
aws_secret_access_key=tsec_xxx
endpoint_url=https://fly.storage.tigris.dev
Then you can use this profile with AWS cli when performing s3 operations:
aws —profile tigris s3api list-buckets
Could you share the name of the bucket with me over email at help@tigrisdata.com
?
I forgot to update here that issues with creating and deleting buckets were resolved some time back. If you run into any further issues let us know.
Hi, I just got access to the beta. Thank you!
One thing I noticed is if I open up the storage dashboard, I see my bucket, but when I click on it I get an “Access denied” error. I’m able to use it fine within my Fly app though. I was expecting I’d be able to browse the contents of the bucket.
Am I doing something wrong?
You are doing nothing wrong. This is a spurious issue on the dashboard. We are working on fixing it.
Hi @justindotpub - we just deployed a fix for this. Can you try again and let us know if you face any issue again.
Yep, it works now. Thank you!
Hey all! I started another thread about a new migration tool Tigris just released. It’s available via the latest flyctl v0.1.147
.