Invalid parameter: TopicArn Reason: An ARN must have at least 6 elements

[dilip-ezops]

Describe the bug

We are deploying landing page for our Marketplace integration. While deploying facing following issues:
Invalid parameter: TopicArn Reason: An ARN must have at
least 6 elements, not 1 (Service: AmazonSNS; Status Code:
400; Error Code: InvalidParameter; Request ID:
98904f2c-9377-56e1-b024-17dcd6a302ad; Proxy: null)User: arn:aws:iam::xxxxxxx:user/xxxxxx is
not authorized to perform: SNS:Subscribe on resource:
arn:aws:sns:us-east-1:287250355862:aws-mp-entitlement-
notification-XXXXXXXX (Service: AmazonSNS;
Status Code: 403; Error Code: AuthorizationError; Request
ID: da0cfc82-d12a-5dfd-b1a6-a472cb4f9071; Proxy: null)
To resolve this issue we commented out EntitlementSQSHandler block from template.yaml.

We were able to deploy the landing page. However when we tried to access web page. It displays following error:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

AccessDenied
Access Denied
Z9161D15XV37JFVH
zrlf9xukKblFljCwM3uMD0j60Vj54fQZrfoHNiXl7wvOVzMt7cwGzXJTN3CB/LJUE0fLVuDvGg0=

[vikramkapoor]

@dilip-ezops We are facing exactly the same issue. Did you find any solution for this yet?

[vikramkapoor]

@dilip-ezops We are facing exactly the same issue. Did you find any solution for this yet?

I found that the fix is not to comment out the EntitlementSQSHandler block from template.yaml.

[dilip-ezops]

@dilip-ezops We are facing exactly the same issue. Did you find any solution for this yet?

I found that the fix is not to comment out the EntitlementSQSHandler block from template.yaml.

@vikramkapoor I am still struggling with the same, need to provide cross-account access to cloudformation for SNS topic subscription

[vikramkapoor]

After I uncommented EntitlementSQSHandler and re-ran the steps everything seems to be working. I am able to register new users but need to test other usecases. On Monday, May 10, 2021, 12:16:43 AM PDT, dilip-ezops ***@***.***> wrote: @dilip-ezops We are facing exactly the same issue. Did you find any solution for this yet? I found that the fix is not to comment out the EntitlementSQSHandler block from template.yaml. @vikramkapoor I am still struggling with the same, need to provide cross-account access to cloudformation for SNS topic subscription — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[AffiTheCreator]

Hi Everyone,

The issue you are facing is not a bug , there is an extra parameter you need to add when launching via sam.

In the README there is a table, this table contains TypeOfSaaSListing , here you can find the 3 options available (notice the default value).

Since most likely you are creating a SaaS subscription or Contract , in saas only you don't have the EntitlementSQS SNS only the subscription. The inverse is true for contracts only.

Since the default is both (saas and contract) and you only 1 type you get this error. You only provided 1 but it expected 2 and both need to follow arn:********

Hope this help.