The template arn is from a different account. We are deploying to another account in a different env. Cross account permission is not an option. Is there way that instead of providing a reference to a template arn, we can provide the template jsons so it does not have to access the template arn account?
Hello @alltej - You can now leverage the Asset As Bundle Methodology. Please go through the below link and I believe this will be helpful especially the cross account deployment section.
Hope this helps!
I think that example works for 1 target (default namespace?). Does the cli provide a target namespace? I need to deploy the bundle to multiple namespaces. Currently(not the asset-as-bundle) I loop through all the namespaces and call the create/update of dashboards and datasets. During each loop I have run validation of memberships, folders, etc. How can I implement that with asset-as-bundle? Is there an example that you point me to?
@alltej - In the Blog post link, that I shared there are multiple example scenarios given with some sample statements / commands. Did you get a chance to look at that?
Hi @alltej
We have not heard back from you regarding your question. We would still like to help. If we do not hear back in the next 3 days, we will archive the question
In the export job, I see that you can specify the target region. Can we specify a different aws partition?
@alltej - Can you please specify what do you mean by Partition? Are you referring to QuickSight namespace?
Namespace like “aws”, “aws-cn” or “aws-us-gov”.
@alltej - Not quite. Please go through the following link regarding namespace, which I was alluding to in my previous post. Namespace helps us to segregate assets logically within a single QuickSight account. Hope this helps!
I am getting error in the describe-asset-bundle-export-job:
"NetworkInterfaces should have more than 1 item for VPC connection...
A simple describe-vpc-connection did not return an error.
Is this a known issue? Or is there a work-around currently?
I resolved the issue by adding another subnet in the VPC.
A few months back, QS released new APIs for creating/updating VPC Connections. QS now requires all newly created/updated VPC connections to have two or more subnet IDs. Please see the updated API documentation and user guide.