Trying to run a procedure against an Amazon Redshift table might result in errors similar to the following:

ERROR: Error during in-database processing.
ERROR: [SAS][ODBC Redshift Wire Protocol driver][Redshift]FATAL: no pg_hba.conf entry for host
"???", user "xxxx", database "xxxx", SSL off(File
/opt/brazil-pkg-cache/packages/RedshiftPADB/RedshiftPADB-1.0.17891.0/AL2_x86_64/generic-flavor/
src/src/pg/src/backend/libpq/auth.c; Line 477; Routine ClientAuthentication; ) 

The issue might occur when the following are true:

• You access an Amazon Redshift database using the SAS/ACCESS^® Interface to Amazon Redshift product.
• You use one of the following procedures:
  • FREQ
  • MEANS
  • RANK
  • REPORT
  • SORT
  • SUMMARY
  • TABULATE
• You access an SSL enabled database and specify the SSL options in the CONOPTS= LIBNAME option. 

Instead of passing the summarization to the database or the step failing without completing, SAS reads the Redshift table and completes the processing within SAS. The errors are informational errors that inform you that the in-database processing of the summarization did not occur.

A similar error might occur if you try to use the FEDSQL procedure to access a Redshift table that is in an SSL enabled database.  With FEDSQL, the step stops processing and exits with the error (unlike the other procedures).

This issue occurs because the connection string that is built for the database is missing the CONOPTS= option, which include information about SSL. 

There is no workaround for this issue.