You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/instructors/admin/integration/lms-systems/blackboard.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@
6
6
Blackboard LTI 1.x
7
7
==================
8
8
9
-
Please be sure to check out the :ref:`Codio LTI App <lti-app>` which allows for an easy way to integrate and to map Codio course assignments to your LMS. The `following page <https://library.blackboard.com/ref/df5b20ed-ce8d-4428-a595-a0091b23dda3/Content/_admin_app_system/admin_app_basic_lti_tool_providers.htm>`_ explains how to set up external apps in Blackboard Learn.
9
+
The `following page <https://library.blackboard.com/ref/df5b20ed-ce8d-4428-a595-a0091b23dda3/Content/_admin_app_system/admin_app_basic_lti_tool_providers.htm>`_ explains how to set up external apps in Blackboard Learn.
Copy file name to clipboardExpand all lines: source/instructors/admin/sandboxes.rst
+87-7Lines changed: 87 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ Sandboxes
9
9
About Sandboxes
10
10
---------------
11
11
12
-
Sandboxes provide time‑boxed, ephemeral **AWS Management Console environments** that expire automatically. A sandbox's permissions are defined by a template and can range from full administrator access to least‑privileged roles, depending on need. When a sandbox's duration ends, access is revoked and all resources created inside the sandbox are cleaned up automatically—no user action required.
12
+
Sandboxes provide time-boxed, ephemeral **AWS Management Console environments** that expire automatically. A sandbox's permissions are defined by a template and can range from full administrator access to least-privileged roles, depending on need. When a sandbox's duration ends, access is revoked and all resources created inside the sandbox are cleaned up automatically—no user action required.
13
13
14
14
.. important::
15
15
@@ -50,6 +50,8 @@ Key Concepts
50
50
- Resource-specific inputs for the sandbox type (for example, EC2 instance settings: ``instance_type``, ``image``, ``volume_size``, ``connection_mode``).
51
51
* - **Region**
52
52
- The AWS region in which sandboxes are created. Currently fixed to ``us-east-1``.
53
+
* - **Prime**
54
+
- Optional pre-warming configuration for sandboxes. When enabled, the platform creates "primed" sandboxes ahead of time to reduce wait time for learners.
53
55
54
56
Lifecycle, Duration, and Cleanup
55
57
--------------------------------
@@ -58,10 +60,34 @@ Lifecycle, Duration, and Cleanup
58
60
- **Extend:** While running, you may extend the lifetime in ``lifetime_extension`` increments, **not exceeding** ``lifetime_max``.
59
61
- **Expire & Clean:** When the lifetime ends, access is revoked and resources created by the sandbox are cleaned up automatically—no user action required.
60
62
63
+
Creating a Sandbox and a Collection
64
+
-----------------------------------
65
+
66
+
1. Select **Sandboxes** from the Build menu, if that option is not available, Sandboxes are not enabled for your organization.
67
+
68
+
.. image:: /img/sandbox_build.png
69
+
:width:90%
70
+
:align:center
71
+
:alt:Select Sandboxes on the top menu.
72
+
73
+
2. Then click the **New Collection** button in the top right. Give your collection a name and click `Create Collection`.
74
+
75
+
.. image:: /img/sandbox_newcollection.png
76
+
:width:70%
77
+
:align:center
78
+
:alt:New Collection screenshot.
79
+
80
+
3. Once created, your new collection will open automatically. Click `Edit` to start creating sandboxes. The section below explains how to get started quickly.
81
+
82
+
.. image:: /img/sandbox_overview.png
83
+
:width:90%
84
+
:align:center
85
+
:alt:View of Sandboxes Overview.
86
+
61
87
Sandbox Configuration (``sandbox.yml``)
62
88
---------------------------------------
63
89
64
-
Define sandboxes in YAML. The best starting point is using this command to get four **working examples** you can adapt:
90
+
Define sandboxes in YAML, one sandbox per folder. The best starting point is using this command to get four **working examples** you can adapt:
65
91
66
92
.. code-block:: bash
67
93
@@ -97,6 +123,10 @@ Top-level keys
97
123
- mapping
98
124
- Yes
99
125
- Configuration block that defines lifetime behavior, permissions, provisioning engine, and resource parameters.
126
+
* - ``prime``
127
+
- mapping
128
+
- No
129
+
- Optional pre-warming configuration for **any** sandbox type. Supports priming continuously or on scheduled UTC start dates.
100
130
101
131
``settings`` (common)
102
132
~~~~~~~~~~~~~~~~~~~~~
@@ -156,11 +186,20 @@ After setting ``type`` to ``aws_ec2``, configure the following ``parameters``:
156
186
* - ``instance_type``
157
187
- string
158
188
- Yes
159
-
- EC2 instance type to provision (e.g., ``t3.medium``).
189
+
- EC2 instance type to provision (e.g., ``t3.medium``). Supported instance types include:
- Windows: ``codio-aws-windows-base`` (or Windows Codio AMI)
164
203
* - ``volume_size``
165
204
- integer (GB)
166
205
- Yes
@@ -169,6 +208,48 @@ After setting ``type`` to ``aws_ec2``, configure the following ``parameters``:
169
208
- enum
170
209
- Optional
171
210
- Default access channel for the instance. Supported values in examples: ``ssh`` or ``vnc``.
211
+
If omitted, both connection modes are available.
212
+
213
+
``prime`` (common)
214
+
~~~~~~~~~~~~~~~~~~
215
+
216
+
Optionally prime (pre-warm) sandboxes to reduce learner wait time. Priming can be:
217
+
218
+
- **Continuous:** Maintain a steady pool of primed sandboxes.
219
+
- **Date-based:** Prime a specific number of sandboxes at specific UTC start times.
220
+
221
+
.. note::
222
+
223
+
For **Continuous**, sandboxes will start priming immediately after publishing the Collection. For **Date-based** this date specifies the time sandboxes will start priming, not when they will be ready.
224
+
225
+
.. list-table::
226
+
:widths: 22 14 10 54
227
+
:header-rows: 1
228
+
229
+
* - Key
230
+
- Type
231
+
- Required
232
+
- Description
233
+
* - ``type``
234
+
- enum
235
+
- Yes
236
+
- Priming mode. Supported values: ``continuous`` or ``date``.
237
+
* - ``count``
238
+
- integer
239
+
- Conditional
240
+
- Required when ``prime.type`` is ``continuous``. Number of primed sandboxes to keep available.
241
+
* - ``start_dates``
242
+
- list
243
+
- Conditional
244
+
- Required when ``prime.type`` is ``date``. List of scheduled priming entries (UTC).
245
+
* - ``start_dates[].date``
246
+
- string (datetime, UTC)
247
+
- Conditional
248
+
- Required within each ``start_dates`` entry. Date/time (UTC) when priming should occur (e.g., ``2025-11-24T11:40:00Z``).
249
+
* - ``start_dates[].count``
250
+
- integer
251
+
- Conditional
252
+
- Required within each ``start_dates`` entry. Number of primed sandboxes to create at the scheduled date/time.
172
253
173
254
Permissions (Full to Least-Privileged)
174
255
--------------------------------------
@@ -182,10 +263,9 @@ This design lets you run anything from **full AWS** environments to tightly cons
182
263
183
264
.. admonition:: How can I create a policy?
184
265
185
-
Policies are an AWS concept. If you want to read more, please visit AWS' guide to
186
-
`Policies and permissions`__ and the
266
+
Policies are an AWS concept. If you want to read more, please visit AWS' guide to
267
+
`Policies and permissions`__ and the
187
268
`IAM tutorial: Delegate access across AWS accounts using IAM roles`__.
0 commit comments