There were multiple conflicting permissions issues when this was initially implemented, which indicated using EDL/access tokens instead of the lambda role was the preferred path, but now that we need to test ingest from SIT & UAT I'd like to revisit that decision and see if we can simplify by just using the lambda role instead
Using the services EDL to generate access tokens from https://archive.swot.podaac.earthdata.nasa.gov/s3credentials means that loading granules ingested to the SIT and UAT venues will always fail.
There were multiple conflicting permissions issues when this was initially implemented, which indicated using EDL/access tokens instead of the lambda role was the preferred path, but now that we need to test ingest from SIT & UAT I'd like to revisit that decision and see if we can simplify by just using the lambda role instead