INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

Topic lessonTopic: AWS data pipelines and SQL Server integration

Lake Formation access paths across the Data Catalog, S3 and audit

Visibility of metadata does not establish read access to SQL Server detail. Test the reporting and detail roles across both integrated and direct access paths.

What you will learn

Test the reporting and detail roles across both integrated and direct access paths.

Prerequisite

This exercise uses fictional evidence and makes no changes in a live environment.

Compare two ways of reaching the same object

Integrated access to a registered S3 location requires the relevant data grant and IAM permission. Direct S3 API access is a separate control path.

Test integrated and direct access
Test integrated and direct access1: Actor — Pick the resource — Catalog. 2: Catalog — Inspect data grants — Data. 3: Data — Compare both paths — Verify123ActorCatalogDataVerifyTest integrated and direct access1: Actor — Pick the resource — Catalog. 2: Catalog — Inspect data grants — Data. 3: Data — Compare both paths — Verify123ActorCatalogDataVerify
  1. Actor → CatalogPick the resource
  2. Catalog → DataInspect data grants
  3. Data → VerifyCompare both paths
Actor
Summary or detail reader
Catalog
Specific table and action
Data
Registered S3 location
Verify
Query and direct API

Restrict the summary reader

Use the same synthetic objects and test identity for each trial.
TrialExpectedEvidence
Athena summaryAllowedGrant and applicable IAM permissions
Athena detailDeniedDetail table grant absent
Direct S3 detailDeniedCheck IAM and bucket policies
AuditMatches all three trialsCompare actor, action and time

A denied query alone cannot demonstrate that direct object access is denied.

Acceptance checks

Identify the permission type Separate creating metadata at a location, selecting from a table and IAM GetDataAccess.

Exercise the other path Review applicable direct S3 and encryption permissions with the owner.

Reconcile audit evidence Record the test actor, resource, time and result.

Check your decision

Choose an option to see the result and explanation.

You can see the table in the catalog. What comes next?
Read the answer and reason

Answer: Verify the scoped data read and result · Execute a bounded query as the intended user.

Athena denies the detail query. What is still worth checking?
Read the answer and reason

Answer: Test direct S3 reads as the same actor · The direct API has separate controls.

What ties the audit record to the test?
Read the answer and reason

Answer: Actor, resource, action, timestamp and result · Capture enough information to match the operation.

Check, then explain in your own words

  1. Match actors and tables.
  2. Exercise query and direct access.
  3. Reconcile the audit entries.
Check your understanding: Does data-location permission for creating a table establish read access?

Check the relevant table data grants and IAM permissions separately.

Permissions for metadata and reading the data serve different purposes.

Sources and conditions checked

The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.