-
Notifications
You must be signed in to change notification settings - Fork 9
Description
根据https://github.com/aws-samples/solution-for-deploying-dify-on-aws/tree/1.0.0安装,
cdk synth没有执行,cdk bootstrap之后,删掉CDKToolkit,再cdk synth,cdk bootstrap,命令之后报错:
Selected cache node type: cache.m7g.large
EKS Using instance type: m8g.large
⏳ Bootstrapping environment aws://526372922310/us-east-2...
Trusted accounts for deployment: (none)
Trusted accounts for lookup: (none)
Using default execution policy of 'arn:aws:iam::aws:policy/AdministratorAccess'. Pass '--cloudformation-execution-policies' to customize.
CDKToolkit: creating CloudFormation changeset...
3:51:54 AM | CREATE_FAILED | AWS::S3::Bucket | StagingBucket
Resource handler returned message: "cdk-hnb659fds-assets-526372922310-us-east-2 already exists (Service: S3, Status Code: 0, Request ID: null)" (RequestToken: 558acdca-32a1-14c1-4159-d3583a347929, HandlerErrorCode: AlreadyExists)
❌ Environment aws://526372922310/us-east-2 failed bootstrapping: ToolkitError: The stack named CDKToolkit failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Resource handler returned message: "cdk-hnb659fds-assets-526372922310-us-east-2 already exists (Service: S3, Status Code: 0, Request ID: null)" (RequestToken: 558acdca-32a1-14c1-4159-d3583a347929, HandlerErrorCode: AlreadyExists)
at FullCloudFormationDeployment.monitorDeployment (/usr/lib/nodejs18/lib/node_modules/aws-cdk/lib/index.js:152075:17)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async _BootstrapStack.update (/usr/lib/nodejs18/lib/node_modules/aws-cdk/lib/index.js:153717:21)
at async /usr/lib/nodejs18/lib/node_modules/aws-cdk/lib/index.js:344527:29 {
type: 'toolkit',
source: 'toolkit',
cause: undefined
}
NOTICES (What's this? https://github.com/aws/aws-cdk/wiki/CLI-Notices)
34892 CDK CLI will collect telemetry data on command usage starting at version 2.1100.0 (unless opted out)
Overview: We do not collect customer content and we anonymize the
telemetry we do collect. See the attached issue for more
information on what data is collected, why, and how to
opt-out. Telemetry will NOT be collected for any CDK CLI
version prior to version 2.1100.0 - regardless of
opt-in/out. You can also preview the telemetry we will start
collecting by logging it to a local file, by adding
`--unstable=telemetry --telemetry-file=my/local/file` to any
`cdk` command.
Affected versions: cli: ^2.0.0
More information at: https://github.com/aws/aws-cdk/issues/34892
34739 (opensearch): As of CDK release v2.201.0, OpenSearch domain TLSSecurityPolicy defaults to TLS 1.2
Overview: As of CDK release v2.201.0, the default TLSSecurityPolicy
for OpenSearch domains is Policy-Min-TLS-1-2-2019-07 (TLS
1.2). The previous default was Policy-Min-TLS-1-0-2019-07
(TLS 1.0).
Affected versions: aws-cdk-lib.aws_opensearchservice.Domain: >=2.0.0 <=2.210.0
More information at: https://github.com/aws/aws-cdk/issues/34739
If you don’t want to see a notice anymore, use "cdk acknowledge ". For example, "cdk acknowledge 34892".
The stack named CDKToolkit failed creation, it may need to be manually deleted from the AWS console: ROLLBACK_COMPLETE: Resource handler returned message: "cdk-hnb659fds-assets-526372922310-us-east-2 already exists (Service: S3, Status Code: 0, Request ID: null)" (RequestToken: 558acdca-32a1-14c1-4159-d3583a347929, HandlerErrorCode: AlreadyExists)
