This message was deleted.
# helpdesks
steep-balloon-41261
11/29/2022, 11:41 AMThis message was deleted.
a
acoustic-engineer-41666
11/29/2022, 11:03 PMcc @able-gigabyte-21598
a
able-gigabyte-21598
11/29/2022, 11:05 PMit sounds like access key and/or secret aren’t being read properly. Is it formatted like this?
Copy code
s3:
access_key: '****'
secret: '****'
region: us-east-1
bucket: mybucketg
gentle-fish-74852
11/30/2022, 7:25 AMI have set access_key and secret via the environment variables as detailed in the docs https://docs.livekit.io/oss/deployment/egress/#config
gentle-fish-74852
11/30/2022, 7:26 AMIdeally I'd prefer to leverage AWS IAM to save generating credentials
gentle-fish-74852
11/30/2022, 8:14 AMI notice the codebase expects static credentials. I've updated it locally to auto-configure for my environment, will feed back if this works!
gentle-fish-74852
11/30/2022, 10:13 AMThis worked. Not sure on the impact of changing this in the livekit repo? (I'm maintaining a fork)
d
dry-elephant-14928
11/30/2022, 8:24 PM@able-gigabyte-21598 is it because we are not parsing the env vars correctly?
g
gentle-fish-74852
11/30/2022, 8:34 PMpotentially, but from my experience with the AWS SDK if you're supplying static credentials directly, it won't be able to auto-configure from environment variables?
gentle-fish-74852
11/30/2022, 8:35 PMpossibly environment variable expansion isnt happening in the config?
d
dry-elephant-14928
11/30/2022, 9:05 PMI think we should set those variables if they are non-empty. Perhaps you are using IAM roles, which wouldn't require anything to be set.
g
gentle-fish-74852
11/30/2022, 9:36 PMI am using IAM roles, but I did also statically set generated credentials in the environment variables. Making the code change and generated credentials (leveraging IAM) resolved the issue.
I'd have to experiment further to validate, but it appeared it was not resolving the credentials via environment variables
a
able-gigabyte-21598
11/30/2022, 11:44 PMah, ok. I can add a
UseIAMd
dry-elephant-14928
11/30/2022, 11:45 PMMaybe we should only set these fields if they are non-empty
dry-elephant-14928
11/30/2022, 11:45 PM?
a
able-gigabyte-21598
11/30/2022, 11:45 PMI was considering that too, it should be fine as long as the error messaging is clear
d
dry-elephant-14928
11/30/2022, 11:46 PMi.e. I think having a
Credentialsdry-elephant-14928
11/30/2022, 11:46 PMwhen it's set it prevents AWS from using IAM roles (if available)
a
able-gigabyte-21598
11/30/2022, 11:46 PMright
able-gigabyte-21598
11/30/2022, 11:52 PMwhat should the location in fileInfo return, if the region is taken from the IAM role?
able-gigabyte-21598
11/30/2022, 11:53 PMwe currently return
fmt.Sprintf("<https://%s.s3.>%<http://s.amazonaws.com/%s|s.amazonaws.com/%s>", conf.Bucket, conf.Region, storageFilepath)d
dry-elephant-14928
11/30/2022, 11:53 PMI don't think region is needed. never had to specify that when accessing files in S3
dry-elephant-14928
11/30/2022, 11:54 PM<http://bucket.s3.amazonaws.com/key|bucket.s3.amazonaws.com/key>g
gentle-fish-74852
12/01/2022, 8:06 AMI think setting on non-empty is a good idea, I've taken similar approaches in the past to aid with things like testing