nit but I'm not sure why this static component needs to be separated. I would just leave it inside the page component

probably subjective, but IMO it makes the root component read nicer as we don't look at long lines that aren't really interesting. LatestFindingsPageTitle tells me all i need to know without looking how it's done

do we actually need both EuiButton and react-router-dom Link? consider doing:

const BackToResourcesButton = () => {
  const { push } = useHistory();

  return (
    <EuiButtonEmpty
      iconType={'arrowLeft'}
      onClick={() => push(generatePath(findingsNavigation.findings_by_resource.path))}
    >
      <FormattedMessage
        id="xpack.csp.findings.resourceFindings.backToResourcesPageButtonLabel"
        defaultMessage="Back to group by resource view"
      />
    </EuiButtonEmpty>
  );
};

Eui don't mind using buttons as links and the opposite aswell

is there a way to do a push with href?

i agree it's unfortunate, but IMO better than using onClick, which makes it a non-anchor link. this means you can't:

• copy the link
• ctrl+click the link to open in a new tab

what i'd like to do is use href in EuiButtonEmpty but it doesn't work with react-router
there's some info on this here but i didn't manage to make anything out of it.