AWS streams documentation change
Summary
Expanded infrastructure security documentation with explicit TLS requirements, cipher suite recommendations, and AWS security references
Security assessment
Added detailed security implementation requirements for network communication (TLS 1.2+/PFS ciphers) and references to AWS security frameworks. While security-related, it documents baseline practices rather than addressing a specific vulnerability.
Diff
diff --git a/streams/latest/dev/infrastructure-security.md b/streams/latest/dev/infrastructure-security.md index 51dc7e856..ad799ebd9 100644 --- a//streams/latest/dev/infrastructure-security.md +++ b//streams/latest/dev/infrastructure-security.md @@ -5 +5,9 @@ -# Infrastructure security in Kinesis Data Streams +# Infrastructure Security in Amazon Kinesis Data Streams + +As a managed service, is protected by AWS global network security. For information about AWS security services and how AWS protects infrastructure, see [AWS Cloud Security](https://aws.amazon.com/security/). To design your AWS environment using the best practices for infrastructure security, see [Infrastructure Protection](https://docs.aws.amazon.com/wellarchitected/latest/security-pillar/infrastructure-protection.html) in _Security Pillar AWS Well‐Architected Framework_. + +You use AWS published API calls to access through the network. Clients must support the following: + + * Transport Layer Security (TLS). We require TLS 1.2 and recommend TLS 1.3. + + * Cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes. @@ -7 +14,0 @@ -As a managed service, Amazon Kinesis Data Streams is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper. @@ -9 +15,0 @@ As a managed service, Amazon Kinesis Data Streams is protected by the AWS global -You use AWS published API calls to access Kinesis Data Streams 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 systems such as Java 7 and later support these modes. @@ -11 +16,0 @@ You use AWS published API calls to access Kinesis Data Streams through the netwo -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.