Erik Robertson
03/20/2022, 8:16 PMAccessDenied: User: arn:aws:sts::XXX:assumed-role/cdk-hnb659fds-deploy-role-XXX-us-west-2/aws-cdk-erik is not authorized to perform: iam:PassRole on resource: arn:aws:iam::XXX:role/DWAM-STAGING-SST-CloudFormation-Role because no identity-based policy allows the iam:PassRole action
I then manually added the passRole to the SST created cdk-hnb659fds-deploy-role-XXX-us-west-2 and things worked.
I believe SST should be adding that permission automatically when creating that role.Matt Morgan
03/20/2022, 10:45 PMFunction
intercept console.log statements and prevent them from going to CloudWatch?Artemiy Davydov
03/21/2022, 10:21 AMArtemiy Davydov
03/21/2022, 10:26 AMRoss Coundon
03/22/2022, 4:37 PMsst build
i.e. just do all the deploy parts and not the build parts?Richard Simpson
03/23/2022, 4:40 PMAdrián Mouly
03/23/2022, 7:46 PMRoger Rajaratnam
03/24/2022, 4:29 PMRoss Coundon
03/24/2022, 7:54 PMaccessLog: true
in the API definition in my stack but the console shows:Brinsley
03/26/2022, 8:06 AMEventBus
construct Using the entirety of the RuleProps
interface from CDK:
new EventBus(this, "scheduler", {
rules: {
rule1: {
targets: ["path/to/file.handler"],
schedule: Schedule.cron({ minute: "1" })
}
}
})
Gives the error:
Cannot associate rule with 'eventBus' when using 'schedule'
Might want to look through what's compatible and what's being omitted on EventBusCdkRuleProps
Derek Kershner
03/26/2022, 4:28 PMapollo-server-errors
work out of the box (because apollo
uses graphql.js). ESM now works, and my package size dropped by ~1.8MB, which made cold starts about half as long.
Happy to share more if it is interesting.Akos
03/28/2022, 2:45 PMthdxr
03/28/2022, 4:47 PMBlockPublicAccesError
in thereMischa Spiegelmock
03/29/2022, 8:07 AMAdrián Mouly
03/29/2022, 3:06 PMsst test
to execute some tests… I want to validate my resources name, but looks like when I use scope.stage
, the value is mapped to dev
… why is that? is that possible to be changed to something like test
?Aaron Eaton
03/29/2022, 3:32 PM--stage test
fix that?Harris Newsteder
03/30/2022, 11:20 AMHarris Newsteder
03/30/2022, 11:37 AMHarris Newsteder
03/30/2022, 12:57 PMJason
03/30/2022, 1:13 PMreportBatchItemFailures
set to true, and my return from the lambda is
{
batchItemFailures: [ { itemIdentifier: 'd6d84d1b-a232-46f8-822d-bc4b232c5a45' } ]
}
So I would expect it to be retried after the visibility timeout, not deleted. But it's not being retried, and when I check the monitoring tab it shows that the message was deleted.
Queue definition:
new sst.Queue(this, 'name', {
sqsQueue: {
retentionPeriod: Duration.days(14),
visibilityTimeout: Duration.seconds(30),
deadLetterQueue: {
queue: deadLetterQueue.sqsQueue,
maxReceiveCount: 8,
},
},
consumer: {
deadLetterQueueEnabled: true,
handler: 'src/services/svc.handler',
timeout: 5,
memorySize: 8192,
consumerProps: { reportBatchItemFailures: true, batchSize: 5 },
},
});
Handler:
export const handler = async (event: SQSEvent) => {
const failedIds = await run(event);
const response = {
batchItemFailures: failedIds.map((id) => {
return {
itemIdentifier: id,
};
}),
};
console.log('Response: ', response);
return response;
};
Anything I could be missing?Slackbot
03/30/2022, 2:36 PMHarris Newsteder
03/30/2022, 9:24 PMMichael Robellard
03/30/2022, 10:23 PMMischa Spiegelmock
03/31/2022, 7:54 PMcdk.context.json
?Harris Newsteder
03/31/2022, 8:12 PMHarris Newsteder
03/31/2022, 9:05 PMHarris Newsteder
03/31/2022, 9:51 PMSelo
04/03/2022, 5:14 PMTyler Renelle
04/03/2022, 5:32 PMRoger Rajaratnam
04/04/2022, 4:30 PM