Richard H Boyd

I've discovered a cleaner way to do this lately ```python import boto3 from botocore.auth import SigV4Auth from botocore.awsrequest import AWSRequest import requests session = boto3.Session() credentials = session.get_credentials() creds =...

yeah, the request.headers part can also be re-used for websockets that need IAM Auth (Neptune Gremlin connections) and the credentials work in a more environment agnostic way as well.

can you clarify the question a little bit? you can sign requests using the security token as well but you shouldn't have to pass the actual credentials in the header....

the first message meant that the request was signed properly but you didn't have permission to invoke the API. what does the API's resource policy look like?

Okay, so there's a few different resources here we need to be clear about. -API Gateway API -API Gateway execution Role (let's call this RoleA) -Lambda Function Execution Role (RoleB)...

I'm seeing this on Amazon Linux as well. I suspect that the [`setup.py`](https://github.com/aws/jsii/blob/7dd04fe9987bbba7b1360162b7afc2caf15a50e6/packages/%40jsii/python-runtime/setup.py#L9) file generated by JSII is referencing a README.md file that doesn't exist. If I follow the directions...

disregard. I'm a big 'ole dummy. ## Old and busted ````bash pip install ../jsii-test/dist/python/acme.hello-jsii-1.0.0.tar.gz --user ```` ## New hotness ````bash pip install --no-index --find-links=../jsii-test/dist/python acme.hello_jsii ````

Did you recently change the method signatures to include line-breaks? That was my biggest pet peeve but it seems to be fixed now.

@brainstorm can you elaborate a bit more on "fix"? Are you referring to one large package that includes all CDK modules instead of individual modules per service?

We're working on something similar with [monocdk](https://github.com/aws/aws-cdk/tree/master/packages/monocdk-experiment)