RESOLVED [Potential Regression]: Pipeline Impacting Issue

An issue that impacts SnapLogic pipeline executions has been raised which has been traced as being caused by an AWS SDK issue #2070. The AWS SDK issue was discovered and reported to the AWS SDK GitHub repository site on August 5th, 2019. AWS acknowledged the regression and committed a fix on August 7th and included in build 1.11.610.

The issue #2070 affects all SnapLogic customers that use AWS related Snaps that have HTTP or HTTPS proxy configured without a username and/or password.

Impacted Snap Packs

  • Binary
  • Redshift
  • Hadoop
  • Snowflake

Details of Impact
The problem affected any SnapLogic customers that leveraged AWS functionality whose Snaplex had either a system configuration that used an unauthenticated HTTP/HTTP proxy, or who had the same defined via Environment Variables. If a proxy was not used, or a proxy username and password was used, then customers were not affected.

To fix this, we are upgrading our dependency versions and will release new versions of the Snap Packs affected. This effort is currently undergoing QA review. When review is complete, we will send a follow up communication confirming that new versions are ready to be applied.

Please contact us directly if you have questions about this at

Thank you!
SnapLogic Product Team

All outstanding patches have been deployed and this issue is now closed. If you have Snaps that are impacted please update to the latest version.

If your Snap Pack was impacted, please be sure to update to the latest deployed version. For full 4.18 Snap Pack patch details, please review the documentation here.

Please contact us directly if you have questions about this at