updating docs for AWS and Salesforce side setup (#66)

* updating docs for AWS and Salesforce side setup * updating docs for AWS and Salesforce side setup * updating docs for AWS and Salesforce side setup Co-authored-by: Mayank Bakshi <[email protected]>
amazon-connect · Jul 14, 2021 · afe33b2 · afe33b2
1 parent 8ec4cdf
commit afe33b2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 4 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1,4 +1,7 @@
 *.DS_Store
 node_modules
 .docusaurus
-build
+build
+.idea
+.settings
+.project
diff --git a/docs/lightning/04-salesforce-lambdas/04-contact-channel-analytics.md b/docs/lightning/04-salesforce-lambdas/04-contact-channel-analytics.md
@@ -95,7 +95,7 @@ Cloudformation stack:
 
 4. Under the "Secret value" tab, select "Retrieve secret value" and then "Edit".
 
-5. For the **CloudFrontPrivateKey** field, copy and paste the modified contents of the private key .pem file. For the **CloudFrontAccessKeyID** field, copy and paste the **Access Key Id** you recorded above. Your Secrets Manager Secret should look like the following:
+5. For the **CloudFrontPrivateKey** field, copy and paste the modified contents of the private key .pem file. For the **CloudFrontAccessKeyID** field, copy and paste the **public key ID** you recorded above. Your Secrets Manager Secret should look like the following:
 
 <img src={useBaseUrl('/img/lightning/image270.png')} />
 
@@ -170,9 +170,9 @@ Please note that your secret may also be formatted stored as a "Secret key/value
 
 3. In the **URL** section, enter `https://lambda.{awsRegion}.amazonaws.com/2015-03-31/functions/{lambdaFunctionName}/invocations/`-- replace {awsRegion} with the awsRegion your serverless application resides in (for example, us-east-1), and replace {lambdaFunctionName} with the full name of the sfGenerateAudioRecordingStreaming lambda you recorded in the previous section.
 
-> Note: There is an intermittant bug with salesfore where the trailing `/` causes an error. Try using `https://lambda.{awsRegion}.amazonaws.com/2015-03-31/functions/{lambdaFunctionName}/invocations` as the **URL** if you see an error message such as *The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.*
+> Note: There is an intermittent bug with salesfore where the trailing `/` causes an error. Try using `https://lambda.{awsRegion}.amazonaws.com/2015-03-31/functions/{lambdaFunctionName}/invocations` as the **URL** if you see an error message such as *The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.*
 
-4. For **Identity Type** select **Named Principal**. For the **Authentication Protocol**, select **AWS Signature Version 4**. Fill in the **Public Key ID** you recorded in the previous section as "AWS Access Key ID", the **Secret access key** as the "AWS Secret Access Key", the AWS Region, and "lambda" as the "AWS Service."
+4. For **Identity Type** select **Named Principal**. For the **Authentication Protocol**, select **AWS Signature Version 4**. Fill in the **Access key ID** you recorded in the previous section as "AWS Access Key ID", the **Secret access key** as the "AWS Secret Access Key", the AWS Region your application resides in (for example, us-east-1), and "lambda" as the "AWS Service".
 
 <img src={useBaseUrl('/img/lightning/image275.png')} />