Error message received when trying to configure the Umbrella integration with a Cisco-managed s3 bucket:
Input 'aws-s3' failed with: failed to initialize s3 poller: failed to get AWS region for bucket: exceeded maximum number of attempts, 3, request send failed, Get "https://s3.cisco-managed-us-east-2.s3.amazonaws.com/cisco-managed-us-east-2?location=": x509: certificate is valid for *.s3.amazonaws.com, s3.amazonaws.com, not s3.cisco-managed-us-east-2.s3.amazonaws.com
Testing with s3 tools, if I remove the s3 at the beginning of the URL, connections work (so change from https://s3.cisco-managed... to https://cisco-managed). If I flip the switch to convert from s3 to s3-fips, that url changes in that spot, so the integration IS adding the s3 / s3-fips, and just need the ability to NOT have it in the URL, so we can pull our logs properly.
Error message received when trying to configure the Umbrella integration with a Cisco-managed s3 bucket:
Input 'aws-s3' failed with: failed to initialize s3 poller: failed to get AWS region for bucket: exceeded maximum number of attempts, 3, request send failed, Get "https://s3.cisco-managed-us-east-2.s3.amazonaws.com/cisco-managed-us-east-2?location=": x509: certificate is valid for *.s3.amazonaws.com, s3.amazonaws.com, not s3.cisco-managed-us-east-2.s3.amazonaws.com
Testing with s3 tools, if I remove the s3 at the beginning of the URL, connections work (so change from https://s3.cisco-managed... to https://cisco-managed). If I flip the switch to convert from s3 to s3-fips, that url changes in that spot, so the integration IS adding the s3 / s3-fips, and just need the ability to NOT have it in the URL, so we can pull our logs properly.