Skip to content

Commit 72fac56

Browse files
author
Arne-Christian Blystad
committed
feat(contrib/ec2): Set ELB timeout to 1200s
Amazon added support for setting the ELB timeout directly from CloudFormation on the 24th of December. This commit removes the documentation which tells the user to change it manually, as that is no longer needed, and sets it to 1200s.
1 parent be2891e commit 72fac56

2 files changed

Lines changed: 5 additions & 6 deletions

File tree

contrib/ec2/deis.template.json

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -293,7 +293,10 @@
293293
{
294294
"Fn::GetAtt": ["DeisWebELBSecurityGroup", "GroupId"]
295295
}
296-
]
296+
],
297+
"ConnectionSettings": {
298+
"IdleTimeout": 1200
299+
}
297300
}
298301
},
299302
"DeisWebELBSecurityGroup": {

docs/managing_deis/configure-load-balancers.rst

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,7 @@ EC2
3030
===
3131

3232
The Deis provisioning scripts for EC2 automatically create an Elastic Load Balancer for your Deis
33-
cluster. However, ELBs on EC2 have a default timeout of 60 seconds, which will disrupt a ``git push``
34-
when using Deis. You should manually `increase this timeout`_ to 1200 seconds to match the timeout
35-
on the router and application unit files.
33+
cluster.
3634

3735
Rackspace
3836
=========
@@ -53,8 +51,6 @@ You'll need to create two load balancers on Rackspace, as follows:
5351
Port 2222
5452
Protocol TCP
5553
56-
.. _`increase this timeout`: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/config-idle-timeout.html
57-
5854
Google Compute Engine
5955
=====================
6056

0 commit comments

Comments
 (0)