import type { AdditionalDiagnosticContext } from '../../actions/diagnose';
import type { SDK } from '../aws-auth/sdk';
import type { ResourceError } from '../stack-events/resource-errors';
/**
 * Investigate a failed custom resource by surfacing its backing Lambda's CloudWatch logs.
 *
 * The CloudFormation event does not name the backing function — only the resource's
 * `ServiceToken` (in the template) does. We resolve that to a function name, derive the
 * log group (the `/aws/lambda/<fn>` convention, confirmed via the function's LoggingConfig
 * only if the convention turns up empty), and fetch the relevant log lines.
 *
 * When the handler uses the cfn-response library, the failing log stream name is embedded
 * in the status reason ("See the details in CloudWatch Log Stream: <name>"), so we can
 * target that exact invocation.
 */
export declare function investigateCustomResource(err: ResourceError, sdk: SDK, debug: (msg: string) => Promise<void>): Promise<AdditionalDiagnosticContext[]>;
//# sourceMappingURL=investigate-custom-resource.d.ts.map