ufo 3.5.7 → 4.0.0

data/docs/_reference/ufo-task.md

@@ -16,29 +16,28 @@ Run a one-time task.
 You can use the `--command` or `-c` option to override the Docker container command.
 
     ufo task hi-migrate # default command
-    ufo task hi-web --command bin/migrate
-    ufo task hi-web --command bin/with_env bundle exec rake db:migrate:redo VERSION=xxx
-    ufo task hi-web -c uptime
-    ufo task hi-web -c pwd
+    ufo task demo-web --command bin/migrate
+    ufo task demo-web --command bin/with_env bundle exec rake db:migrate:redo VERSION=xxx
+    ufo task demo-web -c uptime
+    ufo task demo-web -c pwd
 
-## Skipping Docker
+## Skipping Docker and Task Registration
 
-The `--no-docker` option is useful. By default, the `ufo task` command will build the docker image.  The docker build process usually is the part that takes the most time. You can skip the docker build process after building it at least once.  This is a faster way to run a bunch of commands with thesame Docker image. Example:
+The `--task-only` option is useful. By default, the `ufo task` command will build the docker image and then register a new task definition.  The docker build process usually is the part that takes the most time. You can skip the docker build process after building it at least once.  This is a faster way to run a bunch of commands with the same Docker image. Example:
 
-    ufo task hi-web -c uptime # build at least once
-    ufo task hi-web --no-docker -c ls # skip docker for speed
-    ufo task hi-web --no-docker -c pwd # skip docker for speed
+    ufo task demo-web -c uptime # build at least once
+    ufo task demo-web --task-only -c ls # skip docker for speed
+    ufo task demo-web --task-only -c pwd # skip docker for speed
 
 
 ## Options
 
 ```
-    [--docker], [--no-docker]    # Enable docker build and push
-                                 # Default: true
-c, [--command=one two three]     # Override the command used for the container
-    [--verbose], [--no-verbose]  
-    [--mute], [--no-mute]        
-    [--noop], [--no-noop]        
-    [--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+    [--task-only], [--no-task-only]  # Skip docker and task register steps. Only run the task.
+c, [--command=one two three]         # Override the command used for the container
+    [--verbose], [--no-verbose]      
+    [--mute], [--no-mute]            
+    [--noop], [--no-noop]            
+    [--cluster=CLUSTER]              # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-tasks-build.md

@@ -71,7 +71,7 @@ Here's an example of each of them:
 **task_definitions.rb**:
 
 ```ruby
-task_definition "hi-web" do
+task_definition "demo-web" do
     source "main" # will use ufo/templates/main.json.erb
     variables(
     family: task_definition_name,
@@ -81,7 +81,7 @@ task_definition "hi-web" do
   )
 end
 
-task_definition "hi-worker" do
+task_definition "demo-worker" do
     source "main" # will use ufo/templates/main.json.erb
     variables(
     family: task_definition_name,
@@ -90,7 +90,7 @@ task_definition "hi-worker" do
   )
 end
 
-task_definition "hi-clock" do
+task_definition "demo-clock" do
     source "main" # will use ufo/templates/main.json.erb
     variables(
     family: task_definition_name,
@@ -105,7 +105,7 @@ The shared variables are set in the variables folder:
 **ufo/variables/base.rb**:
 
 ```ruby
-@image = helper.full_image_name # includes the git sha tongueroo/hi:ufo-[sha].
+@image = helper.full_image_name # includes the git sha tongueroo/demo-ufo:ufo-[sha].
 @cpu = 128
 @memory_reservation = 256
 @environment = helper.env_file(".env")
@@ -131,20 +131,20 @@ You should see output similar to below:
     $ ufo tasks build
     Building Task Definitions...
     Generating Task Definitions:
-      ufo/output/hi-web.json
-      ufo/output/hi-worker.json
-      ufo/output/hi-clock.json
+      ufo/output/demo-web.json
+      ufo/output/demo-worker.json
+      ufo/output/demo-clock.json
     Task Definitions built in ufo/output.
     $
 
-Let's take a look at one of the generated files: `.ufo/output/hi-web.json`.
+Let's take a look at one of the generated files: `.ufo/output/demo-web.json`.
 
     {
-      "family": "hi-web",
+      "family": "demo-web",
       "containerDefinitions": [
         {
           "name": "web",
-          "image": "tongueroo/hi:ufo-2017-06-11T22-22-32-a18aa30",
+          "image": "tongueroo/demo-ufo:ufo-2017-06-11T22-22-32-a18aa30",
           "cpu": 128,
           "memoryReservation": 256,
           "portMappings": [

data/docs/_reference/ufo-tasks-register.md

@@ -17,9 +17,9 @@ The `ufo tasks register` command registers all the generated task definitions in
 
 You should see something similiar to this:
 
-    hi-clock task definition registered.
-    hi-web task definition registered.
-    hi-worker task definition registered.
+    demo-clock task definition registered.
+    demo-web task definition registered.
+    demo-worker task definition registered.
 
 You can verify that the task definitions have been registered properly by viewing the AWS ECS Console Task Definitions page.  You should see something similar to this:
 

data/docs/_reference/ufo-tasks.md

@@ -30,6 +30,6 @@ Note all the existing ufo/output generated task defintions are wiped out.
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/_reference/ufo-upgrade-help.md

@@ -0,0 +1,15 @@
+---
+title: ufo upgrade help
+reference: true
+---
+
+## Usage
+
+    ufo upgrade help [COMMAND]
+
+## Description
+
+Describe subcommands or one specific subcommand
+
+
+

data/docs/_reference/ufo-upgrade-v2to3.md

@@ -0,0 +1,15 @@
+---
+title: ufo upgrade v2to3
+reference: true
+---
+
+## Usage
+
+    ufo upgrade v2to3
+
+## Description
+
+Upgrade from version 2 to 3.
+
+
+

data/docs/_reference/ufo-upgrade-v3_3to3_4.md

@@ -0,0 +1,15 @@
+---
+title: ufo upgrade v3_3to3_4
+reference: true
+---
+
+## Usage
+
+    ufo upgrade v3_3to3_4
+
+## Description
+
+Upgrade from version 3.3 to 3.4
+
+
+

data/docs/_reference/ufo-upgrade-v3to4.md

@@ -0,0 +1,27 @@
+---
+title: ufo upgrade v3to4
+reference: true
+---
+
+## Usage
+
+    ufo upgrade v3to4
+
+## Description
+
+Upgrade from version 3 to 4.
+
+## Examples
+
+    ufo upgrade v3to4 --vpc-id vpc-123 --ecs-subnets subnet-111 subnet-222 --elb-subnets subnet-111 subnet-222
+
+
+## Options
+
+```
+[--force]                      # Bypass overwrite are you sure prompt for existing files.
+[--vpc-id=VPC_ID]              # Vpc id
+[--ecs-subnets=one two three]  # Subnets for ECS tasks, defaults to --elb-subnets set to
+[--elb-subnets=one two three]  # Subnets for ELB
+```
+

data/docs/_reference/ufo-upgrade.md

@@ -0,0 +1,28 @@
+---
+title: ufo upgrade
+reference: true
+---
+
+## Usage
+
+    ufo upgrade SUBCOMMAND
+
+## Description
+
+upgrade subcommands
+
+## Subcommands
+
+* [ufo upgrade v2to3]({% link _reference/ufo-upgrade-v2to3.md %}) - Upgrade from version 2 to 3.
+* [ufo upgrade v3_3to3_4]({% link _reference/ufo-upgrade-v3_3to3_4.md %}) - Upgrade from version 3.3 to 3.4
+* [ufo upgrade v3to4]({% link _reference/ufo-upgrade-v3to4.md %}) - Upgrade from version 3 to 4.
+
+## Options
+
+```
+[--verbose], [--no-verbose]  
+[--mute], [--no-mute]        
+[--noop], [--no-noop]        
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
+```
+

data/docs/_reference/ufo-version.md

@@ -18,6 +18,6 @@ Prints version number of installed ufo.
 [--verbose], [--no-verbose]  
 [--mute], [--no-mute]        
 [--noop], [--no-noop]        
-[--cluster=CLUSTER]          # Cluster.  Overrides ufo/settings.yml.
+[--cluster=CLUSTER]          # Cluster.  Overrides .ufo/settings.yml.
 ```
 

data/docs/articles.md

@@ -5,6 +5,6 @@ title: Articles
 * This blog post provides an introduction to the tool: [Ufo - Build Docker Containers and Ship Them to AWS ECS](https://medium.com/@tongueroo/ufo-easily-build-docker-containers-and-ship-them-to-aws-ecs-15556a2b39f#.qqu8o4wal)
 * This presentation covers ufo also: [Ufo Ship on AWS ECS](http://www.slideshare.net/tongueroo/ufo-ship-for-aws-ecs-70885296)
 
-<a id="prev" class="btn btn-basic" href="{% link _docs/faq.md %}">Back</a>
-<a id="next" class="btn btn-primary" href="{% link reference.md %}">Next Step</a>
+<a id="prev" class="btn btn-basic" href="{% link _docs/auto-completion.md %}">Back</a>
+<a id="next" class="btn btn-primary" href="{% link _docs/next-steps.md %}">Next Step</a>
 <p class="keyboard-tip">Pro tip: Use the <- and -> arrow keys to move back and forward.</p>

data/docs/docs.md

@@ -4,7 +4,7 @@ title: Docs
 
 ## Overview
 
-Ufo is a tool that makes building and shipping Docker containers to AWS ECS super easy. Ufo provides a `ufo ship` command that does this. Essentially:
+Ufo is a tool that makes deploying to AWS ECS easy. Ufo provides a `ufo ship` command that does this. It essentially:
 
 1. ufo builds the docker container image
 2. registers that image to ECS as a task definition

data/docs/quick-start.md

@@ -2,19 +2,22 @@
 title: Quick Start
 ---
 
-In a hurry? No sweat! Here's a quick start to using ufo that takes only a few minutes. For this example, we will use a sinatra app from [tongueroo/hi](https://github.com/tongueroo/ufo).  The first `ufo init` command sets up the ufo directory structure in your project. The second `ufo ship` command deploys your code to an AWS ECS service.
+In a hurry? No sweat! Here's a quick start to using ufo that takes only a few minutes. For this example, we will use a sinatra app from [tongueroo/demo-ufo](https://github.com/tongueroo/demo-ufo).  The `ufo init` command sets up the ufo directory structure in your project. The `ufo ship` command deploys your code to an AWS ECS service.  The `ufo ps` and `ufo scale` command shows you how to verify and scale additional containers.
 
 ```sh
 gem install ufo
-git clone https://github.com/tongueroo/hi.git
-cd hi
-ufo init --app=hi --image=tongueroo/hi
-ufo ship hi-web
+git clone https://github.com/tongueroo/demo-ufo.git
+cd demo-ufo
+ufo init --app=demo --image=tongueroo/demo-ufo
+ufo current demo-web
+ufo ship
+ufo ps
+ufo scale 2
 ```
 
 ## What Happened
 
-The `ufo ship hi-web` command does the following:
+The `ufo ship demo-web` command does the following:
 
 1. Builds the Docker image and pushes it to a registry
 2. Builds the ECS task definitions and registry them to ECS
@@ -23,7 +26,7 @@ The `ufo ship hi-web` command does the following:
 You should see something similar to this:
 
 ```
-$ ufo init --app=hi --image=tongueroo/hi
+$ ufo init --app=demo --image=tongueroo/demo-ufo
 Setting up ufo project...
       create  .env
       create  .ufo/settings.yml
@@ -36,13 +39,22 @@ Setting up ufo project...
       create  bin/deploy
       append  .gitignore
 Starter ufo files created.
-$ ufo ship hi-web
+$ ufo ship demo-web
 Building docker image with:
-  docker build -t tongueroo/hi:ufo-2017-09-10T15-00-19-c781aaf -f Dockerfile .
+  docker build -t tongueroo/demo-ufo:ufo-2017-09-10T15-00-19-c781aaf -f Dockerfile .
 ....
 Software shipped!
+$ ufo ps
++----------+------+-------------+---------------+---------+-------+
+|    Id    | Name |   Release   |    Started    | Status  | Notes |
++----------+------+-------------+---------------+---------+-------+
+| f590ee5e | web  | demo-web:85 | 1 minutes ago | RUNNING |       |
++----------+------+-------------+---------------+---------+-------+
+$ ufo scale 2
+Scale demo-web service in development cluster to 2
 $
 ```
+
 Congratulations! You have successfully deployed code to AWS ECS with ufo. It was really that simple 😁
 
 Note: This quick start does require that you have a docker working on your environment.  For docker installation instructions refer to to the official [docker installation guide](https://docs.docker.com/engine/installation/).

data/docs/reference.md

@@ -3,17 +3,25 @@ title: CLI Reference
 ---
 {% include reference.md %}
 
+* [ufo apps]({% link _reference/ufo-apps.md %})
+* [ufo cancel]({% link _reference/ufo-cancel.md %})
 * [ufo completion]({% link _reference/ufo-completion.md %})
 * [ufo completion_script]({% link _reference/ufo-completion_script.md %})
+* [ufo current]({% link _reference/ufo-current.md %})
 * [ufo deploy]({% link _reference/ufo-deploy.md %})
 * [ufo destroy]({% link _reference/ufo-destroy.md %})
 * [ufo docker]({% link _reference/ufo-docker.md %})
 * [ufo init]({% link _reference/ufo-init.md %})
+* [ufo network]({% link _reference/ufo-network.md %})
+* [ufo ps]({% link _reference/ufo-ps.md %})
+* [ufo releases]({% link _reference/ufo-releases.md %})
+* [ufo resources]({% link _reference/ufo-resources.md %})
+* [ufo rollback]({% link _reference/ufo-rollback.md %})
 * [ufo scale]({% link _reference/ufo-scale.md %})
 * [ufo ship]({% link _reference/ufo-ship.md %})
 * [ufo ships]({% link _reference/ufo-ships.md %})
+* [ufo stop]({% link _reference/ufo-stop.md %})
 * [ufo task]({% link _reference/ufo-task.md %})
 * [ufo tasks]({% link _reference/ufo-tasks.md %})
-* [ufo upgrade3]({% link _reference/ufo-upgrade3.md %})
-* [ufo upgrade3_3_to_3_4]({% link _reference/ufo-upgrade3_3_to_3_4.md %})
+* [ufo upgrade]({% link _reference/ufo-upgrade.md %})
 * [ufo version]({% link _reference/ufo-version.md %})

data/exe/ufo

@@ -3,7 +3,7 @@
 # Trap ^C
 Signal.trap("INT") {
   puts "\nCtrl-C detected. Exiting..."
-  sleep 1
+  sleep 0.1
   exit
 }
 

data/lib/cfn/stack.yml

@@ -0,0 +1,259 @@
+Description: "Ufo ECS stack <%= @pretty_service_name %>"
+Parameters:
+  # required
+  Vpc:
+    Description: Existing vpc id
+    Type: AWS::EC2::VPC::Id
+  ElbSubnets:
+    Description: Existing subnet ids for ELB
+    Type: List<AWS::EC2::Subnet::Id>
+  EcsSubnets:
+    Description: Existing subnet ids for ECS
+    Type: List<AWS::EC2::Subnet::Id>
+  EcsSecurityGroups:
+    Description: Existing ecs security group ids
+    Type: String
+    Default: ''
+  ElbSecurityGroups:
+    Description: Existing elb security group ids. List with commas.
+    Type: String
+    Default: ''
+
+  ElbTargetGroup:
+    Description: Existing target group
+    Type: String
+    Default: '' # when blank the automatically created TargetGroup is used
+  CreateElb:
+    Description: Create elb
+    Type: String
+    Default: true
+  EcsDesiredCount:
+    Description: Ecs desired count
+    Type: String
+    Default: 1
+  EcsTaskDefinition:
+    Description: Ecs task definition arn
+    Type: String
+
+  # Using to keep state
+  ElbEipIds:
+    Description: ELB EIP Allocation ids to use for network load balancer
+    Type: String
+    Default: ''
+Conditions:
+  CreateElbIsTrue: !Equals [ !Ref CreateElb, true ]
+  ElbTargetGroupIsBlank: !Equals [ !Ref ElbTargetGroup, '' ]
+  CreateTargetGroupIsTrue: !And
+  - !Condition CreateElbIsTrue
+  - !Condition ElbTargetGroupIsBlank
+  ElbSecurityGroupsIsBlank: !Equals [ !Ref ElbSecurityGroups, '' ]
+  EcsSecurityGroupsIsBlank: !Equals [ !Ref EcsSecurityGroups, '' ]
+  EcsDesiredCountIsBlank: !Equals [ !Ref EcsDesiredCount, '' ]
+Resources:
+  Elb:
+    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
+    Condition: CreateElbIsTrue
+    Properties:
+<% if ENV['UFO_FORCE_ELB'] -%>
+# Error: SetSubnets is not supported for load balancers of type 'network'
+# Happens: When changing subnets for an ELB
+# Solution: Rename the ELB to force a replacement of it
+<% random = (0...3).map { (65 + rand(26)).chr }.join.downcase %>
+      Name: <%= "#{@pretty_service_name}-#{random}" %>
+<% end -%>
+      Type: <%= @elb_type %>
+      Tags:
+      - Key: Name
+        Value: <%= @pretty_service_name %>
+<% if @elb_type == "application" -%>
+      # Add additional extra security groups if parameters set
+      SecurityGroups: !Split
+        - ','
+        - !If
+          - ElbSecurityGroupsIsBlank
+          - !Ref ElbSecurityGroup
+          - !Join [',', [!Ref ElbSecurityGroups, !Ref ElbSecurityGroup]]
+<% end -%>
+<% if @elb_type == "network" && @subnet_mappings && !@subnet_mappings.empty? -%>
+      SubnetMappings:
+<% @subnet_mappings.each do |allocation_id, subnet_id| -%>
+        - AllocationId: <%= allocation_id %>
+          SubnetId: <%= subnet_id %>
+<% end -%>
+<% else -%>
+      Subnets: !Ref ElbSubnets
+<% end -%>
+<%= custom_properties(:Elb) %>
+
+  TargetGroup:
+    Type: AWS::ElasticLoadBalancingV2::TargetGroup
+    Condition: CreateTargetGroupIsTrue
+    Properties:
+      VpcId: !Ref Vpc
+      Tags:
+      - Key: Name
+        Value: <%= @pretty_service_name %>
+<% if ENV['UFO_FORCE_TARGET_GROUP'] -%>
+# When adding and removing EIPs
+# Error: TargetGroup cannot be associated with more than one load balancer
+# Solution: https://forums.aws.amazon.com/thread.jspa?threadID=254544
+      Name: !Join
+      - '-'
+      - - <%= @pretty_service_name %>
+        - !Select [ 2, !Split [ '-', !GetAtt Elb.LoadBalancerName]]
+<% end -%>
+      Protocol: <%= @default_target_group_protocol %>
+<% if @container[:network_mode] == "awsvpc" -%>
+      TargetType: ip
+<% end -%>
+<% if @elb_type == "network" && @network_mode == "awsvpc" -%>
+      # target groups with network load balancers need to check the container
+      # port dirtectly and will be using
+      HealthCheckPort: <%= @container[:port] %>
+<% end -%>
+<%= custom_properties(:TargetGroup) %>
+
+  Listener:
+    Type: AWS::ElasticLoadBalancingV2::Listener
+    Condition: CreateElbIsTrue
+    Properties:
+      DefaultActions:
+      - Type: forward
+        TargetGroupArn:
+          !If [ElbTargetGroupIsBlank, !Ref TargetGroup, !Ref ElbTargetGroup]
+      LoadBalancerArn: !Ref Elb
+      Protocol: <%= @default_listener_protocol %>
+<%= custom_properties(:Listener) %>
+
+<% if @elb_type == "application" -%>
+  ElbSecurityGroup:
+    Type: AWS::EC2::SecurityGroup
+    Condition: CreateElbIsTrue
+    Properties:
+      GroupDescription: Allow http to client host
+      VpcId: !Ref Vpc
+      SecurityGroupIngress:
+      - IpProtocol: tcp
+        FromPort: '<%= cfn[:listener][:port] %>'
+        ToPort: '<%= cfn[:listener][:port] %>'
+        CidrIp: 0.0.0.0/0
+      SecurityGroupEgress:
+      - IpProtocol: tcp
+        FromPort: '0'
+        ToPort: '65535'
+        CidrIp: 0.0.0.0/0
+      Tags:
+      - Key: Name
+        Value: <%= @pretty_service_name %>-elb
+<%= custom_properties(:ElbSecurityGroup) %>
+<% end -%>
+
+  Ecs:
+    Type: AWS::ECS::Service
+<% if @create_elb -%>
+    DependsOn: Listener
+<% end -%>
+    Properties:
+      Cluster: <%= @cluster %>
+      DesiredCount: !If
+      - EcsDesiredCountIsBlank
+      - !Ref AWS::NoValue
+      - !Ref EcsDesiredCount
+      TaskDefinition: !Ref EcsTaskDefinition
+<% if pretty_name? -%>
+      ServiceName: <%= @pretty_service_name %>
+<% end -%>
+<% if @container[:fargate] -%>
+      LaunchType: FARGATE
+<% end -%>
+<% if @container[:network_mode] == "awsvpc" -%>
+      NetworkConfiguration:
+        AwsvpcConfiguration:
+          Subnets: !Ref EcsSubnets # required
+          SecurityGroups: !Split
+            - ','
+            - !If
+              - EcsSecurityGroupsIsBlank
+              - !Ref EcsSecurityGroup
+              - !Join [',', [!Ref EcsSecurityGroups, !Ref EcsSecurityGroup]]
+<% if @container[:fargate] -%>
+          AssignPublicIp: ENABLED # Works with fargate but doesnt seem to work with non-fargate
+<% end -%>
+<% end -%>
+      # Default to port 80 to get template to validate.  For worker processes
+      # there is no actual port used.
+      LoadBalancers: !If
+      - CreateTargetGroupIsTrue
+      - - ContainerName: <%= @container[:name] %>
+          ContainerPort: <%= @container[:port] || 80 %>
+          TargetGroupArn: !Ref TargetGroup
+      - !If
+        - ElbTargetGroupIsBlank
+        - []
+        - - ContainerName: <%= @container[:name] %>
+            ContainerPort: <%= @container[:port] || 80 %>
+            TargetGroupArn: !Ref ElbTargetGroup
+<%= custom_properties(:Ecs) %>
+
+  EcsSecurityGroup:
+    Type: AWS::EC2::SecurityGroup
+    Properties:
+      GroupDescription: Allow http to client host
+      VpcId: !Ref Vpc
+<% if @elb_type == "network" -%>
+      SecurityGroupIngress:
+      - IpProtocol: tcp
+        FromPort: '<%= @container[:port] %>'
+        ToPort: '<%= @container[:port] %>'
+        CidrIp: 0.0.0.0/0
+        Description: docker ephemeral port range for network elb
+<% end -%>
+      # Outbound access: instance needs access to internet to pull down image
+      # or else get CannotPullContainerError
+      SecurityGroupEgress:
+      - IpProtocol: tcp
+        FromPort: '0'
+        ToPort: '65535'
+        CidrIp: 0.0.0.0/0
+        Description: outbound traffic
+      Tags:
+      - Key: Name
+        Value: <%= @pretty_service_name %>
+<%= custom_properties(:EcsSecurityGroup) %>
+
+<% if @elb_type == "application" -%>
+  # Allow all traffic from ELB SG to ECS SG
+  EcsSecurityGroupRule:
+    Type: AWS::EC2::SecurityGroupIngress
+    Condition: CreateElbIsTrue
+    Properties:
+      IpProtocol: tcp
+      FromPort: '0'
+      ToPort: '65535'
+      SourceSecurityGroupId: !GetAtt ElbSecurityGroup.GroupId
+      GroupId: !GetAtt EcsSecurityGroup.GroupId
+      Description: application elb access to ecs
+<%= custom_properties(:EcsSecurityGroupRule) %>
+<% end -%>
+<% if @create_route53 -%>
+  Dns:
+    Type: AWS::Route53::RecordSet
+    Properties:
+      Comment: cname to load balancer
+      Type: CNAME
+      TTL: '60' # ttl has special casing
+      ResourceRecords:
+      - !GetAtt Elb.DNSName
+<%= custom_properties(:Dns) %>
+<% end -%>
+
+Outputs:
+  ElbDns:
+    Description: Elb Dns
+    Condition: CreateElbIsTrue
+    Value: !GetAtt Elb.DNSName
+<% if @create_route53 -%>
+  Route53Dns:
+    Description: Route53 Dns
+    Value: !Ref Dns
+<% end -%>