[deployment fails]

[psantus]

On a clean account, deployment fails, with the Services CloudFormation stack failing on on resource logical ID: loadBalancerServiceAccount1D19AD3A

Received response status [FAILED] from custom resource. Message returned: TimeoutError: {"state":"TIMEOUT","reason":"Waiter has timed out"} at checkExceptions (/var/runtime/node_modules/@aws-sdk/node_modules/@smithy/util-waiter/dist-cjs/index.js:59:26) at waitUntilFunctionActiveV2 (/var/runtime/node_modules/@aws-sdk/client-lambda/dist-cjs/index.js:5820:49) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async defaultInvokeFunction (/var/task/outbound.js:1:1024) at async invokeUserFunction (/var/task/framework.js:1:2794) at async onEvent (/var/task/framework.js:1:369) at async Runtime.handler (/var/task/cfn-response.js:1:1837) (RequestId: b7764054-fe42-40fc-bf8e-8096cbde4b65)

[AWS-Joe-A]

Hello @psantus,
Thank you for your patience. I have recently on-boarded to the team and I'm following up with issues for this project.
I was able to successfully deploy the current version of the code.

Could you confirm if you're still seeing this issue?
I may need more details if so.

[psantus]

Could you do that on a new account?
Now new accounts have default quotas lower than so called default quotas.

[psantus]

@AWS-Joe-A: adding a list of all the quotas request we need to make to get this deployment to work would be a satisfactory solution to this issue.

[AWS-Joe-A]

Hello @psantus,
Thank you for the feedback. I'm deploying a new account and will test again. I'll let you know what I find. Thank you!

[AWS-Joe-A]

Hello @psantus,
I created a new account and was able to successfully deploy the one-observability-demo. I ran through a few modules without issue.

Did any of the other stacks or nested stack have errors as well?

[psantus]

Issue was in one nested stack. I deployed in eu-west-1.

I'll try again and will let you know

[AWS-Joe-A]

I deployed in us-east-1 as I didn't se a region listed in the error message.
I will also attempt to deploy it in eu-west-1 now .

[AWS-Joe-A]

Hello @psantus,
I was able to deploy in eu-west-1 successfully in the new account as well. Please let me know what you find as well. Ty!

[psantus]

Hi @AWS-Joe-A

I appreciate your commitment and efforts to replicate. I just deployed in my account again and got 2 errors

in the Services stack

{"state":"TIMEOUT","reason":"Waiter has timed out"} at checkExceptions (/var/runtime/node_modules/@aws-sdk/node_modules/@smithy/util-waiter/dist-cjs/index.js:59:26) at waitUntilFunctionActiveV2 (/var/runtime/node_modules/@aws-sdk/client-lambda/dist-cjs/index.js:5820:49) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async defaultInvokeFunction (/var/task/outbound.js:1:1024) at async invokeUserFunction (/var/task/framework.js:1:2794) at async onEvent (/var/task/framework.js:1:369) at async Runtime.handler (/var/task/cfn-response.js:1:1837) (RequestId: 7f698e42-ca06-48d6-b2b9-a5a3b5ddf9a0)

in the Observability-Workshop stack

WaitCondition received failed message: 'CodePipeline Deploy ended' for uniqueId: abd96809-8b7e-42fa-967f-d308a96f6f9b

[psantus]

@AWS-Joe-A what's your timezone?
I can be available today from 3PM to 5PM UTC if you want to have a look together on my deployment

[AWS-Joe-A]

Hello @psantus,
Thank you for your patience. I'm sorry we weren't able to connect earlier.
Let me reach out internally to see if I can identify someone closer to UTC time zone to work with you on this.
It may be difficult to find someone due to the holidays, but I'll do my best to find someone that could help.