Elastic Beanstalk Change ELB Type

Does anyone know if it's possible to change an existing AWS Elastic Beanstalk environment to an Application Load Balancer (instead of a classic one).

As far as I know only Application ELB's can be protected with AWS WAF and DDOS "Shield" so any existing EB app can't take advantage of these features since they have classic ELB's.

asked Oct 10 '17 at 11:56

David

1,25241541

add a comment |

Does anyone know if it's possible to change an existing AWS Elastic Beanstalk environment to an Application Load Balancer (instead of a classic one).

As far as I know only Application ELB's can be protected with AWS WAF and DDOS "Shield" so any existing EB app can't take advantage of these features since they have classic ELB's.

asked Oct 10 '17 at 11:56

David

1,25241541

add a comment |

Does anyone know if it's possible to change an existing AWS Elastic Beanstalk environment to an Application Load Balancer (instead of a classic one).

As far as I know only Application ELB's can be protected with AWS WAF and DDOS "Shield" so any existing EB app can't take advantage of these features since they have classic ELB's.

asked Oct 10 '17 at 11:56

David

1,25241541

Does anyone know if it's possible to change an existing AWS Elastic Beanstalk environment to an Application Load Balancer (instead of a classic one).

As far as I know only Application ELB's can be protected with AWS WAF and DDOS "Shield" so any existing EB app can't take advantage of these features since they have classic ELB's.

amazon-web-services elastic-beanstalk amazon-elb amazon-elastic-beanstalk amazon-waf

asked Oct 10 '17 at 11:56

David

1,25241541

asked Oct 10 '17 at 11:56

David

1,25241541

asked Oct 10 '17 at 11:56

David

1,25241541

asked Oct 10 '17 at 11:56

David

1,25241541

asked Oct 10 '17 at 11:56

David

1,25241541

add a comment |

2 Answers
2

active

oldest

votes

Hello As Per AWS Documentation:

The Elastic Beanstalk Environment Management Console only supports
creating and managing an Elastic Beanstalk environment with a Classic
Load Balancer. For other options, see Application Load Balancer and
Network Load Balancer.

Also

Note You can only set the load balancer type during environment
creation. (Refer AWS Documetnation)

So When you deploy application to Elastic Beanstalk via AWS CLI:

Try

eb create test-env --elb-type network

eb create test-env --elb-type application

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

2

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

add a comment |

It is not possible to change the load balancer type for an existing environment but I have used the following process to create a cloned environment with an application load balancer (instead of classic).

In the console, save configuration of the original env.

In terminal, eb config get [save name], you will get a file in .elasticbeanstalksaved_configs .

Edit the file to add

OptionSettings: aws:elasticbeanstalk:environment: LoadBalancerType: application

and remove (if you have those):

aws:elb:loadbalancer: CrossZone: true aws:elb:policies: ConnectionDrainingEnabled: true aws:elb:listener:443: [whatever]

You can use this opportunity to do other changes, such as upgrade PlatformArn

Save modified config as [new save name].

In terminal, eb config put [new save name] .

Update your .ebextensions to have LoadBalancerType: application and optionally add listener to elbv2. You can also create in the console manually later.

aws:elbv2:listener:443: ListenerEnabled: true SSLPolicy: ELBSecurityPolicy-TLS-1-2-2017-01 SSLCertificateArns: [your cert id] DefaultProcess: default Protocol: HTTPS Rules: ''

Create a new env with eb create [new env name] --cfg [new save name]

Now you will have a new environment with a different load balancer type side-by-side with your old environment. You can perform testing, make further configuration changes and then if all is well, swap CNAMEs and terminate the previous environment.

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

add a comment |

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');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f46666169%2felastic-beanstalk-change-elb-type%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

Hello As Per AWS Documentation:

The Elastic Beanstalk Environment Management Console only supports
creating and managing an Elastic Beanstalk environment with a Classic
Load Balancer. For other options, see Application Load Balancer and
Network Load Balancer.

Also

Note You can only set the load balancer type during environment
creation. (Refer AWS Documetnation)

So When you deploy application to Elastic Beanstalk via AWS CLI:

Try

eb create test-env --elb-type network

eb create test-env --elb-type application

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

2

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

add a comment |

Hello As Per AWS Documentation:

The Elastic Beanstalk Environment Management Console only supports
creating and managing an Elastic Beanstalk environment with a Classic
Load Balancer. For other options, see Application Load Balancer and
Network Load Balancer.

Also

Note You can only set the load balancer type during environment
creation. (Refer AWS Documetnation)

So When you deploy application to Elastic Beanstalk via AWS CLI:

Try

eb create test-env --elb-type network

eb create test-env --elb-type application

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

2

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

add a comment |

Hello As Per AWS Documentation:

The Elastic Beanstalk Environment Management Console only supports
creating and managing an Elastic Beanstalk environment with a Classic
Load Balancer. For other options, see Application Load Balancer and
Network Load Balancer.

Also

Note You can only set the load balancer type during environment
creation. (Refer AWS Documetnation)

So When you deploy application to Elastic Beanstalk via AWS CLI:

Try

eb create test-env --elb-type network

eb create test-env --elb-type application

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

Hello As Per AWS Documentation:

The Elastic Beanstalk Environment Management Console only supports
creating and managing an Elastic Beanstalk environment with a Classic
Load Balancer. For other options, see Application Load Balancer and
Network Load Balancer.

Also

Note You can only set the load balancer type during environment
creation. (Refer AWS Documetnation)

So When you deploy application to Elastic Beanstalk via AWS CLI:

Try

eb create test-env --elb-type network

eb create test-env --elb-type application

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

answered Oct 10 '17 at 12:35

Kush Vyas

3,1381925

2

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

add a comment |

2

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

Thanks, that's a shame. It means any existing environments can't be changed I'd presume then.

– David
Oct 10 '17 at 12:58

As of now no according to official AWS documentation , do mark question solved if the answer clears your doubts

– Kush Vyas
Oct 10 '17 at 13:02

Annoying how coy the official docs are about this in other places. You can use the EC2 load balancer migration wizard to generate a second application load balancer which forwards to the classic one, if you don't mind paying twice and it serves your purposes.

– thadk
Oct 23 '18 at 3:10

add a comment |

In the console, save configuration of the original env.

In terminal, eb config get [save name], you will get a file in .elasticbeanstalksaved_configs .

Edit the file to add

OptionSettings: aws:elasticbeanstalk:environment: LoadBalancerType: application

and remove (if you have those):

aws:elb:loadbalancer: CrossZone: true aws:elb:policies: ConnectionDrainingEnabled: true aws:elb:listener:443: [whatever]

You can use this opportunity to do other changes, such as upgrade PlatformArn

Save modified config as [new save name].

In terminal, eb config put [new save name] .

Update your .ebextensions to have LoadBalancerType: application and optionally add listener to elbv2. You can also create in the console manually later.

aws:elbv2:listener:443: ListenerEnabled: true SSLPolicy: ELBSecurityPolicy-TLS-1-2-2017-01 SSLCertificateArns: [your cert id] DefaultProcess: default Protocol: HTTPS Rules: ''

Create a new env with eb create [new env name] --cfg [new save name]

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

add a comment |

In the console, save configuration of the original env.

In terminal, eb config get [save name], you will get a file in .elasticbeanstalksaved_configs .

Edit the file to add

OptionSettings: aws:elasticbeanstalk:environment: LoadBalancerType: application

and remove (if you have those):

aws:elb:loadbalancer: CrossZone: true aws:elb:policies: ConnectionDrainingEnabled: true aws:elb:listener:443: [whatever]

You can use this opportunity to do other changes, such as upgrade PlatformArn

Save modified config as [new save name].

In terminal, eb config put [new save name] .

Update your .ebextensions to have LoadBalancerType: application and optionally add listener to elbv2. You can also create in the console manually later.

aws:elbv2:listener:443: ListenerEnabled: true SSLPolicy: ELBSecurityPolicy-TLS-1-2-2017-01 SSLCertificateArns: [your cert id] DefaultProcess: default Protocol: HTTPS Rules: ''

Create a new env with eb create [new env name] --cfg [new save name]

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

add a comment |

In the console, save configuration of the original env.

In terminal, eb config get [save name], you will get a file in .elasticbeanstalksaved_configs .

Edit the file to add

OptionSettings: aws:elasticbeanstalk:environment: LoadBalancerType: application

and remove (if you have those):

aws:elb:loadbalancer: CrossZone: true aws:elb:policies: ConnectionDrainingEnabled: true aws:elb:listener:443: [whatever]

You can use this opportunity to do other changes, such as upgrade PlatformArn

Save modified config as [new save name].

In terminal, eb config put [new save name] .

Update your .ebextensions to have LoadBalancerType: application and optionally add listener to elbv2. You can also create in the console manually later.

aws:elbv2:listener:443: ListenerEnabled: true SSLPolicy: ELBSecurityPolicy-TLS-1-2-2017-01 SSLCertificateArns: [your cert id] DefaultProcess: default Protocol: HTTPS Rules: ''

Create a new env with eb create [new env name] --cfg [new save name]

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

In the console, save configuration of the original env.

In terminal, eb config get [save name], you will get a file in .elasticbeanstalksaved_configs .

Edit the file to add

OptionSettings: aws:elasticbeanstalk:environment: LoadBalancerType: application

and remove (if you have those):

aws:elb:loadbalancer: CrossZone: true aws:elb:policies: ConnectionDrainingEnabled: true aws:elb:listener:443: [whatever]

You can use this opportunity to do other changes, such as upgrade PlatformArn

Save modified config as [new save name].

In terminal, eb config put [new save name] .

Update your .ebextensions to have LoadBalancerType: application and optionally add listener to elbv2. You can also create in the console manually later.

aws:elbv2:listener:443: ListenerEnabled: true SSLPolicy: ELBSecurityPolicy-TLS-1-2-2017-01 SSLCertificateArns: [your cert id] DefaultProcess: default Protocol: HTTPS Rules: ''

Create a new env with eb create [new env name] --cfg [new save name]

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

answered Sep 8 '18 at 16:20

Arik Yavilevich

11116

add a comment |

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu