Skip to content

Commit

Permalink
Update Accessing-S3-via-SageMaker-notebooks.md
Browse files Browse the repository at this point in the history
  • Loading branch information
qualiaMachine authored Nov 6, 2024
1 parent 4a21e5a commit 389f2ad
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions episodes/Accessing-S3-via-SageMaker-notebooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ exercises: 10

::::::::::::::::::::::::::::::::::::::::::::::::

### Setup
## Initial setup

#### Open .ipynb notebook
Once your newly created notebook *instance* ("SageMaker notebook") shows as `InService`, open the instance in Jupyter Lab. From there, we will select the standard python3 environment (conda_python3) to start our first .ipynb notebook ("Jupyter notebook"). You can name your Jupyter notebook something along the lines of, `Interacting-with-S3.ipynb`.
Expand Down Expand Up @@ -52,7 +52,7 @@ s3 = boto3.client('s3')

```

### Reading data from S3
## Reading data from S3

You can either read data from S3 into memory or download a copy of your S3 data into your notebook's instance. While loading into memory can save on storage resources, it can be convenient at times to have a local copy. We'll show you both strategies in this upcoming section. Here's a more detailed look at the pros and cons of each strategy:

Expand Down

0 comments on commit 389f2ad

Please sign in to comment.