Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for Security Enhancements in the Serverless Architecture #292

Open
cncoder opened this issue Apr 23, 2024 · 0 comments
Open

Proposal for Security Enhancements in the Serverless Architecture #292

cncoder opened this issue Apr 23, 2024 · 0 comments

Comments

@cncoder
Copy link

cncoder commented Apr 23, 2024

To improve the security posture and reduce the attack surface of the serverless architecture, I propose implementing the following security enhancements:

  1. Network Isolation and Access Control:
  • Deploy the frontend web and API Gateway in private subnets within an Amazon VPC.
  • Strictly control inbound traffic using Security Groups and Network ACLs, allowing access only for authorized users or devices via VPN or AWS Direct Connect.
  • Consider using an Application Load Balancer in front of your Lambda functions, which would be the recommended approach for securely exposing Lambda functions without exposing them directly to the internet.
  1. Lambda Function Security Hardening:
  • Deploy Lambda functions in private VPC subnets, accessing services like SageMaker and Bedrock through VPC Endpoints, eliminating the need for public internet access.
  • Follow the principle of least privilege, granting the Lambda execution role only the necessary permissions to access required AWS services.
  1. CDK Deployment Script Permission Optimization:
  • Adhere to the principle of least privilege, granting the IAM roles required for CDK deployment scripts only the minimal necessary permissions.
  • The current documentation uses admin access, which poses a security risk, and permissions should be refined.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant