-
Setup Repository secrets in github repo.
- Repository Settings --> Secrets and variables
- Use these keys to setup repository secretsAWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY -
You need to add openapi secrets in AWS secrete manager service: -
CHAT_GPTas secret name. - chat gpt api key asAPI_KEYsecret. - chat gpt org id asORG_IDsecret. -
Edit
samconfig.tomlfile.
- changestack_name,s3_bucket_for_artifacts,s3_prefix.
-stack_nameis being used as cloudformation stack name.
-s3_bucket_for_artifactsis being used to create S3 bucket to store artifacts when sam builds.
- changeparameter_overridesas well for all three sub-parameters. -
If the S3 Bucket for Artifacts is already present in AWS, then it will skip the creation for artifacts s3 bucket
and continue with the remaining steps in the github action. -
Else if, there is no S3 bucket present in AWS, then it will create the artifact s3 bucket
but it will skip all the remaining steps in github action. -
Just Re-Run the job, if you encounter step 4.
-
You can use
sourceData.xlsxfile for source data in your dynamodb to get the results on the webpage.
- You can find the deployed project cloudfront link / webpage link in your github actions tab.
- Or you can check your cloudformation console --> Outputs tab to get cloudfront link / webpage link.