sparse-intern-71089
03/25/2019, 8:43 PMbillions-lock-73409
03/25/2019, 8:43 PMconst startScanContainer = new aws.lambda.CallbackFunction(`secrets-start-scan-container-${env}`, {
role: lambdaRole,
callback: async (event, context, callback) => {
const AWS = require('aws-sdk');
const Octokit = require('@octokit/rest');
var ecs = new AWS.ECS();
var params = {
taskDefinition: scannerTask.taskDefinition.family,
cluster: cluster.cluster.arn,
launchType: 'FARGATE',
networkConfiguration: {
awsvpcConfiguration: {
subnets: [secretsVpc.privateSubnetIds],
assignPublicIp: 'DISABLED',
securityGroups: [secretsScannerSg.id],
},
},
};
await ecs.runTask(params).promise();
console.log('Scanner task has been started.');
callback(null, 'Hello');
},
});
billions-lock-73409
03/25/2019, 8:44 PMbillions-lock-73409
03/25/2019, 8:47 PM.get()
calls to the family and arn’s? Doesn’t seem that that would fix the issue with the privateSubnetIds
fieldbillions-lock-73409
03/25/2019, 9:11 PM{
"taskDefinition": {
"value": "secrets-scanner-dev-aece9bcd"
},
"cluster": {
"value": "arn:aws:ecs:us-east-1:*****:cluster/secrets-scanner-dev"
},
"launchType": "FARGATE",
"networkConfiguration": {
"awsvpcConfiguration": {
"subnets": [
{
"value": "subnet-010f54d482e6bbe5f"
},
{
"value": "subnet-0b2de25c26fdb6329"
}
],
"assignPublicIp": "DISABLED",
"securityGroups": [
{
"value": "sg-0a99aa39a8f32459f"
}
]
}
}
}
billions-lock-73409
03/25/2019, 9:12 PM