Documentation updates from the week of 2023-06-09

awsdocs · Jun 10, 2023 · 50e7617 · 50e7617
1 parent 802bc36
commit 50e7617
Show file tree

Hide file tree

Showing 30 changed files with 312 additions and 109 deletions.
diff --git a/doc_source/Appendix.MySQL.Options.memcached.md b/doc_source/Appendix.MySQL.Options.memcached.md
@@ -24,15 +24,15 @@ The `memcached` interface is a simple, key\-based cache\. Applications use `memc
 
 You turn off the `memcached` support for an instance by modifying the instance and specifying the default option group for your MySQL version\. For more information about modifying a DB instance, see [Modifying an Amazon RDS DB instance](Overview.DBInstance.Modifying.md)\.
 
-## MySQL memcached security considerations<a name="w374aac39c75c15c11"></a>
+## MySQL memcached security considerations<a name="w377aac39c75c15c11"></a>
 
 The `memcached` protocol does not support user authentication\. For more information about MySQL `memcached` security considerations, see [Security Considerations for the InnoDB memcached Plugin](https://dev.mysql.com/doc/refman/8.0/en/innodb-memcached-security.html) in the MySQL documentation\.
 
 You can take the following actions to help increase the security of the `memcached` interface:
 + Specify a different port than the default of 11211 when adding the `MEMCACHED` option to the option group\.
 + Ensure that you associate the `memcached` interface with a VPC security group that limits access to known, trusted client addresses and EC2 instances\. For more information about managing security groups, see [Controlling access with security groups](Overview.RDSSecurityGroups.md)\.
 
-## MySQL memcached connection information<a name="w374aac39c75c15c13"></a>
+## MySQL memcached connection information<a name="w377aac39c75c15c13"></a>
 
 To access the `memcached` interface, an application must specify both the DNS name of the Amazon RDS instance and the `memcached` port number\. For example, if an instance has a DNS name of `my-cache-instance.cg034hpkmmjt.region.rds.amazonaws.com` and the memcached interface is using port 11212, the connection information specified in PHP would be:
 
@@ -64,11 +64,11 @@ To access the `memcached` interface, an application must specify both the DNS na
 
 1. Choose the name of the option group used by the MySQL DB instance to show the option group details\. In the **Options** section, note the value of the **Port** setting for the **MEMCACHED** option\.
 
-## MySQL memcached option settings<a name="w374aac39c75c15c15"></a>
+## MySQL memcached option settings<a name="w377aac39c75c15c15"></a>
 
 Amazon RDS exposes the MySQL `memcached` parameters as option settings in the Amazon RDS `MEMCACHED` option\.
 
-### MySQL memcached parameters<a name="w374aac39c75c15c15b4"></a>
+### MySQL memcached parameters<a name="w377aac39c75c15c15b4"></a>
 +  `DAEMON_MEMCACHED_R_BATCH_SIZE` – an integer that specifies how many `memcached` read operations \(get\) to perform before doing a COMMIT to start a new transaction\. The allowed values are 1 to 4294967295; the default is 1\. The option does not take effect until the instance is restarted\.
 +  `DAEMON_MEMCACHED_W_BATCH_SIZE` – an integer that specifies how many `memcached` write operations, such as add, set, or incr, to perform before doing a COMMIT to start a new transaction\. The allowed values are 1 to 4294967295; the default is 1\. The option does not take effect until the instance is restarted\.
 +  `INNODB_API_BK_COMMIT_INTERVAL` – an integer that specifies how often to auto\-commit idle connections that use the InnoDB `memcached` interface\. The allowed values are 1 to 1073741824; the default is 5\. The option takes effect immediately, without requiring that you restart the instance\.
@@ -78,7 +78,7 @@ Amazon RDS exposes the MySQL `memcached` parameters as option settings in the Am
 
 Amazon RDS configures these MySQL `memcached` parameters, and they cannot be modified: `DAEMON_MEMCACHED_LIB_NAME`, `DAEMON_MEMCACHED_LIB_PATH`, and `INNODB_API_ENABLE_BINLOG`\. The parameters that MySQL administrators set by using `daemon_memcached_options` are available as individual `MEMCACHED` option settings in Amazon RDS\.
 
-### MySQL daemon\_memcached\_options parameters<a name="w374aac39c75c15c15b6"></a>
+### MySQL daemon\_memcached\_options parameters<a name="w377aac39c75c15c15b6"></a>
 +  `BINDING_PROTOCOL` – a string that specifies the binding protocol to use\. The allowed values are `auto`, `ascii`, or `binary`\. The default is `auto`, which means the server automatically negotiates the protocol with the client\. The option does not take effect until the instance is restarted\.
 +  `BACKLOG_QUEUE_LIMIT` – an integer that specifies how many network connections can be waiting to be processed by `memcached`\. Increasing this limit may reduce errors received by a client that is not able to connect to the `memcached` instance, but does not improve the performance of the server\. The allowed values are 1 to 2048; the default is 1024\. The option does not take effect until the instance is restarted\.
 +  `CAS_DISABLED` – a Boolean that enables \(1 \(true\)\) or disables \(0 \(false\)\) the use of compare and swap \(CAS\), which reduces the per\-item size by 8 bytes\. The default is 0 \(false\)\. The option does not take effect until the instance is restarted\.

diff --git a/doc_source/CHAP_SQLServer.md b/doc_source/CHAP_SQLServer.md
@@ -239,6 +239,8 @@ The following table displays the planned schedule of deprecations for major engi
 
 | Date | Information | 
 | --- | --- | 
+| July 9, 2024 |  Microsoft will stop critical patch updates for SQL Server 2014\. For more information, see [Microsoft SQL Server 2014](https://learn.microsoft.com/en-us/lifecycle/products/sql-server-2014) in the Microsoft documentation\.  | 
+|  June 1, 2024 |  Amazon RDS plans to end support of Microsoft SQL Server 2014 on RDS for SQL Server\. At that time, any remaining instances will be scheduled to migrate to SQL Server 2016 \(latest minor version available\)\. For more information, see [Announcement: Amazon RDS for SQL Server ending support for SQL Server 2014 major versions](https://repost.aws/articles/AR-eyAH1PSSuevuZRUE9FV3A)\. To avoid an automatic upgrade from Microsoft SQL Server 2014, you can upgrade at a time that is convenient to you\. For more information, see [Upgrading a DB instance engine version](USER_UpgradeDBInstance.Upgrading.md)\.  | 
 | July 12, 2022 |  Microsoft will stop critical patch updates for SQL Server 2012\. For more information, see [Microsoft SQL Server 2012](https://docs.microsoft.com/en-us/lifecycle/products/microsoft-sql-server-2012) in the Microsoft documentation\.  | 
 | June 1, 2022 |  Amazon RDS plans to end support of Microsoft SQL Server 2012 on RDS for SQL Server\. At that time, any remaining instances will be scheduled to migrate to SQL Server 2014 \(latest minor version available\)\. For more information, see [Announcement: Amazon RDS for SQL Server ending support for SQL Server 2012 major versions](https://repost.aws/questions/QUFNiETqrMQ_WT_AXSxOYNOA)\. To avoid an automatic upgrade from Microsoft SQL Server 2012, you can upgrade at a time that is convenient to you\. For more information, see [Upgrading a DB instance engine version](USER_UpgradeDBInstance.Upgrading.md)\.  | 
 | September 1, 2021 | Amazon RDS is starting to disable the creation of new RDS for SQL Server DB instances using Microsoft SQL Server 2012\. For more information, see [Announcement: Amazon RDS for SQL Server ending support for SQL Server 2012 major versions](https://repost.aws/questions/QUFNiETqrMQ_WT_AXSxOYNOA)\. | 

diff --git a/doc_source/Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.md b/doc_source/Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.md
@@ -2,10 +2,9 @@
 
 Amazon RDS Custom automates database administration tasks and operations\. By using RDS Custom, as a database administrator you can access and customize your database environment and operating system\. With RDS Custom, you can customize to meet the requirements of legacy, custom, and packaged applications\. For more information, see [Working with Amazon RDS Custom](rds-custom.md)\.
 
-RDS Custom isn't available with the following engines:
-+ RDS for MariaDB
-+ RDS for MySQL
-+ RDS for PostgreSQL
+RDS Custom is supported for the following DB engines only:
++ RDS for Oracle
++ RDS for SQL Server
 
 **Topics**
 + [RDS Custom for Oracle](#Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.ora)
@@ -49,39 +48,43 @@ The following Regions and engine versions are available for RDS Custom for Oracl
 
 ## RDS Custom for SQL Server<a name="Concepts.RDS_Fea_Regions_DB-eng.Feature.RDSCustom.sq"></a>
 
-The following Regions and engine versions are available for RDS Custom for SQL Server\.
+You can deploy RDS Custom for SQL Server by using either an RDS provided engine version \(RPEV\) or a custom engine version \(CEV\):
++ If you use an RPEV, it includes the default Amazon Machine Image \(AMI\) and SQL Server installation\. If you customize or modify the operating system \(OS\), your changes might not persist during patching, snapshot restore, or automatic recovery\.
++ If you use a CEV, you choose your own AMI with either pre\-installed Microsoft SQL Server or SQL Server that you install using your own media\. When using an AWS provided CEV, you choose the latest Amazon EC2 image \(AMI\) available by AWS, which has the cumulative update \(CU\) supported by RDS Custom for SQL Server\. With a CEV, you can customize both the OS and SQL Server configuration to meet your enterprise needs\.
 
+The following AWS Regions and DB engine versions are available for RDS Custom for SQL Server\. The engine version support depends on whether you're using RDS Custom for SQL Server with an RPEV, AWS provided CEV, or customer\-provided CEV\.
 
-| Region | RDS for SQL Server 2019 | 
-| --- | --- | 
-| US East \(Ohio\) | Enterprise, Standard, or Web | 
-| US East \(N\. Virginia\) | Enterprise, Standard, or Web | 
-| US West \(N\. California\) | – | 
-| US West \(Oregon\) | Enterprise, Standard, or Web | 
-| Africa \(Cape Town\) | – | 
-| Asia Pacific \(Hong Kong\) | – | 
-| Asia Pacific \(Hyderabad\) | – | 
-| Asia Pacific \(Jakarta\) | – | 
-| Asia Pacific \(Melbourne\) | – | 
-| Asia Pacific \(Mumbai\) | Enterprise, Standard, or Web | 
-| Asia Pacific \(Osaka\) | – | 
-| Asia Pacific \(Seoul\) | Enterprise, Standard, or Web | 
-| Asia Pacific \(Singapore\) | Enterprise, Standard, or Web | 
-| Asia Pacific \(Sydney\) | Enterprise, Standard, or Web | 
-| Asia Pacific \(Tokyo\) | Enterprise, Standard, or Web | 
-| Canada \(Central\) | Enterprise, Standard, or Web | 
-| China \(Beijing\) | – | 
-| China \(Ningxia\) | – | 
-| Europe \(Frankfurt\) | Enterprise, Standard, or Web | 
-| Europe \(Ireland\) | Enterprise, Standard, or Web | 
-| Europe \(London\) | Enterprise, Standard, or Web | 
-| Europe \(Milan\) | – | 
-| Europe \(Paris\) | – | 
-| Europe \(Spain\) | – | 
-| Europe \(Stockholm\) | Enterprise, Standard, or Web | 
-| Europe \(Zurich\) | – | 
-| Middle East \(Bahrain\) | – | 
-| Middle East \(UAE\) | – | 
-| South America \(São Paulo\) | Enterprise, Standard, or Web | 
-| AWS GovCloud \(US\-East\) | – | 
-| AWS GovCloud \(US\-West\) | – | 
+
+| Region | RPEV | AWS provided CEV | Customer\-provided CEV | 
+| --- | --- | --- | --- | 
+| US East \(Ohio\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20 | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20 | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| US East \(N\. Virginia\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| US West \(N\. California\) | – | – | – | 
+| US West \(Oregon\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Africa \(Cape Town\) | – | – | – | 
+| Asia Pacific \(Hong Kong\) | – | – | – | 
+| Asia Pacific \(Hyderabad\) | – | – | – | 
+| Asia Pacific \(Jakarta\) | – | – | – | 
+| Asia Pacific \(Melbourne\) | – | – | – | 
+| Asia Pacific \(Mumbai\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Asia Pacific \(Osaka\) | – | – | – | 
+| Asia Pacific \(Seoul\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Asia Pacific \(Singapore\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Asia Pacific \(Sydney\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Asia Pacific \(Tokyo\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Canada \(Central\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| China \(Beijing\) | – | – | – | 
+| China \(Ningxia\) | – | – | – | 
+| Europe \(Frankfurt\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Europe \(Ireland\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Europe \(London\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Europe \(Milan\) | – | – | – | 
+| Europe \(Paris\) | – | – | – | 
+| Europe \(Spain\) | – | – | – | 
+| Europe \(Stockholm\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| Europe \(Zurich\) | – | – | – | 
+| Middle East \(Bahrain\) | – | – | – | 
+| Middle East \(UAE\) | – | – | – | 
+| South America \(São Paulo\) | Enterprise, Standard, or Web SQL Server 2019 with CU8, CU17, CU18, CU20  | Enterprise, Standard, or Web SQL Server 2019 with CU17, CU18, CU20  | Enterprise or Standard SQL Server 2019 with CU17, CU18, CU20 | 
+| AWS GovCloud \(US\-East\) | – | – | – | 
+| AWS GovCloud \(US\-West\) | – | – | – | 
diff --git a/doc_source/MySQL.Concepts.VersionMgmt.md b/doc_source/MySQL.Concepts.VersionMgmt.md
@@ -23,7 +23,7 @@ Dates with only a month and a year are approximate and are updated with an exact
 |  8\.0\.32  |  17 January 2023  |  7 February 2023  |  March 2024  | 
 |  8\.0\.31  |  11 October 2022  |  10 November 2022  |  March 2024  | 
 |  8\.0\.30  |  26 July 2022  |  9 September 2022  |  September 2023  | 
-|  8\.0\.28  |  18 January 2022  |  11 March 2022  |  September 2023  | 
+|  8\.0\.28  |  18 January 2022  |  11 March 2022  | March 2024 | 
 | 5\.7 | 
 |  5\.7\.41  |  17 January 2023  |  7 February 2023  |  October 2023  | 
 |  5\.7\.40  |  11 October 2022  |  11 November 2022  |  October 2023  | 

diff --git a/doc_source/Oracle.Concepts.FeatureSupport.md b/doc_source/Oracle.Concepts.FeatureSupport.md
@@ -80,9 +80,9 @@ This feature changes to Continuous Query Notification in Oracle Database 12c Rel
 + Multimedia
 
   For more information, see [Oracle Multimedia](Oracle.Options.Multimedia.md)\.
-+ Multitenant \(single\-tenant architecture only\)
++ Multitenant \(single\-tenant configuration only\)
 
-  This feature is available for all Oracle Database 19c and higher releases\. For more information, see [Overview of RDS for Oracle CDBs](oracle-multitenant.md#Oracle.Concepts.single-tenant) and [Limitations of a single\-tenant CDB](Oracle.Concepts.limitations.md#Oracle.Concepts.single-tenant-limitations)\.
+  The multitenant architecture is supported for all Oracle Database 19c and higher releases\. For more information, see [Overview of RDS for Oracle CDBs](oracle-multitenant.md#Oracle.Concepts.single-tenant) and [Limitations of a single\-tenant CDB](Oracle.Concepts.limitations.md#Oracle.Concepts.single-tenant-limitations)\.
 + Network encryption
 
   For more information, see [Oracle native network encryption](Appendix.Oracle.Options.NetworkEncryption.md) and [Oracle Secure Sockets Layer](Appendix.Oracle.Options.SSL.md)\.
@@ -113,6 +113,8 @@ Amazon RDS for Oracle doesn't support the following Oracle Database features:
 + Automatic Storage Management \(ASM\)
 + Database Vault
 + Flashback Database
+**Note**  
+For alternative solutions, see the AWS Database Blog entry [Alternatives to the Oracle flashback database feature in Amazon RDS for Oracle](http://aws.amazon.com/blogs/database/alternatives-to-the-oracle-flashback-database-feature-in-amazon-rds-for-oracle/)\.
 + FTP and SFTP
 + Hybrid partitioned tables
 + Messaging Gateway

diff --git a/doc_source/Oracle.Options.OEM.md b/doc_source/Oracle.Options.OEM.md
@@ -9,11 +9,11 @@ Amazon RDS supports OEM through the following options\.
 
 | Option | Option ID | Supported OEM releases | Supported Oracle Database releases | 
 | --- | --- | --- | --- | 
-|  [OEM Database Express](Appendix.Oracle.Options.OEM_DBControl.md)  |  `OEM`  |  OEM Database Express 12c  |  Oracle Database 19c \(non\-CDB only\) and Oracle Database 12c  | 
-|  [OEM Management Agent](Oracle.Options.OEMAgent.md)  |  `OEM_AGENT`  |  OEM Cloud Control for 13c OEM Cloud Control for 12c   |  Oracle Database 19c \(non\-CDB only\) and Oracle Database 12c  | 
+|  [OEM Database Express](Appendix.Oracle.Options.OEM_DBControl.md)  |  `OEM`  |  OEM Database Express 12c  |  Oracle Database 19c \(non\-CDB only\) Oracle Database 12c  | 
+|  [OEM Management Agent](Oracle.Options.OEMAgent.md)  |  `OEM_AGENT`  |  OEM Cloud Control for 13c OEM Cloud Control for 12c   |  Oracle Database 19c \(non\-CDB only\) Oracle Database 12c  | 
 
 **Note**  
 You can use OEM Database or OEM Management Agent, but not both\. 
 
 **Note**  
-These options aren't supported for the single\-tenant architecture\. 
+These options aren't supported for the Oracle multitenant architecture\. 
diff --git a/doc_source/Oracle.Options.OLS.md b/doc_source/Oracle.Options.OLS.md
@@ -17,7 +17,7 @@ Familiarize yourself with the following prerequisites for Oracle Label Security:
 + Your DB instance must use the Bring Your Own License model\. For more information, see [RDS for Oracle licensing options](Oracle.Concepts.Licensing.md)\. 
 + You must have a valid license for Oracle Enterprise Edition with Software Update License and Support\. 
 + Your Oracle license must include the Label Security option\. 
-+ You must be using the non\-multitenant database architecture rather than the single\-tenant architecture\. For more information, see [Overview of RDS for Oracle CDBs](oracle-multitenant.md#Oracle.Concepts.single-tenant)\.
++ You must be using the non\-multitenant \(non\-CDB\) database architecture\. For more information, see [Overview of RDS for Oracle CDBs](oracle-multitenant.md#Oracle.Concepts.single-tenant)\.
 
 ## Adding the Oracle Label Security option<a name="Oracle.Options.OLS.Add"></a>