# Infrastructure security in Elastic Beanstalk
<a name="infrastructure-security"></a>

As a managed service, AWS Elastic Beanstalk is protected by the AWS global network security procedures that are described in our [ Best Practices for Security, Identity, and Compliance](https://aws.amazon.com/architecture/security-identity-compliance) website.

You use AWS published API calls to access Elastic Beanstalk through the network. Clients must support Transport Layer Security (TLS) 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS), such as Ephemeral Diffie-Hellman (DHE) or Elliptic Curve Ephemeral Diffie-Hellman (ECDHE). Most modern platforms support these modes.

Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html) (AWS STS) to generate temporary security credentials to sign requests.

For other Elastic Beanstalk security topics, see [AWS Elastic Beanstalk security](security.md).