The following resource(s) failed to create: [VPCStack]. . Rollback requested by user.
templates/tableau-single-server-master.template

Embedded stack arn:aws:cloudformation:ca-central-1:281621781242:stack/TableauSingleNodeWindowsInstall-VPCStack-1C5FZ94RP4S7H/86aea220-92ad-11e9-80f7-0607b10fa94c was not successfully created: The following resource(s) failed to create: [PublicSubnet2, PublicSubnet1, PublicSubnetRouteTable, VPCGatewayAttachment].

Am looking to upgrade the tableau server to 2021 version in AWS cloud using this template. This template was used for 2019 and 2020 version which worked just fine. Post log4j issue Wwe are planning to upgrade to 2021 version by testing in dev

    "TableauServerInstaller": "https://s3-us-west-2.amazonaws.com/tableau-quickstart/tableau-server-2020-1-0.x86_64.rpm"

The above link should work for 2021 version. How can I manage that. Please help

Hi ,

I need to enable "Active Directory" Instance store with the silent installer script.
i cna pretty clearly get the "local" instance store working with the silent installer script, but the active directry fails.

i'm using the below as config file:
{
"configEntities":{
"identityStore": {
"_type": "identityStoreType",
"type": "activedirectory",
"domain": "domainx.com",
"nickname": "domainx.com",
}
}
}

This presents itself in similar way to #91

2023-08-16 07:35:26,843 [INFO] Running config step2
2023-08-16 07:35:26,843 [DEBUG] No packages specified
2023-08-16 07:35:26,843 [DEBUG] No groups specified
2023-08-16 07:35:26,843 [DEBUG] No users specified
2023-08-16 07:35:26,843 [DEBUG] No sources specified
2023-08-16 07:35:26,844 [DEBUG] Writing content to /tmp/tag-instance.py
2023-08-16 07:35:26,844 [DEBUG] Retrieving contents from https://aws-quickstart-eu-west-1.s3.eu-west-1.amazonaws.com/quickstart-tableau-server/scripts/tag-instance.py
2023-08-16 07:35:26,931 [DEBUG] Setting mode for /tmp/tag-instance.py to 550
2023-08-16 07:35:26,931 [DEBUG] Running command a
2023-08-16 07:35:26,932 [DEBUG] No test for command a
2023-08-16 07:35:27,051 [ERROR] Command a (python3 tag-instance.py --tagname Name --tagvalue Tableau-Server-Linux --region eu-west-1) failed
2023-08-16 07:35:27,051 [DEBUG] Command a output: Traceback (most recent call last):
  File "tag-instance.py", line 3, in <module>
    import boto3
  File "/usr/local/lib/python3.7/site-packages/boto3/__init__.py", line 17, in <module>
    from boto3.session import Session
  File "/usr/local/lib/python3.7/site-packages/boto3/session.py", line 17, in <module>
    import botocore.session
  File "/usr/local/lib/python3.7/site-packages/botocore/session.py", line 26, in <module>
    import botocore.client
  File "/usr/local/lib/python3.7/site-packages/botocore/client.py", line 15, in <module>
    from botocore import waiter, xform_name
  File "/usr/local/lib/python3.7/site-packages/botocore/waiter.py", line 18, in <module>
    from botocore.docs.docstring import WaiterDocstring
  File "/usr/local/lib/python3.7/site-packages/botocore/docs/__init__.py", line 15, in <module>
    from botocore.docs.service import ServiceDocumenter
  File "/usr/local/lib/python3.7/site-packages/botocore/docs/service.py", line 13, in <module>
    from botocore.docs.bcdoc.restdoc import DocumentStructure
  File "/usr/local/lib/python3.7/site-packages/botocore/docs/bcdoc/restdoc.py", line 17, in <module>
    from botocore.compat import OrderedDict
  File "/usr/local/lib/python3.7/site-packages/botocore/compat.py", line 32, in <module>
    from urllib3 import exceptions
  File "/usr/local/lib/python3.7/site-packages/urllib3/__init__.py", line 42, in <module>
    "urllib3 v2.0 only supports OpenSSL 1.1.1+, currently "
ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with 'OpenSSL 1.0.2k-fips  26 Jan 2017'. See: https://github.com/urllib3/urllib3/issues/2168

2023-08-16 07:35:27,051 [ERROR] Error encountered during build of step2: Command a failed
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 579, in run_config
    CloudFormationCarpenter(config, self._auth_config, self.strict_mode).build(worklog)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 278, in build
    self._config.commands)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/command_tool.py", line 127, in apply
    raise ToolError(u"Command %s failed" % name)
cfnbootstrap.construction_errors.ToolError: Command a failed
2023-08-16 07:35:27,067 [ERROR] -----------------------BUILD FAILED!------------------------
2023-08-16 07:35:27,067 [ERROR] Unhandled exception during build: Command a failed
Traceback (most recent call last):
  File "/opt/aws/bin/cfn-init", line 181, in <module>
    worklog.build(metadata, configSets, strict_mode)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 137, in build
    Contractor(metadata, strict_mode).build(configSets, self)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 567, in build
    self.run_config(config, worklog)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 579, in run_config
    CloudFormationCarpenter(config, self._auth_config, self.strict_mode).build(worklog)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/construction.py", line 278, in build
    self._config.commands)
  File "/usr/lib/python3.7/site-packages/cfnbootstrap/command_tool.py", line 127, in apply
    raise ToolError(u"Command %s failed" % name)
cfnbootstrap.construction_errors.ToolError: Command a failed```


#this is from cfn-init.log. any suggestions for how to resolve this?

I keep getting this error when trying to set up:

Ideas?

I am currently not able to install a 2020.1 or 2020.2 stack as Tableau Server Management Add-on is required and is not enabled for our license keys. A ticket with Tableau has been opened and they have replied with this:

As we discussed, upon review of the Tableau Server logs, it was identified that during the CloudFormation installation, the backgrounders are being configured with specific roles when the number of nodes is greater than 2. However assigning roles for Backgrounders requires the Data Management Add-on, and that is not specified as a hard requirement for using the CloudFormation Template. The result is that the configuration fails because the current key doesn't have the Data Management Add-on.

With Tableau not requiring the Data Management Add-on, yet the CloudFormation template has stipulations for a key with the add on (specifically for deployments with nodes greater than 2), we've found the issue resides with the code of the template. To resolve the issue, a bug report will need to be filed on the Github site for the template.

This can be fixed by changing lines 713 -717.

This code customizes the backgrounder node roles without checking to see if a data management add-on license is present. Since the Data Management is not a requirement, these customization should not be made or should only happen when it is verified that the Data Management Add on License is present.

(CloudFormation Tableau Template
https://github.com/aws-quickstart/quickstart-tableau-server/blob/master/templates/tableau-cluster-linux.template)

Hi,

It looks like tableau-cluster-windows.template is missing the Mapping for AWSAMIRegionMap:

I have added the mapping from tableau-cluster-windows-master.template however, the AMI for ap-southeast-2 seems to be deprecated and CloudFormation is giving below error.

API: ec2:RunInstances Not authorized for images: [ami-0b90712bab07bff79]

Can someone confirm if the AMI's are correct and update the correct AMI if possible.

Thanks
Mayur

Hello.

I was able to run the Linux standalone server quickstart successfully (using Ubuntu), but encountered the following hurdles that weren't documented in the deployment guide.

1. When I connected to the Tableau Services Manager URL output by CloudFormation (https://#.#.#.#:8850/#/status), my browser complained that the connection was not secure, and I had to add a security exception. The discussion of SSL certificates in the deployment guide appears to be related to inter-instance communication in a cluster setup.

2. After I logged in as tsmadmin and various configurations were deployed in a window resembling a terminal, I got a message like "installation is incomplete - someone with admin access must connect to the instance with localhost". It took me a while to find the solution, which is to execute tabcmd initialuser --server 'localhost:80' --username 'tsadmin', but the user executing this must be a member of both the sudo and tsmadmin groups. If that condition is not true, the error messages from tabcmd are misleading.

Does it sound as if I missed a required step in the setup?

Current Quickstart template has three AZs for deployment.

Please let me know how to install in Two AZ. One AZ for Tableau Server and Another AZ for Workers.

I created an instance in sa-east-1 through the quickstart.
Everything worked as expected. The stacks are completed:

and in the outputs I have the URL's to start configuring the server:

But when I try to enter the administration site, in the 8850 port, the site can't be reached:

So I went to the terminal and ssh to the instance and tried to see the tsm status and is not installed:

So I went to the opt directory to see the tableau directory but found only the aws folder.

Don't know what is going on. Seems thtat everything is created but Tableau is not installed

Thanks in advance

Hi I am following the setup for CF Centos,

It takes some time and it fails with the following

Value (TableauServerInstanceProfile) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterValue; Request ID: ; Proxy: null)

AFAIK I have given IAM permissions. Any ideas what might be happening?

The server license key is missing a preceding -k so when you run this script it incorrectly thinks that the license key is the package file:

Package file <license key> not found. Canceling.
Provide the package file (rpm or deb) as last argument.

Tableau Single-Server (Ubuntu) Cloudformation template fails when associating the running instance with an elastic IP:

You must specify an allocation id when mapping an address to a VPC instance (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 72deff9b-df66-454a-91e4-8213b3e55813)

Last year I opened an issue with stack creation failing with interactor license types and this was fixed by using --role all-jobs(Line 736-738). Now using all-jobs results in Primary Server Failed to create, changing jobs to no-flow now gets past Primary Server creation, but fails on worker creation. See below screenshot, if anyone is running into similar issues, help would be much appreciated.

Since that solution is most likely going to be used with data hosted on AWS, it would make sense to have support for Athena out of the box.

I finally got the installation working on Linux and I'm at 2018.1.1 (20181.18.0510.1418). I'd like to upgrade to the latest release and Tableau is telling me that the quickstart can't be upgraded, which makes it useless for anything but a trial installation. Is this correct?

The AWS Quickstart version of Tableau Server is designed to provide a quick way to stand up a Tableau Server for evaluation or proof of concept.
 
It cannot be upgraded.
 
The vast majority of our customers (if not all) running Tableau Server on AWS configure the AWS OS environment, install Tableau Server and apply an appropriate license for the server

HI Guys,

Can I please confirm if the function in the Linux stack the worker script calls:
"send_singal_to_topologyWaitHandle() {", "# Signal successful completion", { "Fn::Sub": "/opt/aws/bin/cfn-signal -e $? '${TopologyWaitHandle}'" }, "}", "set_topology", "unset -f set_topology", "trap send_singal_to_topologyWaitHandle EXIT"

is meant to be send_singal_to_topologyWaitHandle

or send_signal_to_topologyWaitHandle

thanks!

We are getting this error on AWS Centos. we created a brand new VPC.

You must specify an allocation id when mapping an address to a VPC instance (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: ****

Sounds like Postgres 12+ is not supported until version 2020.4. Are there plans to add this?

Hi.

The option to install a standalone server on Linux appears to be described incorrectly both on github and at amazon.com. It's described only as deploying the stack into the default VPC, but it created a new VPC for me. I'm happy to be up and running so it was not a problem, but I wonder if either the guides are out of date (i.e., referring to tableau-single-server.template instead of tableau-cluster-linux-master.template), or my architecture somehow presents an unusual condition that leads to a new VPC. Since tableau-cluster-linux-master.template invokes aws-vpc.template but tableau-single-server.template does not, the creation of a new VPC looks like the expected result.

Here's what I did:

1. On the Tableau quickstart page, select "How to deploy" then "Deploy a standalone Tableau Server environment (uses your default VPC)" option.
2. Change the region, use Ubuntu, add the CIDR of my office, choose user IDs for tsm admin and ts admin, set the instance type to m4.2xlarge.
3. Go.

Result: CloudFormation is successful. Output includes server URLs and VPC ID. VPC dashboard shows a new, non-default VPC with all its tags set by CloudFormation. The stack launched only one new instance, confirming that this is the standalone option.

Using tableau-cluster-linux.template. Primary server starts OK. When Worker Servers start up, it ends up failing with a WaitCondition timed out.

Looked in the /var/log/cloud-init-output.log and found an Operation failed message. Below is the end of the file. Worker is Ubuntu

Creating environment file...
Calling node installer...
log function temporarily off when processing password
Operation failed.
An error occurred during installation.
The server must be initialized before using this feature.
ERROR: installer returned status InternalError
+ unset -f install
+ /opt/aws/bin/cfn-signal -e 0 'https://cloudformation-waitcondition-us-east-2.s3.us-east-2.amazonaws.com/arn%3Aaws%3Acloudformation%3Aus-east-2%3A794232612963%3Astack/tableau-cluster/254baaa0-14db-11e9-a3f8-06413d85a3ea/WorkerWaitHandle?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20190110T132511Z&X-Amz-SignedHeaders=host&X-Amz-Expires=86399&X-Amz-Credential=AKIAI722P7Q4X76EQLQA%2F20190110%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Signature=4f4df4ea5f30ce8c56d454824260318fd567aa012fc2a7b4347a7f574ef20525'
CloudFormation signaled successfully with SUCCESS.
+ rm -f /tmp/secrets.properties
+ rm -f /tmp/tableau-server.deb
+ rm -f /tmp/automated-installer
Cloud-init v. 18.4-0ubuntu1~16.04.2 running 'modules:final' at Thu, 10 Jan 2019 13:33:07 +0000. Up 39.04 seconds.
Cloud-init v. 18.4-0ubuntu1~16.04.2 finished at Thu, 10 Jan 2019 13:36:06 +0000. Datasource DataSourceEc2Local.  Up 218.17 seconds

Hi All,

I'm using the Tableau Quick Start template for Ubuntu Single Server (https://github.com/aws-quickstart/quickstart-tableau-server/blob/main/templates/tableau-single-server-ubuntu.template). Kindly provide some feedback

When I try to create the server from the cloud formation template I get the below error:

I am trying to deploy tableau cluster linux and get error

All cloudformation scripts are currently hardcoded for AWS Commercial cloud. Please allow the functionality to support aws-us-gov ARNs instead of just aws.

The solution seems to be inconsistent when changing the instance type, can you provide a way of logging what is causing the stack update fails to change instance type to m5.2xlarge
is there a specific hardware requirement /software requirement on linux to be used as a reference ?
with m5.large after receiving a failure signal in cloudformation, trying the script manually results in error of installation due to insufficient memory and hardware requirements

when updating the stack and change instance type to m5.2xlarge it fails to update like this :
"Parameter InstanceType failed to satisfy constraint: must be a valid EC2 instance type."

It is not customary to specify the state for my office address, only the postal code. Leaving the state parameter blank causes the installation to fail and the CloudFormation stack to rollback. Also, having access to the Tableau Server installation logs would have made debugging this issue a lot simpler.

On Windows (not tested on CentOS/Ubuntu), current installed version is 2019.2.0, latest is 2019.2.3.

How do I fix this error? I have disabled automatic rollback and can get to the instance, but why I am getting this error?

Embedded stack arn:aws:cloudformation:us-east-2:accountid:stack/Tableau-Server-WorkloadStack was not successfully created: The following resource(s) failed to create: [TableauServer].

From the "nested" script:

On first invocation of the single server linux stack, the nested stack invocation rolled back, resulting in a failure of the parent stack. On investigation we found in the cloudformation logs:

As part of our investigation our experience was that this warning message only appears the first time the stack invocation is attempted - we had to recover this info from the list of deleted stacks in cloudformation. As far as we observed, https://aws-quickstart.s3.amazonaws.com/quickstart-tableau-server/doc/tableau-server-on-the-aws-cloud.pdf does not capture this point.

After multiple tries, with VPC creation and without, eu-west-3 can't work with this template.

Since Ubuntu 16.04 is nearing the end of its maintenance window (April 2021), is there interest in making Ubuntu 18.04 an allowed AMIOS? Do we anticipate this would require many changes to the installation pathway?

Issue: CF build fails on timeout because CF isn't notified of completion by the cfn-signal. cfn function aren't properly installed

I've modified my template from before this issue - so it's possible this isn't an issue in main. But with the deprecation of easy_install, my server wouldn't build. I replaced the easy_install line with the following code and updated the path to cfn functions as a workaround:

#this from https://aws.amazon.com/blogs/infrastructure-and-automation/introduction-to-quickstart-linux-utilities/ as an alternative to easy_install which is apparently deprecated
            until git clone https://github.com/aws-quickstart/quickstart-linux-utilities.git; do echo "Retrying"; done
            cd /quickstart-linux-utilities
            source quickstart-cfn-tools.source
            qs_update-os || qs_err
            qs_bootstrap_pip || qs_err
            qs_aws-cfn-bootstrap || qs_err

#now cfn functions at here: /usr/local/bin/cfn-init 
#remove easy_install reference 
#/usr/bin/easy_install --script-dir /opt/aws/bin https://s3.amazonaws.com/cloudformation-examples/aws-cfn-bootstrap-latest.tar.gz 
            #/opt/aws/bin/cfn-init --stack ${AWS::StackName} --resource TableauServer --region ${AWS::Region}
            
#replace cfn-init references (though this may not be necessary because it's on the path

            /usr/local/bin/cfn-init --stack ${AWS::StackName} --resource TableauServer --region ${AWS::Region}
            # Various machine configs
            hostnamectl set-hostname $(hostnamectl --static)
            echo "before call sftp" >> /tmp/logging.txt
            setup_sftp() {
                source '/tmp/secrets.properties'
                useradd -m "$tsm_admin_user"
                echo -e "$tsm_admin_pass\n$tsm_admin_pass" | passwd "$tsm_admin_user"

            }

I am totally new Cloudformation world, I am trying to run the Cloudformation template (tableau-single-server-master.template) . Once I change the region to Bahrain (me-south-1) and run it, I get the error:
Unable to get mapping for AWSAMIRegionMap::me-south-1::WS2012R2
,notice that the template is based on Oregon. Also when I validate the template before running it, I got the error: Template contains errors.: Template error: every Fn::GetAtt object requires two non-empty parameters, the resource name and the resource attribute
Please help me sorting this out.

Hi,
When I use the CFT for a windows cluster I receive the following error ~ 4 minutes into the build:
Template error: Mapping named 'AWSAMIRegionMap' is not present in the 'Mappings' section of template.

I've performed the following:

• Re-read the PDF to ensure I wasn't missing any of the required fields
• Changed up a few of the variables, like the bucket name, availability zones selected, etc.
• Saw that the template does not reference the latest AMI for W2012 R2 and so updated that value for the region I'm building in
• Looked for naming inconsistencies in the template for 'Mappings' and 'AWSAMIRegionMap'

Is this error misleading or is there genuinely an issue in the Mappings section?

Would be great to see support for the

NVMe Enabled SSD EC2 the m5[a]d.4xlarge.* series.
Based on some research about tableau server performance I would expect this to be an option with potential performance gains.

http://russellchristopher.me/ec2/index.html

1. Title

AMIs in tableau-single-server-windows.template are deprecated and need update AMI IDs.

2. Description

Stack creation in us-east-1 results in "API: ec2:RunInstances Not authorized for images: [ami-094a644f1fb9e4ce3]"
Windows_Server-2012-R2_RTM-English-64Bit-Base-2019.07.12 has been deprecated.

When changing the instance type with less hardware than required instance send a failure signal , part of the userdata script failed to finish ( apparently no logs to point to that in cloud-init).

Is it possible to enable those logs in the solution so that customers does not have to modify the userdata scripts in the template or maybe modify the tableau installation commands to log installation errors.

The issue was CFN was receiving a failure signal due to incomplete installation but cloud-init and cfn-init had no details about the failure.

An error occurred during installation.
java.net.UnknownHostException: ip-10-75-193-145: ip-10-75-193-145: Name or service not known
ERROR: TSM services returned status 10

After my Cloud Formation stack got deployed, I was checking the Tableau IAM role policies for AmazonEC2RoleforSSM and I noticed this:

Description	This policy will soon be deprecated. Please use AmazonSSMManagedInstanceCore policy to enable AWS Systems Manager service core functionality on EC2 instances. For more information see https://docs.aws.amazon.com/systems-manager/latest/userguide/setup-instance-profile.html

I'll try to run a copy of this template with AmazonSSMManagedInstanceCore IAM role policy. If everything works smoothly and I have time then I'll send a pull-request.

Thanks!

The following resource(s) failed to create: [BastionAutoScalingGroup].

BastionAutoScalingGroup CREATE_FAILED Received 1 FAILURE signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement

log from bastionHost:-

grep -ni 'error|failure' $(sudo find /var/log -name cfn* -or -name cloud-init*) /var/log/cloud-init.log:458:Apr 22 08:19:08 cloud-init[3012]: main.py[DEBUG]: Ran 13 modules with 0 failures /var/log/cloud-init.log:560:Apr 22 08:19:19 cloud-init[3208]: main.py[DEBUG]: Ran 10 modules with 0 failures /var/log/cloud-init.log:594:ProcessExecutionError: Unexpected error while running command. /var/log/cloud-init.log:615:RuntimeError: Runparts: 1 failures in 1 attempted commands /var/log/cloud-init.log:651:Apr 22 08:20:09 cloud-init[3415]: main.py[DEBUG]: Ran 9 modules with 1 failures /var/log/cloud-init-output.log:212:--> Processing Dependency: perl(Error) for package: perl-Git-2.23.1-1.amzn2.0.2.noarch /var/log/cloud-init-output.log:215:---> Package perl-Error.noarch 1:0.17020-2.amzn2 will be installed /var/log/cloud-init-output.log:230: perl-Error noarch 1:0.17020-2.amzn2 amzn2-core 32 k /var/log/cloud-init-output.log:249: Installing : 1:perl-Error-0.17020-2.amzn2.noarch 3/8 /var/log/cloud-init-output.log:261: Verifying : 1:perl-Error-0.17020-2.amzn2.noarch 7/8 /var/log/cloud-init-output.log:272: perl-Error.noarch 1:0.17020-2.amzn2 /var/log/cloud-init-output.log:842:Error occurred during build: Command b-bootstrap failed /var/log/cfn-init.log:20:2020-04-22 08:20:08,653 [ERROR] Command b-bootstrap (./bastion_bootstrap.sh --banner https://aws-quickstart.s3.us-east-1.amazonaws.com/quickstart-linux-bastion/scripts/banner_message.txt --enable false --tcp-forwarding false --x11-forwarding false) failed /var/log/cfn-init.log:35:2020-04-22 08:20:08,654 [ERROR] Error encountered during build of config: Command b-bootstrap failed /var/log/cfn-init.log:42: raise ToolError(u"Command %s failed" % name) /var/log/cfn-init.log:43:ToolError: Command b-bootstrap failed /var/log/cfn-init.log:44:2020-04-22 08:20:08,656 [ERROR] -----------------------BUILD FAILED!------------------------ /var/log/cfn-init.log:45:2020-04-22 08:20:08,660 [ERROR] Unhandled exception during build: Command b-bootstrap failed /var/log/cfn-init.log:58: raise ToolError(u"Command %s failed" % name) /var/log/cfn-init.log:59:ToolError: Command b-bootstrap failed /var/log/cfn-init.log:61:2020-04-22 08:20:08,882 [DEBUG] Signaling resource BastionAutoScalingGroup in stack Tableau-ubuntu-BastionHost-1FMT6T80AVICN with unique ID i-0ba02ad1171cdc569 and status FAILURE /var/log/cfn-wire.log:3:2020-04-22 08:20:08,938 [DEBUG] Response: 200 https://cloudformation.us-east-2.amazonaws.com/?Status=FAILURE&ContentType=JSON&StackName=Tableau-ubuntu-BastionHost-1FMT6T80AVICN&Version=2010-05-15&UniqueId=i-0ba02ad1171cdc569&Action=SignalResource&LogicalResourceId=BastionAutoScalingGroup [headers: {'x-amzn-requestid': '9a5ea98d-c6bb-49c9-a6d1-0b663848c9f3', 'date': 'Wed, 22 Apr 2020 08:20:08 GMT', 'content-length': '100', 'content-type': 'application/json'}] /var/log/cfn-init-cmd.log:23:2020-04-22 08:20:08,653 P12339 [ERROR] Exited with error code 6

logs from primary:-

grep -ni 'error|failure' $(sudo find /var/log -name cfn* -or -name cloud-init*) /var/log/cloud-init-output.log:2099:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2113:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2127:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2141:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2155:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2169:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2183:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2197:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2211:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2225:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2239:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2254:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2268:There are 1 topology validation errors/warnings. /var/log/cloud-init-output.log:2281:There are 2 topology validation errors/warnings. /var/log/cloud-init-output.log:2305:There are 3 topology validation errors/warnings. /var/log/cloud-init-output.log:2475:There are 3 topology validation errors/warnings. /var/log/cloud-init-output.log:2485:Error: This configuration is invalid. Configuring Backgrounder node roles for /var/log/cloud-init-output.log:2496:Error: This configuration is invalid. Configuring Backgrounder node roles for /var/log/cloud-init.log:856:2020-04-22 08:18:10,148 - main.py[DEBUG]: Ran 15 modules with 0 failures /var/log/cloud-init.log:981:2020-04-22 08:18:23,213 - main.py[DEBUG]: Ran 14 modules with 0 failures /var/log/cloud-init.log:1078:cloudinit.util.ProcessExecutionError: Unexpected error while running command. /var/log/cloud-init.log:1105:RuntimeError: Runparts: 1 failures in 1 attempted commands /var/log/cloud-init.log:1141:2020-04-22 08:39:47,298 - main.py[DEBUG]: Ran 20 modules with 1 failures

The stack uses the deprecated classic load balancer rather than the modern ALB. Can it be modernized to get the features such as WAF support that ALB has that classic LB doesn't?

Auto Scaling Group: Tableau-Server-WorkloadStack-1QWKC4SWJS1JU-WorkerGroup-XFN9F9PBBPYR
ELB: Tableau-S-ServerLo-1VBKW2Z3UJDTW

I deleted the ELB and replaced with an ALB outside of cloud-formation in my environment after running the stack, but I'm pretty sure there is a reference in the ASG to the ELB so I probably broke the ASG setup.

customer would like to be able to use 2 AZs instead of 3 and have the load balancer in a private subnet , customer wants the solution to allow such customization.

Deployment of Tableau Cluster in the New VPC failed with the Topology Wait condition

AWS Support ticket raised and they are able to resolve the issue. Please update the template from your and confirm.

The issue was with the QuickStart template provided by Tableau where the TopologyWaitHandle was unable to receive the success signal from the PrimarySever resource

Here is the changes made to the template:

The TopologyWaitCondition resource is created after the PrimaryServer has created successfully.
In that case, since the PrimaryServer resource has already sent a success signal, the TopologyWaitCondition resource is waiting for an already received signal.
In the UserData section, there is no cfn-signal being sent to the TopologyWaitHandle resource.
Added the cfn-signal for the TopologyWaitHandle resource in the UserData section
There is the cfn-signal command in the /tmp/workers.sh file in the Init section but the .sh script never gets called and thus the TopologyWaitHandle resource does not receive the success signal.

Hi,
I was Deploying Tableau Server into a new VPC but it was not showing the parameters to provide Private Subnet details and the deployment was failing with error below (which was showing the default IP in the error). Then I had to dig in and add the parameters in this definition file for it to work.

I am new to cloud formation so not sure if it was something other way around and I missed to look at it in right way. Correct me if I was wrong.

ERROR

Thanks,
Libin Tom

When creating a new CloudFormation stack based on tableau-single-server-main.template.yaml, execution fails.

Error message:

Embedded stack arn:aws:cloudformation:us-west-2:128489674626:stack/Tableau-Server-TableauStack-PLY7E4U0P251/a7364520-4fb5-11ed-8f10-06e58235caa5 was not successfully created: The following resource(s) failed to create: [TableauServer].

I chose Linux as OS.

S3 error: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. For more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html

The following resource(s) failed to create: [Infrastructure].

I am attempting to create this within eu-west-2, however I believe it is having trouble accessing the infrastructure S3 resources with the default configuration.

I am hoping I have just missed a simple step.

Stack failed to create with the following error. Is this an error in execution or something I can fix on my side? Not sure what it means and the substack with details gets deleted.

Embedded stack arn:aws:cloudformation:us-east-1:564062160093:stack/Tableau-Server-WorkloadStack-1RV8H8I72BC99/0133b5a0-94ce-11e8-9b56-503aca261699 was not successfully created: The following resource(s) failed to create: [ServerLoadBalancer, WorkerWaitCondition, IPAssoc].

I would propose using the Security Group of the Load Balancer for traffic (80 & 443) between the LB and the Worker Servers, then the Security Group of the Servers for intra-server traffic (0-65535). I would also remove Port 22 as these servers are on a Private subnet.

This caused me an issue because I use different subnets for our Public vs Private subnets within the same VPC.

I will attach an updated version of tableau-cluster-linux.template as a suggestion when I am done testing.