Description

• Improve the documentation about the SQS part : https://serverless.com/framework/docs/providers/aws/events/sqs/

As a new serverless user, I'm having trouble understanding how to configure the SQS queue to call lambda after reading the doc;

Few question I've asked myself after reading this doc and started to copy paste the code:

1/ In the example, we have under

I just noticed that in SQS events triggered by creating an S3 object, the size is always 1024, rather than the real size of the file.

With the 'real' AWS, you get the size of the file.

The code in get_event_message() has a default file_size parameter of 1024, but this is n

In the help page for the aws sqs receive-message command, it says:

       --wait-time-seconds (integer)
          The duration (in seconds) for which the call waits for a message  to
          arrive in the queue before returning. If a message is available, the
          call returns sooner than WaitTimeSeconds . If no messages are avail-
          able  and  the wait time expires, t

AWS Lambda currently supports Node v10.x
Can you please support it.

FEATURE REQUEST:
Hi,

I see that there is nothing in the kargo repo related to docker login stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.

I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi

What would be the minimal IAM Policy for deploying, I know the policy on the website, but that has also access to EC2 and is quite broad. For example I would not need to control a domain from there.

Like it would be a role that you could put on Travis-CI and not worry about them deleting your EC2 instances.

I tried deleting everything other than Lambda, API Gateway and S3, but then I began

Do all drivers decode times in UTC? Local time? Do they differ?

We should document, and ideally, make it consistent.

Hello!

I have updated to the new chalice release 1.11.0. I have seen that there are two tickets related with my request:
aws/chalice#976
aws/chalice#897

I would like to handle both lambda and API gateway Resource policy in the same file.

When I ran the

chalice deploy --no-autogen-policy

I bumped in:
**chalice.deploy.deployer

I recently ran into an issue where resource policy on my API was getting updated but was not effective. So essentially a new deployment was not being created by SAM. It's because SAM processes the template before any mapping substitutions and according to SAM nothing changed and it doesn't generate a deployment. However, cloud-formation does the substitutions and updates the API. So you see update

Using the query parameter name "code" causes "invalid_grant" error due to the Amplify listener attempting to validate the parameter as an OAuth code. Might make sense to namespace the code parameter to "awscode" or even validate that the code value looks like an OAuth response code before throwing an error.... took a few hours to debug this.

Goal
I want to minimize the external dependencies in my Lambda code (node.js) as much as possible. I expect this to reduce the size, increase the speed and minimize regression when external libraries change.

Background
My solution needs to call external to AWS REST endpoints, retrieve the results and do further processing on those requests. I hope to use the AWS SDK method Service

• It would be great to update the README to mention the additional utilities that are now supported by the SDK.
• Improve the content of the README by removing replicated information and providing URL's of the appropriate document.

I'm in the preview for a new AWS service, and have added the cli models for that service. I get the following error when running aws-shell.

$ aws-shell
First run, creating autocomplete index...
Traceback (most recent call last):
  File "/usr/local/bin/aws-shell", line 9, in <module>
    load_entry_point('aws-shell==0.1.1', 'console_scripts', 'aws-shell')()
  File "/Library/Python/2.7/si

put_bucket_encryption has a link to AWS API Documentation.

The destination is wrong. Should probably be:

https://docs.aws.amazon.com/AmazonS3/latest/API/RESTBucketPUTencryption.html

Description

The build process doesn't copy over .so files when building a Python Lambda function.

Steps to reproduce

Install the ptvsd library:

pip install

Coming from: aws ec2 describe-reserved-instances

It sure would be great if the docs would list:

1. Which resources SM will watch and audit
2. All of the checks that are available out of the box

In order to find an answer to the second question I had to search through all of the auditor modules and count the individual check methods. By my count there are 152 checks all together, but that could easily be incorrect.

I'm a bit confused about the registerOutputs call and what actually is considered an output.
The current documentation says this:

Components can define their own properties using registerOutputs. The Pulumi engine uses this information to display the logical outputs of the component. The call to registerOutputs also tells Pulumi that the resource is done registering children and should be c

Unable to create an aws_api_gateway_domain_name on the first run (when no infra were previously created). On re-run the resource is created successfully. The behavior is constant and always reproduces.

Community Note

• Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-request