aws-samples / ac-multi-region-apis Goto Github PK

License: MIT No Attribution

CSS 11.85% HTML 26.79% JavaScript 61.36%

ac-multi-region-apis's Introduction

Amazon Connect Global Resiliency APIs demo

This demo shows how you can leverage Amazon Connect Global Resiliency APIs and manage Traffic Distribution Groups(TDG), Claim a phone number to a TDG, Percentage allocate traffic between 2 regions etc.

Usage

Use sam to build, invoke and deploy the function.

SAM Build:

Ensure you are in the root folder

sam build --use-container

SAM Deploy:

sam deploy template.yaml --s3-bucket REPLACE_ME --stack-name REPLACE_ME --parameter-overrides ParameterKey=parS3BucketForWebSite,ParameterValue=REPLACE_ME --capabilities CAPABILITY_IAM

ac-multi-region-apis's People

Contributors

Stargazers

Watchers

Forkers

reziakk

ac-multi-region-apis's Issues

Error While deploying cloudformation template

Hi Team

We are deploying the below blog for "Build a multi-region resilient contact center with Amazon Connect global resiliency"
https://aws.amazon.com/blogs/contact-center/build-a-multi-region-resilient-contact-center-with-amazon-connect-global-resiliency/

We are facing the below error.
Properties validation failed for resource webSiteCreator with message: #/Code: expected type: JSONObject, found: String.

\"#/Code: expected type: JSONObject, found: String

Hi Team,

We are getting the error while run the cloud formation template . We have open the ticket with support team and they have suggest some issue with cloud formation template Please check with blog owner.

The Issue:

I do understand that while trying to impelment the solution in Link: [1] below, the CloudFormation stack failed with error message: "#/Code: expected type: JSONObject, found: String".

Investigation:

Checking the CloudFormation stack events and the related CloudTrail background events, I found the following Api call:

{
"Role": "arn:aws:iam::********:role/test",
"MemorySize": "256",
"Runtime": "nodejs14.x",
"Description": "AWS Lambda Function that will create the website and upload it to the S3 bucket\n",
"Timeout": "120",
"Handler": "index.handler",
"Code": "./website-creator"
}

Inspecting the Stack template I can see the Lambda Function resource definition is referring to a local directory for the Code property

Getting error in Cloudformation template of Module 3

Hi Team,
We have followed below blog for AWS global resiliency implementation but getting error on importing Module 3 Cloudformation template.
https://aws.amazon.com/blogs/contact-center/build-a-multi-region-resilient-contact-center-with-amazon-connect-global-resiliency/

Error while importing Cloudformation template of Module 3 -
Properties_ validation failed for resource webSiteCreator with message: #/Code: expected type: JSONObject, found: String._

This demo is failing when deploying with S3 error

Hello,

I tried this demo using the SAM deployment as well as the usual CloudFormation deployment and it seems to fail due to an issue with the S3 bucket ACL, which presumably is from the change AWS made to S3 in April regarding new S3 buckets. Here is the failure message I receive from CloudFormation:
"Invalid request provided: AWS::CloudFront::Distribution: The S3 bucket that you specified for CloudFront logs does not enable ACL access: bmassey215-06-15-2023-test-mrr-stack.s3.amazonaws.com (Service: CloudFront, Status Code: 400, Request ID: a9685ef3-f66e-4ea8-97af-8290408ca1bd)" (RequestToken: 1faf67f1-c4e6-c1c4-411b-5ccf166eab3d, HandlerErrorCode: InvalidRequest)"

I tried modifying the YAML file several different ways to get around this, such as changing the PublicAccessBlockConfiguration to all be False or adding an ObjectOwnership line in the properties under resources, etc, but none of them worked. Is there a fix for this code/template file to account for the new S3 bucket creation ACL?

Thank you