Stack update fails on unchanged Timestream Table in CD

0

I have a CDK stack that contains a Timestream Database with a Timestream Table. There has been no changes to these since they were originally deployed.

When running the deployment locally, everything goes smoothly for both of the two accounts we have this stack in.

However, the CI/CD system is not allowed to deploy. It fails the same way for both accounts:

UPDATE_FAILED        | AWS::Timestream::Table    | <table name in stack> (<table name>) Resource handler returned message: "null" (RequestToken: 73f0b0b6-fee5-dba2-355f-d85a235942df, HandlerErrorCode: InternalFailure)

There is no error in CloudTrail. The only two visible events related to this are a CreateChangeSet and an ExecuteChangeSet. None of these show any errors.

I have checked the deployment template in S3. The template from the local deploy contains the RetentionProperties while the one from the CI/CD-deploy does not. The CDK defines these explicitly.

The Role used by the CI/CD system has these premissions on "*":

                  'timestream:DescribeDatabase',
                  'timestream:DescribeEndpoints',
                  'timestream:DescribeScheduledQuery',
                  'timestream:DescribeTable',
                  'timestream:ListDatabases',
                  'timestream:ListMeasures',
                  'timestream:ListTables',
                  'timestream:UpdateDatabase',
                  'timestream:UpdateTable',
                  'timestream:UpdateDatabase',
                  'timestream:UpdateTable'

I have tried giving the deployment role all rights with 'timestream:*' and the result is the same.

Knut
posta un anno fa217 visualizzazioni
1 Risposta
0
Risposta accettata

So I found out what is happening. It is CDK that has a bug with RetentionProperties. I used a cdk version prior to 2.55 locally while we alway try to use the most recent version in the CI/CD system. In this case that is 2.55.1. The issue also present in 2.55.

The bug has been reported so it should hopefully be fixed in the not too distant future: https://github.com/aws/aws-cdk/issues/23404

Knut
con risposta un anno fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande