Enabling the automated process of using the events generated by their Pinpoint campaigns to rapidly train and optimize their Personalize campaigns.
- Clone the repository, then make the desired code changes
- Next, run unit tests to make sure added customization passes the tests
cd ./deployment
chmod +x ./run-unit-tests.sh \n
./run-unit-tests.sh \n
- Configure the bucket name of your target Amazon S3 distribution bucket
export DIST_OUTPUT_BUCKET=my-bucket-name # bucket where customized code will reside
export SOLUTION_NAME=my-solution-name
export VERSION=my-version # version number for the customized code
Note: You would have to create an S3 bucket with the prefix 'my-bucket-name-<aws_region>'; aws_region is where you are testing the customized solution. Also, the assets in bucket should be publicly accessible.
- Now build the distributable:
chmod +x ./build-s3-dist.sh \n
./build-s3-dist.sh $DIST_OUTPUT_BUCKET $SOLUTION_NAME $VERSION \n
- Deploy the distributable to an Amazon S3 bucket in your account. Note: you must have the AWS Command Line Interface installed.
aws s3 cp ./dist/ s3://my-bucket-name-<aws_region>/$SOLUTION_NAME/$VERSION/ --recursive --acl bucket-owner-full-control --profile aws-cred-profile-name \n
- Get the link of the solution template uploaded to your Amazon S3 bucket.
- Deploy the solution to your account by launching a new AWS CloudFormation stack using the link of the solution template in Amazon S3.
|-deployment/
|-build-s3-dist.sh [ shell script for packaging distribution assets ]
|-run-unit-tests.sh [ shell script for executing unit tests ]
|-amazon-personalize-optimizer-using-amazon-pinpoint-events.yaml [ solution CloudFormation deployment template ]
|-source/
|-01-cleanup-lambda [ micoservice to clean up temp files ]
|-02-export-pinpoint-endpoints-lambda [ microservice to initiate an Amazon Pinpoint export ]
|-03-export-status-lambda [ microservice to check on the export status ]
|-04-query-augment-start-lambda [ microservice to initiate an Amazon Athena query ]
|-05-query-status-lambda [ microservice to check on the query status ]
|-06-dataset-import-lambda [ microservice to initiate an Amazon Personalize dataset import ]
|-07-dataset-import-status-lambda [ microservice to check on the import status ]
|-08-create-solution-version-lambda [ microservice to initiate an Amazon Personalize solution version ]
|-09-create-solution-version-status-lambda [ microservice to check on the solution version ]
|-10-update-campaign-lambda [ microservice to initiate an Amazon Personalize campaign update ]
|-11-update-campaign-status-lambda [ microservice to check on the campaign update status ]
|-custom-resource-helper [ microservice to help deploy queries during CF deployment ]
|-firehose-record-conversion-lambda [ microservice to transform the Amazon Pinpoint event stream events ]
Each microservice follows the structure of:
|-service-name/
|-index.js [injection point for microservice]
|-package.json
Copyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Licensed under the Apache License Version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at
http://www.apache.org/licenses/
or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied. See the License for the specific language governing permissions and limitations under the License.