Amy krizan wang patch 2#5
Conversation
Updated 'DevOps' to 'DevSecOps' and added security note.
There was a problem hiding this comment.
Pull Request Overview
This PR updates the README documentation for the demo_wordpress project, making improvements to formatting, organizational structure, and content. The changes modernize the project title, enhance infrastructure descriptions, and add a to-do list section.
- Updated project title and restructured author's notes into a proper "To Do List" section
- Enhanced infrastructure documentation to reference "DevSecOps" and added security note
- Removed several trailing backslashes from section headings for cleaner formatting
| - Containerization: Docker (available on request) | ||
| - Orchestration: Amazon EKS (Kubernetes) (available on request) | ||
| - Storage: Amazon S3 buckets (for media, backups, and static assets) | ||
| - Security: Additonal security can be assigned as required |
There was a problem hiding this comment.
Spelling error: "Additonal" should be "Additional".
| - Security: Additonal security can be assigned as required | |
| - Security: Additional security can be assigned as required |
| Website, Mobile App, IoT, VoiceAssistants, Kiosks, eCommerce Platforms | ||
|
|
||
| # Project Overview & Architecture \ | ||
| # Project Overview & Architecture |
There was a problem hiding this comment.
Inconsistent formatting: This line is missing the trailing backslash (\) used throughout the document for line continuations. According to the project conventions, markdown lines should use trailing backslashes for consistent formatting.
|
|
||
| AmyCN1's Notes: This architecture is fully scalable, secure, and ready for enterprise or high-traffic use cases. \ | ||
| next build GitHub Action possible with TravisCI for code validation? | ||
| AmyCN1's Notes: This architecture is fully scalable, secure, and ready for enterprise or high-traffic use cases. |
There was a problem hiding this comment.
Inconsistent formatting: This line is missing the trailing backslash (\) used throughout the document for line continuations. According to the project conventions, markdown lines should use trailing backslashes for consistent formatting.
| - Containerization: Docker (available on request) | ||
| - Orchestration: Amazon EKS (Kubernetes) (available on request) | ||
| - Storage: Amazon S3 buckets (for media, backups, and static assets) | ||
| - Security: Additonal security can be assigned as required |
There was a problem hiding this comment.
Vague and unclear content: This security note is too generic and doesn't provide actionable information. Consider specifying what types of additional security measures are available (e.g., "AWS WAF, VPC configuration, encryption at rest/in transit, DDoS protection via AWS Shield") to make this documentation more useful.
| - Security: Additonal security can be assigned as required | |
| - Security: Multiple layers of security available, including: \ | |
| - AWS WAF (Web Application Firewall) for application-layer protection \ | |
| - AWS Shield for DDoS mitigation \ | |
| - VPC (Virtual Private Cloud) configuration for network isolation \ | |
| - Encryption at rest (EBS, S3) and in transit (SSL/TLS) \ | |
| - IAM roles and policies for least-privilege access control \ | |
| - Regular automated backups and disaster recovery \ | |
| - WordPress hardening (security plugins, login rate limiting, 2FA, file permissions) \ | |
| - OS-level firewalls and patch management \ | |
| - Audit logging and monitoring via AWS CloudWatch/CloudTrail \ | |
| - Additional custom security controls available on request |
No description provided.