Skip to content

Instantly share code, notes, and snippets.

@tbeseda
Created October 9, 2015 03:00
Show Gist options
  • Save tbeseda/dae28f61f89b957e60fe to your computer and use it in GitHub Desktop.
Save tbeseda/dae28f61f89b957e60fe to your computer and use it in GitHub Desktop.
Trouble with JAWS Quick Start Deploy, AccessDeniedException during endpoint deploy

Following the Quick Start in the Readme, an AccessDeniedException error is reported during the endpoint deployment.

$ jaws dash

JAWS: Dashboard for project "jaws-test2"
 -------------------------------------------
 Project Summary
 -------------------------------------------
    Stages: 
       dev us-east-1 
    Lambdas: 1
    Endpoints: 1
 -------------------------------------------
 Select Resources To Deploy
 -------------------------------------------  
    greetings/hello
      L) lGreetingsHello
      E) /greetings/hello - GET
    - - - - -
  >   Deploy Selected -->
JAWS: -------------------------------------------  
JAWS:  Dashboard:  Deploying Lambdas...  
JAWS: -------------------------------------------  
JAWS: Lambda Deployer:  Packaging "lGreetingsHello"...  
JAWS: Lambda Deployer:  Saving in dist dir /var/folders/z0/9b57q8t94nvgp81p9fjc_kbc0000gn/T/lGreetingsHello@1444358363281  
JAWS: Getting ENV file from S3 bucket: jaws.dev.useast1.myapp-vj8qwgee.com in us-east-1  
JAWS: Lambda Deployer:  Bundled file written to /var/folders/z0/9b57q8t94nvgp81p9fjc_kbc0000gn/T/lGreetingsHello@1444358363281/bundled.js  
JAWS: Lambda Deployer:  Minified file written to /var/folders/z0/9b57q8t94nvgp81p9fjc_kbc0000gn/T/lGreetingsHello@1444358363281/minified.js  
JAWS: Lambda Deployer:  Compressed lambda written to /var/folders/z0/9b57q8t94nvgp81p9fjc_kbc0000gn/T/lGreetingsHello@1444358363281/package.zip  
JAWS: Lambda Deployer:  Uploading lGreetingsHello to jaws.dev.useast1.myapp-vj8qwgee.com  
JAWS: Running CloudFormation lambda deploy...  
JAWS: Lambda Deployer:  Done deploying lambdas in us-east-1  
JAWS: Lambda Deployer:  Successfully deployed lambdas to the requested regions!  
JAWS: -------------------------------------------  
JAWS:  Dashboard:  Deploying Endpoints...  
JAWS: -------------------------------------------  
JAWS: Endpoint Deployer:  Deploying endpoint(s) to region "us-east-1"...  
JAWS: Endpoint Deployer:  "dev - us-east-1": found 1 endpoints to deploy  
JAWS: Endpoint Deployer:  "dev - us-east-1": created a new REST API on AWS API Gateway with ID: e10lxidklg  
JAWS: Endpoint Deployer:  "dev - us-east-1": found 1 existing resources on API Gateway  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created resource: greetings  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created resource: hello  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created method: GET  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created integration with the type: AWS  
{ [AccessDeniedException: Unable to determine service/operation name to be authorized]
  message: 'Unable to determine service/operation name to be authorized',
  code: 'AccessDeniedException',
  time: Thu Oct 08 2015 20:39:46 GMT-0600 (MDT),
  statusCode: 403,
  retryable: false,
  retryDelay: 30 }
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created method response  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created method response  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created method integration response  
JAWS: Endpoint Deployer:  "dev - us-east-1 - greetings/hello": created method integration response  
JAWS: Endpoint Deployer:  Endpoints for stage "dev" successfully deployed to API Gateway in the region "us-east-1". Access them @ https://e10lxidklg.execute-api.us-east-1.amazonaws.com/dev/  
JAWS: -------------------------------------------  
JAWS:  Dashboard:  Deployments Completed  
JAWS: -------------------------------------------  

Further, visiting https://e10lxidklg.execute-api.us-east-1.amazonaws.com/dev/greetings/hello returns {"message": "Internal server error"}

My IAM user has the managed AdministratorAccess policy attached: iam-user

Any help is appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment