AccessDenied for SQS with Laravel

[mikevang]

I'm attempting to push a job to the SQS queue using laravel, which is working fine locally, but when I deploy to AWS and run it there I get a 403 Forbidden error returned.

"Error executing "SendMessage" on "https://sqs.us-west-2.amazonaws.com/<removed>/My-Creation-Requests"; AWS HTTP error: Client error: `POST https://sqs.us-west-2.amazonaws.com/<removed>/My-Creation-Requests` resulted in a `403 Forbidden` response:
<?xml version="1.0"?>
  <ErrorResponse xmlns="http://queue.amazonaws.com/doc/2012-11-05/">
    <Error>
      <Type>Sender</Type>
      <Code>A (truncated...)\n AccessDenied (client): Access to the resource https://sqs.us-west-2.amazonaws.com/<removed>/My-Creation-Requests is denied. - <?xml version="1.0"?><ErrorResponse xmlns="http://queue.amazonaws.com/doc/2012-11-05/"><Error><Type>Sender</Type><Code>AccessDenied</Code><Message>Access to the resource https://sqs.us-west-2.amazonaws.com/<removed>/My-Creation-Requests is denied.</Message><Detail/>
    </Error>
    <RequestId>f3ecb080-b3ef-52b1-949b-ea63ef0d23f5</RequestId>
  </ErrorResponse>"

I'm guessing this a permissions problem? I'm not really sure where to go from here. I saw in another thread that someone was having a similar issue and fixed it by adding 'token' => env('AWS_SESSION_TOKEN'), to the config/queue.php file, but mine already has that. Where does this AWS_SESSION_TOKEN get setup? Maybe that's not getting set correctly?

My serverless.yml (I'm using a manually created queue instead of having Lift create it for me, could that be the problem?):

provider:
   ...
    environment:
      ...
      QUEUE_CONNECTION: sqs
      SQS_QUEUE: My-Creation-Requests
      SQS_PREFIX: https://sqs.us-west-2.amazonaws.com/<removed>

  ...
  constructs:
    jobs:
      type: queue
      worker:
        handler: worker.php
        layers:
          - ${bref:layer.php-80}

config/queue.php

'sqs' => [
            'driver' => 'sqs',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'token' => env('AWS_SESSION_TOKEN'),
            'prefix' => env('SQS_PREFIX', 'https://sqs.us-east-1.amazonaws.com/your-account-id'),
            'queue' => env('SQS_QUEUE', 'default'),
            'suffix' => env('SQS_SUFFIX'),
            'region' => env('AWS_DEFAULT_REGION', 'us-east-1'),
            'after_commit' => false,
        ],

[mikevang]

Well I "solved" this by changing the queue setting in serverless.yml to SQS_QUEUE: ${construct:jobs.queueUrl} Not really the approach I wanted, but it's working for now.