How grasslandnetwork/big_node_aws works
Main Components
a) Development Environment Layer:
• Docker Container (Primary Development Environment)
• Local File System Mounts (~/.aws)
• Developer's Host Machine
b) Authentication Layer:
• AWS SSO Integration
• AWS CLI Configuration
• Authentication Token Management
c) AWS Service Integration Layer:
• AWS Services (S3, Lambda, SQS, API Gateway)
• AWS Control Tower
• AWS Administrator Access Role
• Developer Workspace | (Top Layer)
• Authentication & | (Middle Layer)
• Security |
• AWS Infrastructure | (Bottom Layer)
Component Relationships
• Double lines (⇒) for data/resource access
Specific Elements
a) Developer Workspace Layer:
• Docker Container (show installed tools: AWS CLI, kubectl)
• Local .aws directory
• Makefile automation
• Documentation resources
b) Authentication Layer:
• AWS SSO configuration
• Token management
• Role-based access control
• SSO URL endpoints
c) AWS Infrastructure Layer:
• Administrative access scope
• Supported AWS services
• Regional configurations (ca-central-1)
Important Flows to Highlight
• Developer login flow
• AWS SSO authentication process
• Container initialization process
• AWS service access patterns
Technical Details to Emphasize
• Docker container isolation
• AWS profile configuration
• SSO integration points
• Tool chain relationships
Key Annotations to Include:
• Token expiration windows
• Required environment variables
• Mount points for persistent storage
• Authentication flow sequence numbers
Remember to include references to the documentation directory structure, as it contains important information about Control Tower, SSO, and general setup procedures that support the overall system architecture.