Hi I am encountering a botocore `NoCredentialsError Unable t

Question

Hi I am encountering a botocore `NoCredentialsError Unable to locate credentials ` error using Docker Storage local image prefect cloud and the `s3ResultHandler` When the flow is run locally There are no credential issues initializing the handler `s3 handler = S3ResultHandler bucket= some bucket ` To resolve the issue I created a Prefect Secret called ` AWS CREDENTIALS ` and tried ```s = Secret AWS CREDENTIALS aws scrts = s get s3 handler = S3ResultHandler bucket= some bucket aws credentials secret=aws scrts ``` What is the best way to resolve aws credential error Thanks

Zachary Hughes · Answer

Hi < itay livni> taking a look now Will get back to you with an answer ASAP

Zachary Hughes · Answer

It looks like you might be giving the `S3ResultHandler` your secret values rather than the name of your Prefect secret Do you still get the `NoCredentialsError` when you provide `aws credentials secret= NAME OF YOUR SECRET HERE ` Here are a couple of links below for reference if that s at all helpful

itay livni · Answer

< Zachary Hughes> Just to be clear the AWS Prefect Secret name has to be all caps ` AWS CREDENTIALS `

Zachary Hughes · Answer

Not necessarily it just needs to be the name of your secret I just used all caps to denote that this was a portion of code that needed to be replaced slightly smiling face

itay livni · Answer

So something else is going on Because this flow was running previously in the same enviroment using different version of prefect

Zachary Hughes · Answer

Hmm do you recall what version of Prefect you were on and what version you re on now

itay livni · Answer

well I am on 0 10 6

itay livni · Answer

and the secret should look like this ``` ACCESS KEY something SECRET ACCESS KEY something ```

Zachary Hughes · Answer

I believe so

itay livni · Answer

Strange I did not need to muck around with this previously

Zachary Hughes · Answer

I can ask around to see if folks know of any changes that could have impacted this It depends on your setup but I m also wondering if boto s picking up changes in your environment config as the S3ResultHandler defaults to standard boto3 auth if you don t provide a secret

Zachary Hughes · Answer

Out of curiosity how were you providing AWS creds previously

itay livni · Answer

I was not It was magically happening behind the scene If not provided `boto3` will fall back on standard AWS rules for authentication

itay livni · Answer

Now That stopped working

itay livni · Answer

```s = Secret aws credentials aws scrts = s get s3 handler = S3ResultHandler bucket= some bucket aws credentials secret=aws scrts ``` And when I build an image using `flow register ` and the code above I get this error ```Beginning health checks System Version check OK Traceback most recent call last File root prefect healthcheck py line 123 in lt module gt flows = cloudpickle deserialization check flow file path File root prefect healthcheck py line 39 in cloudpickle deserialization check flows append cloudpickle load f File MOC etl moc py line 48 in lt module gt aws scrts = s get File usr local lib python3 7 site packages prefect client secrets py line 139 in get from None ValueError Local Secret aws credentials was not found ```

itay livni · Answer

and the secret does exist

Zachary Hughes · Answer

It looks like you re passing in the value of `s get ` rather than the name of your secret Can you try passing in the secret name aws credentials like this `s3 handler = S3ResultHandler bucket= some bucket aws credentials secret= aws credentials `

itay livni · Answer

< Zachary Hughes> For closure 1 Why I suddenly need to use a prefect aws configuration is a mystery 2 Using prefect secret works

itay livni · Answer

Thank you for your patience

Zachary Hughes · Answer

No patience required just glad it s working for you slightly smiling face Haven t been able to isolate any core changes that might have prompted this shift but I ll be sure to keep an eye out