AWS Secrets Manager simplifies the management of sensitive information like database credentials and API keys. In Amazon EKS environments, managing these secrets can be tricky due to language-specific AWS SDK dependencies, network calls, and complex secret rotation across pods. The AWS Secrets Manager Agent provides a solution by allowing applications to retrieve secrets from a local HTTP interface instead of directly from Secrets Manager. It runs as a sidecar container in EKS, caching secrets locally and improving application availability while reducing the number of API calls. The agent uses a language-agnostic approach, enabling its use across various programming languages without needing specific SDKs. It also incorporates advanced security features, including post-quantum cryptography with ML-KEM for secure key exchange and protection against server-side request forgery (SSRF) through a unique token system. Authentication is handled via Amazon EKS Pod Identity, which simplifies the association of IAM roles with Kubernetes service accounts. To deploy the Secrets Manager Agent, you need an AWS account, an EKS cluster, and several tools like AWS CLI and Docker. The deployment involves building the agent binary, containerizing it, and configuring IAM roles for secure access to Secrets Manager. The article outlines a step-by-step installation process, including creating necessary files and commands for building and publishing the agent's Docker image, as well as creating secrets and IAM roles. This structured approach ensures secure and efficient management of application secrets within EKS.