mismatching account ids in lambda update through bitbucket pipelines

[andrew.ritter]

Hi,

I have my own IAM user which Ive used to access my bosses AWS for creating API Gateways and Lambdas.  I set up a bitbucket pipeline to update the lambda everytime I update the bitbucket repo.
I entered my IAM user's access key, secret access key and region into pipeline variables.

When the pipeline attempts to update the Lambda I get an error like

```
An error occurred (ResourceNotFoundException) when calling the UpdateFunctionCode operation: Function not found: arn:aws:lambda:us-east-2:{iamuseraccountidnumber}:function:my-lambda

✖ Failed to update Lambda function code.
```

Where {iamuseraccountidnumber} is the account number in my IAM user's arn.
It doesnt not find the lambda because I created it in my bosses account so the account id in the arn it attempts to connect to is not the same.

What do I need to update to change which account id is filled in in the generated arn?

[andrew.ritter · Accepted solution]

It was as simple as using the access key/secret access for my IAM user in the host account