You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We couldn't run the stack because it only supports the N. Virginia region today and we use Ohio, with strict guard rails in place to prevent notifications being received from other regions.
Describe the solution you'd like
Create the stack so that it can be deployed in any region that supports the services.
Describe alternatives you've considered
Manual integration and custom deployment.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
I've run the CFM template multiple time in the southeast-1 region and getting CREATE_FAILED status in CFM.
Steps taken
Launch template
Switch to southeast-1 region
Fill in all required parameters
Run template.
Sample status reason
Resource handler returned message: "Error occurred while GetObject. S3 Error Code: PermanentRedirect. S3 Error Message: The bucket is in this region: us-east-1. Please use this region to retry the request (Service: Lambda, Status Code: 400, Request ID: a20fb286-b414-44b8-8fe5-b9b6208969ad)" (RequestToken: b20325e1-75e7-cd4f-73e3-aebaebc6830b, HandlerErrorCode: InvalidRequest)
Affected LogicalID
MeteringSQSHandler
GrantOrRevokeAccess
SusbscriptionSQSHandler
Hourly
EntitlementSQSHandler
RegisterNewMarketplaceCustomer
SampleApp (failed due to dependencies above)
Is your feature request related to a problem? Please describe.
We couldn't run the stack because it only supports the N. Virginia region today and we use Ohio, with strict guard rails in place to prevent notifications being received from other regions.
Describe the solution you'd like
Create the stack so that it can be deployed in any region that supports the services.
Describe alternatives you've considered
Manual integration and custom deployment.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: