You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .kiro/specs/infra/requirements.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@ This document specifies the requirements for creating a new AWS workshop infrast
24
24
-**Modular_Scripts**: Architecture where bootstrap functionality is separated into focused scripts (UserData → bootstrap → vscode → base)
25
25
-**CDK_Naming_Convention**: Consistent pattern for CDK construct resource naming that produces clean CloudFormation logical IDs following {ConstructName}{ResourceType} format
26
26
-**EKS_IDE_Integration**: Architecture pattern where EKS cluster shares security groups and IAM roles with IDE environment for seamless kubectl access
27
+
-**Workshop_Naming_Convention**: Consistent resource naming pattern using "workshop-" prefix followed by component and function names for operational clarity and management
27
28
28
29
## Requirements
29
30
@@ -282,3 +283,15 @@ This document specifies the requirements for creating a new AWS workshop infrast
282
283
4. WHEN EKS cluster integrates with IDE, THE system SHALL share security groups and IAM roles through proper construct interfaces
283
284
5. WHEN construct naming is applied consistently, THE system SHALL ensure all resources follow the same naming convention across VPC, IDE, Database, EKS, and CodeBuild constructs
284
285
286
+
### Requirement 21
287
+
288
+
**User Story:** As a workshop developer, I want consistent logging and resource naming with a universal "workshop-" prefix, so that all workshop-related resources are easily identifiable, filterable, and manageable in AWS services.
289
+
290
+
#### Acceptance Criteria
291
+
292
+
1. WHEN Lambda functions are created, THE system SHALL use "workshop-" prefix followed by component and function name (e.g., "workshop-ide-launcher", "workshop-database-setup")
293
+
2. WHEN CodeBuild projects are created, THE system SHALL use "workshop-" prefix for project names (e.g., "workshop-setup")
294
+
3. WHEN CloudWatch log groups are created, THE system SHALL use "workshop-" prefix for consistent grouping and filtering
295
+
4. WHEN bootstrap logging is configured, THE system SHALL use "workshop-ide-bootstrap-{timestamp}" pattern for unique log group names
296
+
5. WHEN AWS resources are named, THE system SHALL follow the pattern "workshop-{component}-{function}" for operational consistency
Copy file name to clipboardExpand all lines: .kiro/specs/infra/tasks.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -373,6 +373,16 @@
373
373
- Applied consistent naming convention: construct name + resource type (e.g., Ide + PasswordSecret = IdePasswordSecret)
374
374
-_Requirements: 1.1, 5.6_
375
375
376
+
-[x] 11.28 Implement consistent "workshop-" naming convention for all AWS resources
377
+
- Updated Lambda function names to use "workshop-" prefix: "setup-codebuild-start" → "workshop-codebuild-start", "ide-ec2-launcher" → "workshop-ide-launcher"
378
+
- Updated CodeBuild project name: "workshop-codebuild" → "workshop-setup" for consistency
379
+
- Updated Database Lambda: "workshop-db-setup" → "workshop-database-setup" for clarity
380
+
- Updated IDE Lambda functions: "ide-cloudfront-prefix-lookup" → "workshop-ide-prefixlist", dynamic password function → "workshop-ide-password"
0 commit comments