Aller au contenu principal

Deploy the template from the AWS CLI

Maybe we'll use more partials. Not sure yet.

The CloudFormation template deploys a server instance with JupyterLab running in a container controlled by systemd.

Decide which template to use​

New section?​

The Jupyter template's parameter file is here: '/deployments/aws/parameters/'.

Do they add/change values to the parm JSON file? Seems like we need a section for the parms, like what's in the console topic - we could use a partial that works for the console Jupyter topic and this CLI Jupyter topic.

Related... the console topic tells them they can configure stack options. How do they set those options if they use the CLI? Looks like that's "tags" and "capabilities" in the code below. Maybe link to AWS doc about that? Compare that part of the AWS console to what's in the code here. For the console do we need to point out anything in particular on the UI page that follows the parms?

Create a stack​

remarque

You can deploy the stack using the aws cloudformation create-stack or aws cloudformation deploy commands. This example uses aws cloudformation create-stack. See AWS CLI Command Reference for the syntax differences.

Run the command that matches the template you're using:

The user has already cloned the repo. For the CLI (not the concole), seems they can reference the local template file and don't need to download it. Maybe we need to include the paths to the template and parm files starting with /deployments/ in the code below? How does this work?

remarque
  • CAPABILITY_IAM is required if IamRole is set to New.
  • CAPABILITY_NAMED_IAM is required if IamRole is set to New and IamRoleName is given a value.

To use an existing role, see Control AWS Access and Permissions using Permissions and Policies. Is this to be an external link--or our topic that's WIP?

Delete a stack​

Let's remove. This topic is for installing. If they want to eventually remove the stack, as CLI users maybe they know how to run "delete-stack"? Maybe originally this topic was a reference, not an installation task topic.

Run this command:

Get stack information​

Can we tell them what sort of information or why they do this? Is this something they normally do after creating a stack?

Delete-stack is in the first line of code--probably there by mistake.

The second one is also in the last section.

Run this command:

Get stack outputs​

Run this command:

***Tell them how to access JupyterLab.

Do they get that from "describe-stacks"?