forked from docs/doc-exports
Wang , Deng Ke
166ff0f192
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
33 lines
2.8 KiB
HTML
33 lines
2.8 KiB
HTML
<a name="rds_07_0003"></a><a name="rds_07_0003"></a>
|
|
|
|
<h1 class="topictitle1">RDS Custom Policies</h1>
|
|
<div id="body1559186438461"><p class="MsoNormal" id="rds_07_0003__p10675105311117">Custom policies can be created to supplement the system policies of <span class="keyword" id="rds_07_0003__keyword1520081015588">RDS</span>. </p>
|
|
<p id="rds_07_0003__p7233955171110">You can create custom policies in either of the following two ways:</p>
|
|
<ul id="rds_07_0003__ul023410556110"><li id="rds_07_0003__li823412552112">Visual editor: Select cloud services, actions, resources, and request conditions without the need to know policy syntax.</li><li id="rds_07_0003__li1723415554114">JSON: Edit JSON policies from scratch or based on an existing policy.</li></ul>
|
|
<p id="rds_07_0003__p1870153144">For details, see <a href="https://docs.otc.t-systems.com/usermanual/iam/en-us_topic_0274187246.html" target="_blank" rel="noopener noreferrer">Creating a Custom Policy</a>. The following section contains examples of common RDS custom policies.</p>
|
|
<div class="section" id="rds_07_0003__en-us_topic_0172661626_section7689721"><h4 class="sectiontitle">Example Custom Policies</h4><ul id="rds_07_0003__en-us_topic_0172661626_ul40462633"><li id="rds_07_0003__en-us_topic_0172661626_li28619382">Example 1: Allowing users to create RDS DB instances<pre class="codeblock" id="rds_07_0003__codeblock2950151332118">{
|
|
"Version": "1.1",
|
|
"Statement": [{
|
|
"Effect": "Allow",
|
|
"Action": ["rds:instance:create"]
|
|
}]
|
|
}</pre>
|
|
</li><li id="rds_07_0003__en-us_topic_0172661626_li36468595">Example 2: Denying RDS DB instance deletion<p id="rds_07_0003__en-us_topic_0172661626_p59781901"><a name="rds_07_0003__en-us_topic_0172661626_li36468595"></a><a name="en-us_topic_0172661626_li36468595"></a>A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user include both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.</p>
|
|
<p id="rds_07_0003__en-us_topic_0172661626_p1166200">The following method can be used if you need to assign permissions of the <strong id="rds_07_0003__b565292410472">RDS FullAccess</strong> policy to a user but you want to prevent the user from deleting RDS DB instances. Create a custom policy for denying RDS DB instance deletion, and attach both policies to the group the user belongs to. Then, the user can perform all operations on RDS DB instances except deleting RDS DB instances. The following is an example deny policy:</p>
|
|
<pre class="codeblock" id="rds_07_0003__codeblock154531756192113">{
|
|
"Version": "1.1",
|
|
"Statement": [{
|
|
"Action": ["rds:instance:delete"],
|
|
"Effect": "Deny"
|
|
}]
|
|
}</pre>
|
|
</li></ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rds_07_0000.html">Permissions Management</a></div>
|
|
</div>
|
|
</div>
|
|
|