-
Notifications
You must be signed in to change notification settings - Fork 4k
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
aws-cdk-lib/aws-eks: waiter-state-machine is not authorized to access the Log Destination #33332
Comments
Hi We are still working on the 1.32 support in #33339 and we can't guarantee if 1.32 is working now before that PR is merged. Are you able to simplify your code and see if 1.31 is working? For example import * as ec2 from 'aws-cdk-lib/aws-ec2';
import * as iam from 'aws-cdk-lib/aws-iam';
import { App, Stack, StackProps } from 'aws-cdk-lib';
import { KubectlV31Layer } from '@aws-cdk/lambda-layer-kubectl-v31';
import * as eks from 'aws-cdk-lib/aws-eks';
import { Construct } from 'constructs';
export class EksClusterLatestVersion extends Stack {
constructor(scope: Construct, id: string, props: StackProps) {
super(scope, id, props);
const vpc = new ec2.Vpc(this, 'Vpc', { natGateways: 1 });
const mastersRole = new iam.Role(this, 'Role', {
assumedBy: new iam.AccountRootPrincipal(),
});
new eks.Cluster(this, 'Cluster', {
vpc,
mastersRole,
version: eks.KubernetesVersion.V1_31,
kubectlLayer: new KubectlV31Layer(this, 'KubectlLayer'),
defaultCapacity: 1,
});
}
}
const app = new App();
new EksClusterLatestVersion(app, 'v31-stack', {
env: {
account: process.env.CDK_DEFAULT_ACCOUNT,
region: process.env.CDK_DEFAULT_REGION,
},
}) |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Hi ! Thanks for your answer ! I tried the provided code (modified it slightly to use an existing VPC because the account reached its quota), updated the package JSON to use Kubernetes 1.31. I still get the same error:
|
Describe the bug
Hello !
I am trying to create a cluster in an AWS Account I have admin permissions on.
The creation fails when a Provider I have no control on fails:
How can I fix this as it seems to be out of my scope ?
Regression Issue
Last Known Working CDK Version
No response
Expected Behavior
EKS cluster is created without error.
Current Behavior
The creation fails when a Provider I have no control on fails:
Reproduction Steps
I have the following package.json:
And here is a kind of simplified version of my Stack
Portion of the generated template:
Possible Solution
No response
Additional Information/Context
I saw people say that the resource policies for logs have a limited size but I am not sure if that is the issue as the logs are in
/aws/vendedlogs/states/
:aws logs describe-resource-policies | wc 54 85 4575
CDK CLI Version
2.178.1 (build ae342cb)
Framework Version
No response
Node.js Version
v22.11.0
OS
macOS Version 15.2 (24C101)
Language
TypeScript
Language Version
5.6.3
Other information
No response
The text was updated successfully, but these errors were encountered: