Skip to content
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.

Sign up for GitHub

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

Upgrade to Python 3.9 #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Upgrade to Python 3.9 #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ If you are rebuilding the function or deploying it manually instead of using the
```
>Please note the labelled version in Github does not include any user queries.
1. Create a Lambda function, and upload the zip file generated by the build script. some of the parameters of the function are:
* Runtime: Python 3.6
* Runtime: Python 3.9
* Handler: `lambda_function.lambda_handler`
* Role: Use the role created above
* Memory: 256MB
Expand All @@ -188,9 +188,9 @@ If you are rebuilding the function or deploying it manually instead of using the
After a period of time, you can check your CloudWatch metrics and create alarms. You can also view the AuroraPostgresAdvancedMonitoringDashboard that was created as part of the CloudFormation script to visualize the custom metrics.

![Dashboard1](dashboard1.png)
![Dashboard2](dashboard2.png)
![Dashboard2](dashboard2.PNG)

If the metrics are not being emitted properly after deploying the solution, send a test event to the Lambda function with a JSON payload similar to [the one shown above](#EventJson) where Debug is set to True (update parameters to match your environment). This will log additional details to help you uncover the cause of the failure. The most common issues are 1) Lack of network connectivity between the Lambda function amd the KMS and Cloudwatch APIs, and 2) Insufficient permissions on the database. [Review the Pre-Requisites](#PreReqs) for solutions to these issues.
If the metrics are not being emitted properly after deploying the solution, send a test event to the Lambda function with a JSON payload similar to [the one shown above](#EventJson) where Debug is set to True (update parameters to match your environment). This will log additional details to help you uncover the cause of the failure. The most common issues are 1) Lack of network connectivity between the Lambda function and the KMS and Cloudwatch APIs, and 2) Insufficient permissions on the database. [Review the Pre-Requisites](#PreReqs) for solutions to these issues.

## <a name="MetricDefinitions"></a>Metric Definitions

Expand Down
2 changes: 1 addition & 1 deletion deploy-non-vpc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Resources:
Type: AWS::Serverless::Function
Properties:
Handler: lambda_function.lambda_handler
Runtime: python3.6
Runtime: python3.9
CodeUri:
Bucket: !Sub paramsey-cfn-${AWS::Region}
Key: AuroraPostgresAdvancedMonitoring/aurora-postgres-advanced-monitoring-1.0.zip
Expand Down
2 changes: 1 addition & 1 deletion deploy-vpc.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ Resources:
Type: AWS::Serverless::Function
Properties:
Handler: lambda_function.lambda_handler
Runtime: python3.6
Runtime: python3.9
CodeUri:
Bucket: !Sub paramsey-cfn-${AWS::Region}
Key: AuroraPostgresAdvancedMonitoring/aurora-postgres-advanced-monitoring-1.0.zip
Expand Down