Can I update a Resource (Like Autoscalinggroup) in another Region using Node Lambda in a different Region?
0
Am trying to update an AutoScalingGroup in another Region via my Node Lambda deployed in us-east-1.
I've tried setting the region in AWS.AutoScaling() constructor. The CLI COMMAND line argument works fine from an EC2 Instance in us-east-1 by passing --region us-west-2 in the CLI to update the AutoscalingGroup in us-west-2.
But when I attempt the same in Lambda which is in us-east-1, I get a ValidationError : AutoscalingGroup name not found - null
var autoscalinggroup = new AWS.AutoScaling({'credentials': credentials, 'region' : 'us-west-2'});
var params = {
AutoScalingGroupName : 'converse-kibana-ecs-cluster-QA-Integration-Cluster-Container-1-0-8bint-5-ECSContainerAutoScalingGroup-18F80FECCOLH2',
MaxSize: 4,
MinSize: 2,
DesiredCapacity: 2
};
autoscalinggroup.updateAutoScalingGroup(params, function(err, data) {
if (err) {
console.log(err, err.stack);
}
else {
console.log(data);
}
});
amazon-web-services aws-lambda
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
add a comment |
0
Am trying to update an AutoScalingGroup in another Region via my Node Lambda deployed in us-east-1.
I've tried setting the region in AWS.AutoScaling() constructor. The CLI COMMAND line argument works fine from an EC2 Instance in us-east-1 by passing --region us-west-2 in the CLI to update the AutoscalingGroup in us-west-2.
But when I attempt the same in Lambda which is in us-east-1, I get a ValidationError : AutoscalingGroup name not found - null
var autoscalinggroup = new AWS.AutoScaling({'credentials': credentials, 'region' : 'us-west-2'});
var params = {
AutoScalingGroupName : 'converse-kibana-ecs-cluster-QA-Integration-Cluster-Container-1-0-8bint-5-ECSContainerAutoScalingGroup-18F80FECCOLH2',
MaxSize: 4,
MinSize: 2,
DesiredCapacity: 2
};
autoscalinggroup.updateAutoScalingGroup(params, function(err, data) {
if (err) {
console.log(err, err.stack);
}
else {
console.log(data);
}
});
amazon-web-services aws-lambda
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
Are you sure you've passed the correctAutoScalingGroupNameparam? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.
– Brandon
Dec 28 '18 at 0:59
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago
add a comment |
0
0
0
Am trying to update an AutoScalingGroup in another Region via my Node Lambda deployed in us-east-1.
I've tried setting the region in AWS.AutoScaling() constructor. The CLI COMMAND line argument works fine from an EC2 Instance in us-east-1 by passing --region us-west-2 in the CLI to update the AutoscalingGroup in us-west-2.
But when I attempt the same in Lambda which is in us-east-1, I get a ValidationError : AutoscalingGroup name not found - null
var autoscalinggroup = new AWS.AutoScaling({'credentials': credentials, 'region' : 'us-west-2'});
var params = {
AutoScalingGroupName : 'converse-kibana-ecs-cluster-QA-Integration-Cluster-Container-1-0-8bint-5-ECSContainerAutoScalingGroup-18F80FECCOLH2',
MaxSize: 4,
MinSize: 2,
DesiredCapacity: 2
};
autoscalinggroup.updateAutoScalingGroup(params, function(err, data) {
if (err) {
console.log(err, err.stack);
}
else {
console.log(data);
}
});
amazon-web-services aws-lambda
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
Am trying to update an AutoScalingGroup in another Region via my Node Lambda deployed in us-east-1.
I've tried setting the region in AWS.AutoScaling() constructor. The CLI COMMAND line argument works fine from an EC2 Instance in us-east-1 by passing --region us-west-2 in the CLI to update the AutoscalingGroup in us-west-2.
But when I attempt the same in Lambda which is in us-east-1, I get a ValidationError : AutoscalingGroup name not found - null
var autoscalinggroup = new AWS.AutoScaling({'credentials': credentials, 'region' : 'us-west-2'});
var params = {
AutoScalingGroupName : 'converse-kibana-ecs-cluster-QA-Integration-Cluster-Container-1-0-8bint-5-ECSContainerAutoScalingGroup-18F80FECCOLH2',
MaxSize: 4,
MinSize: 2,
DesiredCapacity: 2
};
autoscalinggroup.updateAutoScalingGroup(params, function(err, data) {
if (err) {
console.log(err, err.stack);
}
else {
console.log(data);
}
});
amazon-web-services aws-lambda
amazon-web-services aws-lambda
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
edited Dec 27 '18 at 23:40
John Rotenstein
67.8k775118
67.8k775118
asked Dec 27 '18 at 18:48
Dorian McAllister
497
asked Dec 27 '18 at 18:48
Dorian McAllister
497
asked Dec 27 '18 at 18:48
Dorian McAllister
497
497
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
Are you sure you've passed the correctAutoScalingGroupNameparam? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.
– Brandon
Dec 28 '18 at 0:59
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago
add a comment |
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
Are you sure you've passed the correctAutoScalingGroupNameparam? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.
– Brandon
Dec 28 '18 at 0:59
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
Are you sure you've passed the correct
AutoScalingGroupName param? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.– Brandon
Dec 28 '18 at 0:59
Are you sure you've passed the correct
AutoScalingGroupName param? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.– Brandon
Dec 28 '18 at 0:59
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53949537%2fcan-i-update-a-resource-like-autoscalinggroup-in-another-region-using-node-lam%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53949537%2fcan-i-update-a-resource-like-autoscalinggroup-in-another-region-using-node-lam%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It should work with some limitations. E.g. CloudWatch in Tokyo gave me an error with not being able to trigger lambda in us-east-1. This is documented and the error is different. I work usually with Python, but I went through docs and your code and cannot see any obvious issue. Note that here docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html is described that the region should be set up with Config. Let you try to search for an ASG in us-east-1 with region set to us-west-2 to confirm your hypothesis that region is ignored. Can be an implementation error or really wrong name.
– petrch
Dec 28 '18 at 0:56
Are you sure you've passed the correct
AutoScalingGroupNameparam? I created an ASG in us-west-2, created a Lambda function in us-east-1 with the code you provided, and invoked the Lambda function. The ASG was updated as expected. However, if I misspelled the name of the ASG, I got the error you posted.– Brandon
Dec 28 '18 at 0:59
Interesting.I did pass in the exact ASG name but it didn't work. At this point I have two lambdas in each region that updates their respective ASGs as a workaround
– Dorian McAllister
2 days ago