Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Services stack failed #223

Open
sebastianalfaro opened this issue May 16, 2023 · 2 comments
Open

Services stack failed #223

sebastianalfaro opened this issue May 16, 2023 · 2 comments

Comments

@sebastianalfaro
Copy link

Hello,

I am using a fresh AWS account with full IAM admin permissions. After getting to resource 188/198, the stack fails to create the following resources. Following the One Observability Workshop here https://catalog.workshops.aws/observability/en-US/installation/not-using-ee/deploy-app

5:22:21 AM | CREATE_FAILED | Custom::AWSCDK-EKS-KubernetesResource | xraydeployment/Resource/Default
Received response status [FAILED] from custom resource. Message returned: AccessDeniedException: Resource is not in the state functionActive
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:61:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:688:12) (RequestId: c1d0cf25-d230-418e-a8a5-f873027682e7)

5:22:21 AM | CREATE_FAILED | Custom::AWSCDK-EKS-KubernetesResource | petsite/AwsAuth/ma...t/Resource/Default
Received response status [FAILED] from custom resource. Message returned: AccessDeniedException: Resource is not in the state functionActive
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:61:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:688:12) (RequestId: b90f105e-3086-4eba-9c15-935e1347ec26)

5:22:21 AM | CREATE_FAILED | Custom::AWSCDK-EKS-KubernetesResource | ssmAgentdeployment/Resource/Default
Received response status [FAILED] from custom resource. Message returned: AccessDeniedException: Resource is not in the state functionActive
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:52:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:61:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
^[c

Any assistant would be appreciated!

@weklund
Copy link

weklund commented Jun 6, 2023

I'm getting the same error. Brand new account with admin permissions.

It's on the LoadBalancer CRD resource

@AWS-Joe-A
Copy link

Hello @weklund @sebastianalfaro ,
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 code.

Can you confirm if you are still seeing this issue?

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

No branches or pull requests

3 participants