Skip to content
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.

bug: Upstream Quickstart CFT Inaccessible #13

Open
mbeacom opened this issue Nov 15, 2023 · 1 comment
Open

bug: Upstream Quickstart CFT Inaccessible #13

mbeacom opened this issue Nov 15, 2023 · 1 comment

Comments

@mbeacom
Copy link

mbeacom commented Nov 15, 2023

It appears the CFT used to stamp out the NR stackset is (similarly to the rest of the experience so far) not usable either since it's inaccessible.

create: failed to create CloudFormation stack, rollback requested (ROLLBACK_COMPLETE): ["The following resource(s) failed to create: [NewRelicControlTowerEvents, NewRelicFirstLaunch]. Rollback requested by user." "Resource creation cancelled" "Received response status [FAILED] from custom resource. Message returned: An error occurred (ValidationError) when calling the CreateStackSet operation: Object referenced by https://aws-quickstart.s3.amazonaws.com/quickstart-ct-newrelic-one/templates/newrelic-stack-set.yml is not accessible.

@mbeacom mbeacom changed the title Upstream Quickstart CFT Inaccessible bug: Upstream Quickstart CFT Inaccessible Nov 15, 2023
@netcrazed
Copy link

A potential workaround has been identified which is to create the StackSet manually using the URL mentioned in the error message. The name of the StackSet with the manual deploy must be the same as the value as the StackSetName parameter name. This stack set has a few other parameters which do not have defaults which their values can be pulled from the quickstart.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants