{"action":"created","issue":{"url":"https://api.github.com/repos/lambci/lambci/issues/65","repository_url":"https://api.github.com/repos/lambci/lambci","labels_url":"https://api.github.com/repos/lambci/lambci/issues/65/labels{/name}","comments_url":"https://api.github.com/repos/lambci/lambci/issues/65/comments","events_url":"https://api.github.com/repos/lambci/lambci/issues/65/events","html_url":"https://github.com/lambci/lambci/issues/65","id":188926947,"number":65,"title":"deploying another aws service (s3/lambda/cloudformation)","user":{"login":"thewillhuang","id":7867215,"avatar_url":"https://avatars.githubusercontent.com/u/7867215?v=3","gravatar_id":"","url":"https://api.github.com/users/thewillhuang","html_url":"https://github.com/thewillhuang","followers_url":"https://api.github.com/users/thewillhuang/followers","following_url":"https://api.github.com/users/thewillhuang/following{/other_user}","gists_url":"https://api.github.com/users/thewillhuang/gists{/gist_id}","starred_url":"https://api.github.com/users/thewillhuang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thewillhuang/subscriptions","organizations_url":"https://api.github.com/users/thewillhuang/orgs","repos_url":"https://api.github.com/users/thewillhuang/repos","events_url":"https://api.github.com/users/thewillhuang/events{/privacy}","received_events_url":"https://api.github.com/users/thewillhuang/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-11-12T18:32:49Z","updated_at":"2016-11-12T22:39:24Z","closed_at":null,"body":"I've been trying hard to deploy an [Apex](http://apex.run/) lambda function via LambCi to get the same build environment. I'm having some difficulty.\r\n\r\nIn my dynamo DB, I've set up a separate AWS credential and region just like the readme. But I get an error similar to https://gist.github.com/cmawhorter/3cf67164414c4a97fcd8\r\n\r\nI've also tried every step given in the gist that includes\r\n- lambda full access permission\r\n- IAM roles full permission\r\n\r\nMy suspicion is that somehow the AWS credentials that I gave it is being replaced by lambda's own credentials.\r\n\r\nhere is the repo commit for reference https://github.com/thewillhuang/rancher-in-apex/commits/master\r\n\r\nI've also tried to get Apex to run on [circle](https://circleci.com/gh/thewillhuang/rancher-in-apex/5?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link), and it was successful. The commands and the AWS credentials are the same.\r\n\r\nso my question is, what's the best way to **securely** use another AWS credential in a public repo? Or better yet, what am I doing wrong and how to fix it?"},"comment":{"url":"https://api.github.com/repos/lambci/lambci/issues/comments/260153345","html_url":"https://github.com/lambci/lambci/issues/65#issuecomment-260153345","issue_url":"https://api.github.com/repos/lambci/lambci/issues/65","id":260153345,"user":{"login":"thewillhuang","id":7867215,"avatar_url":"https://avatars.githubusercontent.com/u/7867215?v=3","gravatar_id":"","url":"https://api.github.com/users/thewillhuang","html_url":"https://github.com/thewillhuang","followers_url":"https://api.github.com/users/thewillhuang/followers","following_url":"https://api.github.com/users/thewillhuang/following{/other_user}","gists_url":"https://api.github.com/users/thewillhuang/gists{/gist_id}","starred_url":"https://api.github.com/users/thewillhuang/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thewillhuang/subscriptions","organizations_url":"https://api.github.com/users/thewillhuang/orgs","repos_url":"https://api.github.com/users/thewillhuang/repos","events_url":"https://api.github.com/users/thewillhuang/events{/privacy}","received_events_url":"https://api.github.com/users/thewillhuang/received_events","type":"User","site_admin":false},"created_at":"2016-11-12T22:39:24Z","updated_at":"2016-11-12T22:39:24Z","body":"Makes sense! The main problem is that sometimes with other libraries such as Apex, it is not possible to call another ENV unless I fork it and rebuild it from source. Depending on the author of these tools, it's not always something the user has control over. Which is why I think having a way to set a new AWS credential by default and revert to lambda's would be a better developer experience"}}
{"actor":{"display_login":"thewillhuang"}}