<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic getting alerts in AWS UnauthorizedAccess:IAMUser/InstanceCredentialExfiltration.InsideAWS in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/getting-alerts-in-aws-unauthorizedaccess-iamuser/m-p/58307#M768</link>
    <description>&lt;P&gt;Hi folks,&amp;nbsp;&lt;BR /&gt;I have been using IAM instance profile as a credentials provider to Databricks workspace. I am getting this error&amp;nbsp;&lt;BR /&gt;"&lt;SPAN&gt;Credentials created exclusively for an EC2 instance using instance role &amp;lt;role-arn&amp;gt; have been used from a remote AWS account 414351767826."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can someone suggest how to tackle it .&amp;nbsp;&lt;BR /&gt;I have tried this &lt;A title="s3 commit service" href="https://docs.databricks.com/en/security/network/classic/s3-commit-service.html#aws-guardduty-alerts-related-to-s3-commit-service" target="_self"&gt;link&lt;/A&gt;&amp;nbsp;.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 24 Jan 2024 06:46:49 GMT</pubDate>
    <dc:creator>anurag_dev</dc:creator>
    <dc:date>2024-01-24T06:46:49Z</dc:date>
    <item>
      <title>getting alerts in AWS UnauthorizedAccess:IAMUser/InstanceCredentialExfiltration.InsideAWS</title>
      <link>https://community.databricks.com/t5/administration-architecture/getting-alerts-in-aws-unauthorizedaccess-iamuser/m-p/58307#M768</link>
      <description>&lt;P&gt;Hi folks,&amp;nbsp;&lt;BR /&gt;I have been using IAM instance profile as a credentials provider to Databricks workspace. I am getting this error&amp;nbsp;&lt;BR /&gt;"&lt;SPAN&gt;Credentials created exclusively for an EC2 instance using instance role &amp;lt;role-arn&amp;gt; have been used from a remote AWS account 414351767826."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can someone suggest how to tackle it .&amp;nbsp;&lt;BR /&gt;I have tried this &lt;A title="s3 commit service" href="https://docs.databricks.com/en/security/network/classic/s3-commit-service.html#aws-guardduty-alerts-related-to-s3-commit-service" target="_self"&gt;link&lt;/A&gt;&amp;nbsp;.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jan 2024 06:46:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/getting-alerts-in-aws-unauthorizedaccess-iamuser/m-p/58307#M768</guid>
      <dc:creator>anurag_dev</dc:creator>
      <dc:date>2024-01-24T06:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: getting alerts in AWS UnauthorizedAccess:IAMUser/InstanceCredentialExfiltration.InsideAWS</title>
      <link>https://community.databricks.com/t5/administration-architecture/getting-alerts-in-aws-unauthorizedaccess-iamuser/m-p/58868#M798</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/98706"&gt;@anurag_dev&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Databricks runs a commit service that coordinates writes to Amazon S3 from multiple clusters. This service runs in the Databricks&amp;nbsp;control plane. (441371677306)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The S3 commit service helps guarantee consistency of writes across multiple clusters on a single table in specific cases. For example, the commit service helps&amp;nbsp;Delta Lake&amp;nbsp;implement ACID transactions.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;In the default configuration, Databricks sends temporary AWS credentials from the data plane to the control plane in the commit service API call. Instance profile credentials are valid for six hours.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If you use&amp;nbsp;AWS GuardDuty&amp;nbsp;and you access data using AWS IAM instance profiles, GuardDuty may create alerts for default Databricks behavior related to Delta Lake, Structured Streaming, Auto Loader, or&amp;nbsp;COPY&amp;nbsp;INTO. These alerts are related to instance credential exfiltration detection, which is enabled by default. These alerts include the title UnauthorizedAccess: IAMUser/InstanceCredentialExfiltration.InsideAWS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You can configure your Databricks deployment to address GuardDuty alerts related to the S3 commit service by creating an&amp;nbsp;AWS instance profile&amp;nbsp;that assumes the role of your original S3 data access IAM role.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As an alternative to using instance profile credentials, this new instance profile can configure clusters to assume a role with short-duration tokens. This capability already exists in all recent Databricks Runtime versions and can be enforced globally via&amp;nbsp;cluster policies.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please refer to the following documentation for a detailed explanation:-&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.databricks.com/administration-guide/cloud-configurations/aws/s3-commit-service.html#aws-guardduty-alerts-related-to-s3-commit-service" target="_blank" rel="noopener noreferrer"&gt;https://docs.databricks.com/administration-guide/cloud-configurations/aws/s3-commit-service.html#aws-guardduty-alerts-related-to-s3-commit-service&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jan 2024 16:02:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/getting-alerts-in-aws-unauthorizedaccess-iamuser/m-p/58868#M798</guid>
      <dc:creator>Yeshwanth</dc:creator>
      <dc:date>2024-01-31T16:02:30Z</dc:date>
    </item>
  </channel>
</rss>

