Q. What’s the difference between Parameter Store and AWS Secrets Manager?
Secrets Manager is more advanced (auto-rotation, RDS integration), while Parameter Store is simpler and cheaper, suitable for most configs.
Q. How do you handle sensitive parameters like passwords?
Store them as “SecureString” in Parameter Store with KMS encryption, and ensure the Beanstalk EC2 role has IAM permission to decrypt.
Q. How can Elastic Beanstalk apps access parameters?
By using the AWS SDK in application code, or by configuring environment variables at runtime that read from Parameter Store.
Q. Why use Parameter Store with Elastic Beanstalk?
It centralizes config management, keeps secrets secure, and makes apps portable across environments.
Q. What is AWS SSM Parameter Store?
It’s a secure service for storing configuration values and secrets, such as DB credentials or API keys.
Q. What are best practices for NestJS microservices on Beanstalk?
Use separate environments per microservice Store secrets in AWS Parameter Store Monitor with CloudWatch Automate deployments with CI/CD pipelines
Q. How do you manage inter-service communication in this architecture?
Use AWS VPC networking, service discovery (via DNS or API Gateway), and message brokers like SQS or SNS.
Q. How does Elastic Beanstalk handle scaling?
It auto-scales based on CPU, memory, or custom CloudWatch metrics to match demand.
Q. How do you configure microservices on Elastic Beanstalk?
Each microservice can be packaged as a Docker container and deployed as an independent environment in Elastic Beanstalk.
Q. Why use AWS Elastic Beanstalk for NestJS microservices?
Elastic Beanstalk automates deployment, scaling, and health monitoring, which simplifies managing distributed microservices.