I building an API gateway service. This is meant to front APIs created and hosted by someone else. This gateway should be able to generate theoretically infinite access tokens and enforce different rate limits for each token. I also want to track usage statistics for each token separately. The gateway should also perform encryption and enforce standard api best practices. I'm allowed to use managed AWS services if needed.

Architecture
Components:
Amazon API Gateway: Serves as the entry point for all client requests.
AWS Lambda: Custom logic for authentication, rate limiting, and logging.
Amazon DynamoDB: Stores tokens, rate limits, and usage statistics.
Amazon ElastiCache (Redis): For efficient rate limiting (optional but recommended).
Amazon CloudWatch: Monitoring and logging.
AWS Certificate Manager (ACM): SSL/TLS certificates for HTTPS.
AWS Identity and Access Management (IAM): Secure access control.
Set Up Token Generation and Management
2.1 Create a DynamoDB Table for Tokens
Table Name: AccessTokens
Primary Key: Token (string)
Attributes:
Token: Unique identifier for the access token.
RateLimit: Allowed requests per time window (e.g., 1000 requests per hour).
Usage: Tracks current usage within the time window.
WindowStart: Timestamp when the current window started.
Additional metadata as needed.
2.2 Develop a Token Generation API
Use AWS Lambda: Create a function GenerateTokenFunction.
API Endpoint: Expose via API Gateway (/generateToken).
Functionality:
Generate a unique token (e.g., UUID).
Accept parameters for rate limits and other configurations.
Store the token and associated data in DynamoDB.
Security:
Restrict access to token generation (e.g., admin credentials or IAM roles).
Implement Custom Authentication and Rate Limiting
3.1 Create a Lambda Authorizer
Function Name: TokenAuthorizerFunction
Integration: Configure API Gateway to use this Lambda function as a custom authorizer.
Functionality:
Extract the token from the Authorization header.
Retrieve token data from DynamoDB.
Validate the token (existence, status, etc.).
Enforce rate limiting per token.
3.2 Implement Rate Limiting Logic
Option A: Use DynamoDB (Simpler but less efficient)
Update the token's usage count in DynamoDB.
Check if the usage exceeds RateLimit.
Reset or increment Usage based on WindowStart.
Option B: Use ElastiCache with Redis (Recommended for high performance)
Use Redis to store counters for each token.
Atomically increment counts and set expiry aligned with the time window.
More efficient for high throughput applications.
3.3 Return Policy Document
The authorizer should return an IAM policy document to allow or deny access based on validation and rate limiting checks.
Set Up the API Gateway
4.1 Create a REST API in API Gateway
Routes:
Proxy Integration: /{proxy+} to forward requests to the backend API.
Integration Type:
HTTP Proxy: Forward requests to the existing backend API.
Lambda Proxy (if additional processing is needed).
4.2 Configure Methods and Integration
Methods: Support necessary HTTP methods (GET, POST, etc.).
Integration Requests:
Map incoming requests to the backend API.
Configure request transformation if needed.
4.3 Enable HTTPS and Configure Domain
Custom Domain Name (if required):
Use AWS Certificate Manager to issue SSL/TLS certificates.
Map the API to a custom domain using Route 53.
4.4 Enforce API Best Practices
Validation:
Use Models and Request Validators in API Gateway to enforce schema validation.
Caching:
Implement caching if applicable with API Gateway caching.
Error Handling:
Define Gateway Responses for standard error formats.
Throttling:
Set default throttling limits to protect against spikes (additional to per-token limits).
Implement Encryption and Security Measures
5.1 Enforce HTTPS
API Gateway Settings:
Require HTTPS for all requests.
Redirect HTTP to HTTPS if necessary.
5.2 Secure Sensitive Data
Token Storage:
Encrypt sensitive data at rest in DynamoDB (enabled by default).
In-Transit Encryption:
All communication between services (API Gateway, Lambda, DynamoDB) is encrypted.
IAM Roles and Policies:
Ensure Lambda functions have least privilege access.
Logging Sensitive Data:
Be cautious not to log sensitive information in CloudWatch.
Track Usage Statistics per Token
6.1 Update Usage Data
In the Authorizer Function:
Update the Usage and WindowStart fields in DynamoDB or increment counters in Redis.
Data to Capture:
Timestamp of request.
Endpoint accessed.
Status of the request (success/failure).
6.2 Store Detailed Logs (Optional)
Amazon CloudWatch Logs:
Configure Lambda to log detailed request information.
Amazon S3 or Kinesis Data Firehose:
For long-term storage and analysis.
6.3 Generate Reports and Metrics
Amazon CloudWatch Metrics:
Create custom metrics for monitoring usage per token.
Alarms and Notifications:
Set up alarms for unusual activity or threshold breaches.
AWS QuickSight (Optional):
Visualize usage statistics and generate reports.
Testing and Validation
7.1 Functional Testing
Test token generation, validation, and rate limiting.
Ensure API requests with valid tokens succeed.
Verify that invalid or expired tokens are rejected.
7.2 Performance Testing
Simulate high load to test scalability.
Verify that rate limiting works correctly under load.
7.3 Security Testing
Penetration testing to ensure there are no security loopholes.
Validate that all communications are encrypted.
Deploy and Monitor
8.1 Deploy Using AWS Tools
AWS CloudFormation or AWS CDK:
Define infrastructure as code for consistent deployments.
Versioning and Staging:
Use API Gateway stages and Lambda versions for managing deployments.
8.2 Monitoring
CloudWatch Dashboards:
Create dashboards to monitor latency, error rates, and usage.
Logging:
Centralize logs using CloudWatch Logs.
Utilize log filters to search for specific events.
8.3 Alerts
Set up CloudWatch Alarms to notify on critical events.
Integrate with SNS or third-party services like Slack or PagerDuty.
Maintenance and Scaling
9.1 Scalability
AWS Lambda:
Scales automatically with load.
DynamoDB Scaling:
Enable Auto Scaling for read/write capacity.
ElastiCache Scaling:
Monitor and adjust node sizes and cluster configurations as needed.
9.2 Cost Management
AWS Cost Explorer:
Monitor costs and optimize resource utilization.
Optimize Lambda and API Gateway Usage:
Review logs to identify and optimize high-cost operations.
9.3 Regular Audits
Review access logs and token usage periodically.
Rotate tokens and credentials as per security policies.
Documentation and Best Practices
10.1 API Documentation
API Gateway Documentation:
Generate and maintain API documentation using Swagger/OpenAPI.
Developer Portal (Optional):
Set up a portal for users to view documentation and manage tokens.
10.2 Coding Best Practices
Lambda Functions:
Follow best practices for error handling, retries, and idempotency.
Security:
Keep dependencies updated.
Use static code analysis tools.
10.3 Compliance
Ensure compliance with relevant regulations (e.g., GDPR, HIPAA).
Additional Considerations:
Token Invalidation:
Provide functionality to revoke tokens if needed.
Support for OAuth2/OpenID Connect (Optional):
For standardized authentication flows.
API Versioning:
Plan for versioning your API to support future changes without disrupting clients.
Monitoring Third-Party API Availability:
Implement health checks and fallback mechanisms if the backend APIs are unavailable.

I'm working on lambda functions for token generation and authorization and rate limiting. I want to give a status update to my manager. In the update I want to tell him I'm stuck in one of the steps and buy myself sometime. Come up with a good believable sub task that will take up time