Usage
Deployed Resources
Once deployed, you should see the following in your AWS account:
Naming convention: <org>-<env>-<domain>-<module>-<resource>
SSM parameters: /<org>/<domain>/<module>/<resource-type>/<resource-name>/<attribute>
| Resource | Deployed Name / SSM Path | Config Reference |
|---|---|---|
| IAM Role | <org>-dev-govern-roles-data-admin/<org>/govern/generated-role/data-admin/id |
generateRoles.data-admin in govern/roles.yaml |
| Glue Catalog Encryption | Account-level setting | deployed by glue-catalog module(not configurable) |
| LakeFormation Data Lake Settings | Account-level setting | deployed by govern/lakeformation-settings.yaml(not configurable) |
Post-Deployment Verification
- Navigate to IAM Console > Roles and confirm the data-admin role exists.
- Navigate to AWS Glue Console > Settings and verify encryption is enabled.
- Navigate to AWS Lake Formation Console > Data lake administrators and verify the data-admin role is listed.
Next Steps
This minimal kit provides the governance foundation. Extend it by adding modules:
- Add
@aws-mdaa/datalakefor S3 buckets with Lake Formation integration - Add
@aws-mdaa/athena-workgroupfor SQL query capabilities - Add
@aws-mdaa/dataops-projectfor Glue ETL pipelines
See the Basic DataLake starter kit for a working example with data storage and querying.