Drop use of maap-py for obtaining S3 credentials (#71)

S3 credentials are now obtained via a role using EC2 instance metadata.

Fixes #14

CHANGELOG.md

@@ -7,7 +7,13 @@ The format is based on [Keep a Changelog], and this project adheres to
 
 ## Unreleased
 
-### 0.7.0 (2024-04-23)
+### Changed
+
+- [#14](https://github.com/MAAP-Project/gedi-subsetter/issues/14) AWS S3
+  credentials are no longer obtained via the `maap-py` library.  Instead, they
+  are obtained via a role using the EC2 instance metadata.
+
+## 0.7.0 (2024-04-23)
 
 ### Added
 

Makefile

@@ -28,7 +28,7 @@ $(CONDA_PREFIX): bin/create
 	@bin/create
 
 $(MAAP): $(CONDA_PREFIX) conda-lock.yml bin/install
-	@bin/install
+	@bin/install --dev
 
 ## lock: generate the lock file (conda-lock.yml) for the gedi_subset environment
 # Simply a convenience target to generate the lock file since typing `make lock`