Skip to content

Commit f4b218f

Browse files
authored
Update README for some troubleshooting steps
1 parent 45c7156 commit f4b218f

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

s3-logs-extension-demo-zip-archive/README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ cd s3-logs-extension-demo-zip-archive
3535
1. Run the following command for AWS SAM to deploy the components as specified in the `template.yml` file:
3636
```bash
3737
sam build
38-
# If you don't have 'Python' or 'make' installed, you can use the option to build using a container which uses a python3.8 Docker container image
38+
# If you receive build errors or don't have 'Python' or 'make' installed, you can use the option to build using a container which uses a python3.8 Docker container image.
3939
# sam build --use-container
4040
sam deploy --stack-name s3-logs-extension-demo --guided
4141
```
@@ -70,4 +70,7 @@ The logging extension also receives the log stream directly from Lambda, and cop
7070

7171
Browse to the [Amazon S3 Console](https://console.aws.amazon.com/S3). Navigate to the S3 bucket created as part of the SAM deployment.
7272

73-
Downloading the file object containing the copied log stream. The log contains the same platform and function logs, but not the extension logs, as specified during the subscription.
73+
Downloading the file object containing the copied log stream. The log contains the same platform and function logs, but not the extension logs, as specified during the subscription.
74+
75+
If you receive a `permission denied Extension.LaunchError` in the logs, the extension does not have the neccesary permissions.
76+
Run `chmod +x logs_api_http_extension.py` and build and deploy the AWS SAM application again.

0 commit comments

Comments
 (0)