@<1523701070390366208:profile|CostlyOstrich36>
ok from what im seeing, for some reason my the updated credentials don't get to the actual task, when i spin up the task and go to the configurations tab in the webserver, it shows an old key and secret. any idea why this is happening?
Hi @<1612982606469533696:profile|ZealousFlamingo93> , how exactly are you running the autoscaler?
Is this what you're running?
None
@<1523701070390366208:profile|CostlyOstrich36>
hey john,
yeah this is what i'm running, im running it on a local machine (where the web server is also running if thats relevant), the aws credentials i've given it are with an IAM role that gives access to EC2:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"ec2:DescribeInstances",
"ec2:TerminateInstances",
"ec2:RequestSpotInstances",
"ec2:DeleteTags",
"ec2:CreateTags",
"ec2:RunInstances",
"ec2:DescribeSpotInstanceRequests",
"ec2:GetConsoleOutput"
],
"Resource": "*"
}
]
}
along with S3 access, then i put the key and secret into the autoscaler.yaml so it can run