AWS Discovery fails on large payload attachments

If public image discovery for AWS is on and there are a number of public images, the payload size sent by AWS is bigger than the default payload size in the instance.

1. Go to sc_properties_list.do and set the com.glide.attachment.max_size system property to a small value, for example, 1 MB.

   Note that this property takes a value in bytes, so for a desired setting of 1 MB, the property value would be set to 1048576 bytes.

2. Run AWS Discovery.

   For more information, see the documentation topic Discover and view AWS resources.

   An error message appears in the Discovery logs indicating that the payload attachment exceeds the limit set by com.glide.attachment.max_size.

Choose from one of the following solutions depending on your product version:

• Prior to Helsinki: Because AWS public image discovery is set on by default, be sure to set the com.glide.attachment.max_size property to a large value (over 5 MB, for example) to decrease the likelihood of encountering this issue. Note that this property takes a value in bytes, so for a desired setting of 5 MB, the property value would be set to 5242880 bytes.
  
  
• Geneva, Helsinki and later releases: As updated in PRB663054, Public image discovery is off by default after Geneva Patch 10 and Helsinki Patch 8 so the likelihood of encountering this issue is greatly reduced.