Changed the settings to prevent the SlowDown errors that occured with…

… PSScene3Band. Decreased Execution Limit from 1400 to 200. Modified the ingest and publish workflow so that it waits longer for a retry and has a larger multiplier on the time it waits when having to wait more than once. Note, JitterStrategy means that there is randomness introduced in the wait time, this should allow more granules to get through in the event of time or synchronized based errors.

app/stacks/cumulus/main.tf

@@ -576,7 +576,7 @@ module "cumulus" {
     {
       id              = "backgroundJobQueue",
       url             = aws_sqs_queue.background_job_queue.id,
-      execution_limit = 1400
+      execution_limit = 200
     }
   ]
 }

app/stacks/cumulus/templates/ingest-and-publish-granule-workflow.asl.json

@@ -113,9 +113,9 @@
                     "Lambda.SdkClientException",
                     "Lambda.TooManyRequestsException"
                   ],
-                  "IntervalSeconds": 4,
+                  "IntervalSeconds": 6,
                   "MaxAttempts": 6,
-                  "BackoffRate": 2,
+                  "BackoffRate": 3,
                   "JitterStrategy": "FULL"
                 },
                 {

app/stacks/post-deploy-mods/resources/lambdas/pre-filter-DistributionApiEndpoints/src/lambda_function.py

@@ -18,7 +18,7 @@
 #
 # If this is set to False, this function does nothing extra than the original lambda did, it just allows a pass through
 # If this is set to True, this function does the normal request, then attempts to detect a request for a file, if this IS a file request, then it checks EULA permissions for the current user
-is_post_EULA_filter_enabled = True  # True # False
+is_post_EULA_filter_enabled = False   # True # False
 #
 # Which dynamo DB table holds the Access Tokens after a succesful authentication?
 #dynamo_db__table_name = 'cumulus-prod-DistributionAccessTokensTable'