Describe a data file so tools can read it — AWS Glue and Data Catalog

Your goal

Create a catalog database and a table describing two fields in a data file.

Why this matters

Data files are easier to use when their fields have clear names and types. You will create a catalog database and a table description, then retrieve the schema you saved.

Words you will use

A catalog stores descriptions of data. A schema names fields and their types. A Glue database groups table descriptions; it does not itself hold your file contents.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a catalog database

Create a Glue database to group table descriptions. This is catalog metadata, not a running database engine or the storage location of the actual files.

2. Describe the visit records

Create a visits table with a page string and a numeric visits field. The S3 location is a practice path. A catalog description does not repair missing or malformed source files.

3. Read the table description

Get the visits table and inspect its columns and location. The lab verifies the saved schema, showing what a catalog knows about data before a query tool reads it.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.