Skip to content

Commit 792f3fa

Browse files
Merge pull request #237318 from linda33wj/main
Update S3 connector & SHIR articles
2 parents 662c956 + 219c878 commit 792f3fa

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

articles/purview/manage-integration-runtimes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: how-to
9-
ms.date: 04/20/2023
9+
ms.date: 05/08/2023
1010
---
1111

1212
# Create and manage a self-hosted integration runtime
@@ -56,7 +56,7 @@ Installation of the self-hosted integration runtime on a domain controller isn't
5656

5757
- Self-hosted integration runtime requires a 64-bit Operating System with .NET Framework 4.7.2 or above. See [.NET Framework System Requirements](/dotnet/framework/get-started/system-requirements) for details.
5858

59-
- The recommended minimum configuration for the self-hosted integration runtime machine is a 2-GHz processor with 4 cores, 8 GB of RAM, and 80 GB of available hard drive space. For the details of system requirements, see [Download](https://www.microsoft.com/download/details.aspx?id=39717).
59+
- The recommended minimum configuration for the self-hosted integration runtime machine is a 2-GHz processor with 8 cores, 28 GB of RAM, and 80 GB of available hard drive space. Scanning some data sources may require higher machine specification based on your scenario. Please also check the prerequisites in corresponding [connector article](microsoft-purview-connector-overview.md).
6060
- If the host machine hibernates, the self-hosted integration runtime doesn't respond to data requests. Configure an appropriate power plan on the computer before you install the self-hosted integration runtime. If the machine is configured to hibernate, the self-hosted integration runtime installer prompts with a message.
6161
- You must be an administrator on the machine to successfully install and configure the self-hosted integration runtime.
6262
- Scan runs happen with a specific frequency per the schedule you've set up. Processor and RAM usage on the machine follows the same pattern with peak and idle times. Resource usage also depends heavily on the amount of data that is scanned. When multiple scan jobs are in progress, you see resource usage goes up during peak times.

articles/purview/register-scan-amazon-s3.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: aashishr
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: how-to
9-
ms.date: 02/15/2023
9+
ms.date: 05/08/2023
1010
ms.custom: references_regions
1111
# Customer intent: As a security officer, I need to understand how to use the Microsoft Purview connector for Amazon S3 service to set up, configure, and scan my Amazon S3 buckets.
1212
---
@@ -32,10 +32,11 @@ For this service, use Microsoft Purview to provide a Microsoft account with secu
3232

3333
\** Lineage is supported if dataset is used as a source/sink in [Data Factory Copy activity](how-to-link-azure-data-factory.md)
3434

35+
### Known limitations
3536

36-
## Microsoft Purview scope for Amazon S3
37+
When scanning Amazon S3 of Glacier storage classes, schema extraction, classification and sensitivity labels are not supported.
3738

38-
We currently don't support ingestion private endpoints that work with your AWS sources.
39+
Microsoft Purview private endpoints are not supported when scanning Amazon S3.
3940

4041
For more information about Microsoft Purview limits, see:
4142

0 commit comments

Comments
 (0)