-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix] cfn exec policies error and specify profile #10
Conversation
The updated version of CDK requires that Cloudformation execution policies are passed in for the toolkit stack. By default, we're okay to set this as AdministratorAccess, but I've added the ability for a user to specify it under `provider` in `serverless.yml` too. Also, we shouldn't rely on AWS creds before we even log in with AWS creds - useful e.g. if the user sets a profile. Previously, we used the STS client directly to get acct ID. Now, we get default acct ID from the SDK provider or pull from `provider.accountId` if specified.
Also applied |
Terrific, thank you so much! |
Does that solve your issue? If so, I'll try to get it merged and released tomorrow morning UK time 🙂 And if it doesn't, feel free to ping over any other errors you hit and I'm happy to see what I can do! |
Now this:
|
Hm, looks like For example: "scripts": {
// ... other scripts
"sls": "tsc && sls",
// ... other scripts
}, Just to check, is there a |
I installed latest global and local sls, sls will use sls from local node_modules in recent versions. I have node_modules/uuid I had serverless-aws-cdk npm linked though and after running And now it deploys! Thanks for all your help! This is fabulous |
Well it created the stack. After building my infra it spat out:
|
@revmischa Just to check, was the above issue fixed by #12? |
The CfnRole issue is fixed yes, thanks a million for your help with that |
Great, and has it stopped emitting the |
I think this helped that #12 Problem may be related to running with |
The updated version of CDK requires that Cloudformation execution policies are passed in for the toolkit stack. By default, we're okay to set this as AdministratorAccess, but I've added the ability for a user to specify it under
provider
inserverless.yml
too.Also, we shouldn't rely on AWS creds before we even log in with AWS creds - useful e.g. if the user sets a profile. Previously, we used the STS client directly to get acct ID. Now, we get default acct ID from the SDK provider or pull from
provider.accountId
if specified.