The Lightstep satellite is available as an AMI in several AWS regions:

The AMI will start the Satellite binary automatically when an instance boots.

When creating instances, set user data to configure Satellites. If you are using the console, you can find user data under Configure Instance Details and Advanced Details. User data should be entered into the console as YAML-formatted text. You can use the template below and find detailed explanations and recommended settings here. Defaults are entered, but you can change them.

If you are happy with the default port numbers and don’t need TLS, you only need to modify the following settings:
* satellite_key
* pool
* bytes_per_project

The GUID does not need to be the same as the AWS instance ID.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
# Satellite Configuration
#
# This file describes all the required and optional fields to customize your satellite configuration.
#
# ----------------------- AUTHENTICATION ---------------------
# REQUIRED: Satellite API Key
satellite_key:

# ----------------------- DEBUGGING ---------------------
# HIGHLY RECOMMENDED: Satellite Pool Name
pool:
# HIGHLY RECOMMENDED: GUID
guid:

# ----------------------- MONITORING ---------------------
# OPTIONAL: Export statsd metrics for Satellite
# To enable satellite metrics, uncomment the `statsd` header and relevant fields below.
#
# statsd:
#
#   REQUIRED: Host address for the statsd agent
#     Note: "localhost" may not work, use 127.0.0.1 instead
#     Uncomment the line below to set the statsd agent host address
#   host:
#
#   REQUIRED: Port number for the statsd agent
#     Uncomment the line below to set the port number for your statsd agent
#   port:
#
#   REQUIRED: Choose between statsd and dogstatsd metrics format
#     The following settings are mutually exclusive and you must set exactly one of them.
#     Uncomment one of the following lines to enable the desired format for metrics
#   export_statsd: true
#   export_dogstatsd: true
#
#   OPTIONAL: Add custom tags for dogstatsd metrics
#     This setting is only available when export_dogstatsd: true
#     Uncomment the following line to add one or more custom tags for dogstatsd metrics
#   dogstatsd_tags:
#
#
#   Note: Metrics exported by the satellite are named as follows:
#       <prefix>.<satellite_prefix|client_prefix>.<metric_name>
#   You can use the set of optional fields below to customize the metric names, if desired.
#
#     All prefixes and tag names below should follow these rules, unless your metrics service provider supports additional characters:
#     - must start with a letter
#     - must only contain ASCII alphanumerics (lowercase recommended), underscores, and periods
#
#   OPTIONAL: Set a custom metric name prefix
#     The prefix is empty by default.
#     Uncomment the following line to set a custom metrics prefix
#   prefix: "lightstep"
#
#   OPTIONAL: Rename the satellite and/or client metrics
#     The satellite_prefix field has a default value of "satellite", and will be included in the name of all
#     metrics that reflect Satellite behavior.
#     Uncomment the following line to set a custom prefix for satellite metrics
#   satellite_prefix: "satellite"
#
#     The client_prefix field has a default value of "client", and will be included as part of the name for all metrics
#     that reflect the behavior of the Lightstep tracer client (these metrics are still exported via the Satellite).
#     Uncomment the following line to set a custom prefix for client metrics
#   client_prefix: "client"

# ----------------------- PORTS ---------------------

# Ports cannot be shared. All port numbers below must be unique.

# REQUIRED: Debug Port ("diagnostic")
diagnostic_port: 8000

# REQUIRED: Admin Ports: Health Checks / Diagnostics
# The values are flexible and can be set to different (unbound) port numbers as needed.
admin:

  # REQUIRED: Plaintext Admin Port
  plain_port: 8180

  # Uncomment the line below to enable the secure health check port.
  # secure_port: 9090

# REQUIRED: Proto-via-HTTP Ports
# If either of these ports is set, the corresponding port in the 'grpc' section must also be configured.
http:

  # RECOMMENDED: Plaintext Proto-via-HTTP Port
  # Required for the satellite to accept *unencrypted* Proto-over-HTTP span traffic.
  plain_port: 8181

  # Uncomment the line below to enable the secure Proto-over-HTTP port.
  # secure_port: 9191

# REQUIRED: gRPC Ports
# At least one of these ports is required in order to accept span traffic via gRPC.
# The values are flexible and can be set to a different (unbound) port as needed.
grpc:

  # RECOMMENDED: Plaintext gRPC Port
  # Required for the satellite to accept *unencrypted* gRPC span traffic.
  plain_port: 8282

  # OPTIONAL: Secure gRPC Port
  # Uncomment the line below to enable the secure gRPC port.
  # secure_port: 9292

# REQUIRED: Thrift ports
# At least one of the following ports must be set in order to handle Thrift span traffic.

# REQUIRED: Plaintext Thrift Port
# This port accepts *unencrypted* Thrift span traffic.
plain_port: 8383

# OPTIONAL: Secure Thrift Port

# Uncomment the line below to enable the secure Thrift port.
# secure_port: 9393

# ----------------------- MEMORY ---------------------

# REQUIRED: Memory settings

reporter:
  bytes_per_project: 100_000_000
  bytes_per_project_overrides:

# ----------------------- TLS ---------------------

# OPTIONAL: TLS certificate path
# Required if using any of the SecurePorts in order to provide TLS termination at the satellite.

# Uncomment the line below (and set appropriately) if using any of the secure ports above.
# tls_cert_prefix:

# -------------------MISC-------------------------
# OPTIONAL: Ingestion tags
# Uncomment the line below and add a comma-separated list of tag/value pairs. These tags and values are added to every span the Satellite ingests.
# ingestion_tags:

# OPTIONAL: Single project mode
# Uncomment the lines below if you are only running one project in Lightstep and you don't want to pass an access token from your tracer to your Satellite.

# disable_access_token_checking:
# project_name

Follow these instructions to further validate your installation and troubleshoot any issues.

You configure your Lightstep tracers to communicate with your Satellites by providing their location. If you are using a single Satellite, you provide the DNS name or IP address of that Satellite. For more than one, use the name or address of the load balancer you’ve deployed. Find out how to do that in the language-specific Quick Start guides.

By default, client libraries use secure connections. If you’ve configured your Satellites to use plainport connections, you must configure your tracer appropriately.