aws rds create-db-proxy-endpoint
Creates a DBProxyEndpoint. Only applies to proxies that are associated with Aurora DB clusters. You can use DB proxy endpoints to specify read/write or read-only access to the DB cluster. You can also use DB proxy endpoints to access a DB proxy through a different VPC than the proxy's default VPC
Options
| Name | Description |
|---|---|
--db-proxy-name <string> | The name of the DB proxy associated with the DB proxy endpoint that you create |
--db-proxy-endpoint-name <string> | The name of the DB proxy endpoint to create |
--vpc-subnet-ids <list> | The VPC subnet IDs for the DB proxy endpoint that you create. You can specify a different set of subnet IDs than for the original DB proxy |
--vpc-security-group-ids <list> | The VPC security group IDs for the DB proxy endpoint that you create. You can specify a different set of security group IDs than for the original DB proxy. The default is the default security group for the VPC |
--target-role <string> | A value that indicates whether the DB proxy endpoint can be used for read/write or read-only operations. The default is READ_WRITE |
--tags <list> | A list of tags. For more information, see Tagging Amazon RDS Resources in the Amazon RDS User Guide |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally |
--generate-cli-skeleton <string> | Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value ``input``, prints a sample input JSON that can be used as an argument for ``--cli-input-json``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |