쿠키 기본 설정 선택

당사는 사이트와 서비스를 제공하는 데 필요한 필수 쿠키 및 유사한 도구를 사용합니다. 고객이 사이트를 어떻게 사용하는지 파악하고 개선할 수 있도록 성능 쿠키를 사용해 익명의 통계를 수집합니다. 필수 쿠키는 비활성화할 수 없지만 '사용자 지정' 또는 ‘거부’를 클릭하여 성능 쿠키를 거부할 수 있습니다.

사용자가 동의하는 경우 AWS와 승인된 제3자도 쿠키를 사용하여 유용한 사이트 기능을 제공하고, 사용자의 기본 설정을 기억하고, 관련 광고를 비롯한 관련 콘텐츠를 표시합니다. 필수가 아닌 모든 쿠키를 수락하거나 거부하려면 ‘수락’ 또는 ‘거부’를 클릭하세요. 더 자세한 내용을 선택하려면 ‘사용자 정의’를 클릭하세요.

RDS Database Stack | Create from Backup

포커스 모드
RDS Database Stack | Create from Backup - AMS Advanced Change Type Reference
이 페이지는 귀하의 언어로 번역되지 않았습니다. 번역 요청

Create an Amazon Relational Database Service (RDS) from a backup. When you restore a backup this way, the service-specific restore parameters are presented automatically.

Full classification: Deployment | Advanced stack components | RDS database stack | Create from backup

Change Type Details

Change type ID

ct-0pgvtw5rpcsb6

Current version

1.0

Expected execution duration

360 minutes

AWS approval

Required

Customer approval

Not required

Execution mode

Automated

Additional Information

Create DB stack from backup

Screenshot of this change type, in the AMS console:

Console interface for creating an Amazon RDS instance from a backup, showing description and version details.

How it works:

  1. Navigate to the Create RFC page: In the left navigation pane of the AMS console click RFCs to open the RFCs list page, and then click Create RFC.

  2. Choose a popular change type (CT) in the default Browse change types view, or select a CT in the Choose by category view.

    • Browse by change type: You can click on a popular CT in the Quick create area to immediately open the Run RFC page. Note that you cannot choose an older CT version with quick create.

      To sort CTs, use the All change types area in either the Card or Table view. In either view, select a CT and then click Create RFC to open the Run RFC page. If applicable, a Create with older version option appears next to the Create RFC button.

    • Choose by category: Select a category, subcategory, item, and operation and the CT details box opens with an option to Create with older version if applicable. Click Create RFC to open the Run RFC page.

  3. On the Run RFC page, open the CT name area to see the CT details box. A Subject is required (this is filled in for you if you choose your CT in the Browse change types view). Open the Additional configuration area to add information about the RFC.

    In the Execution configuration area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the Additional configuration area.

  4. When finished, click Run. If there are no errors, the RFC successfully created page displays with the submitted RFC details, and the initial Run output.

  5. Open the Run parameters area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.

Screenshot of this change type, in the AMS console:

Console interface for creating an Amazon RDS instance from a backup, showing description and version details.

How it works:

  1. Navigate to the Create RFC page: In the left navigation pane of the AMS console click RFCs to open the RFCs list page, and then click Create RFC.

  2. Choose a popular change type (CT) in the default Browse change types view, or select a CT in the Choose by category view.

    • Browse by change type: You can click on a popular CT in the Quick create area to immediately open the Run RFC page. Note that you cannot choose an older CT version with quick create.

      To sort CTs, use the All change types area in either the Card or Table view. In either view, select a CT and then click Create RFC to open the Run RFC page. If applicable, a Create with older version option appears next to the Create RFC button.

    • Choose by category: Select a category, subcategory, item, and operation and the CT details box opens with an option to Create with older version if applicable. Click Create RFC to open the Run RFC page.

  3. On the Run RFC page, open the CT name area to see the CT details box. A Subject is required (this is filled in for you if you choose your CT in the Browse change types view). Open the Additional configuration area to add information about the RFC.

    In the Execution configuration area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the Additional configuration area.

  4. When finished, click Run. If there are no errors, the RFC successfully created page displays with the submitted RFC details, and the initial Run output.

  5. Open the Run parameters area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.

How it works:

  1. Use either the Inline Create (you issue a create-rfc command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the create-rfc command with the two files as input. Both methods are described here.

  2. Submit the RFC: aws amscm submit-rfc --rfc-id ID command with the returned RFC ID.

    Monitor the RFC: aws amscm get-rfc --rfc-id ID command.

To check the change type version, use this command:

aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
Note

You can use any CreateRfc parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}" to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference.

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:

aws amscm create-rfc \ --change-type-id "ct-0pgvtw5rpcsb6" \ --change-type-version "1.0" --title "Create RDS From Backup" \ --execution-parameters "{\"Description\":\"Create RDS Instance Stack from Backup: awsbackup:job-00000000-0000-0000-0000-000000000.\",\"VpcId\":\"vpc-00000000\",\"StackTemplateId\":\"stm-siqajx00000000000\",\"Name\":\"restoredb\",\"TimeoutInMinutes\":360,\"Parameters\":{\"DBSnapshotIdentifier\":\"awsbackup:job-00000000-0000-0000-0000-000000000\",\"DBSubnetIds\":[\"subnet-79663144\", \"subnet-d0cf52fa\"]}}"

TEMPLATE CREATE:

  1. Output the execution parameters JSON schema for this change type to a JSON file; this example names it CreateRdsFromBackupParams.json:

    aws amscm get-change-type-version --change-type-id "ct-0g690ekkyfm79" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateRdsFromBackupParams.json
  2. Modify and save the CreateRdsFromBackupParams file.

    { "Description": "Create RDS Instance Stack from Backup: awsbackup:job-00000000-0000-0000-0000-000000000.", "VpcId": "vpc-00000000", "StackTemplateId": "stm-siqajx00000000000", "Name": "Stack Name", "TimeoutInMinutes": 360, "Parameters": { "DBSnapshotIdentifier": "awsbackup:job-00000000-0000-0000-0000-000000000", "DBSubnetIds": ["subnet-79663144", "subnet-d0cf52fa"] } }
  3. Output the RFC template to a file in your current folder; this example names it CreateRdsFromBackupRfc.json:

    aws amscm create-rfc --generate-cli-skeleton > CreateRdsFromBackupRfc.json
  4. Modify and save the CreateRdsFromBackupRfc.json file. For example, you can replace the contents with something like this:

    { "ChangeTypeId": "ct-0pgvtw5rpcsb6", "ChangeTypeVersion": "1.0", "Title": "Create RDS Instance Stack from Backup" }
  5. Create the RFC, specifying the CreateRdsFromBackupRfc file and the CreateRdsFromBackupParams file:

    aws amscm create-rfc --cli-input-json file://CreateRdsFromBackupRfc.json --execution-parameters file://CreateRdsFromBackupParams.json

    You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.

How it works:

  1. Use either the Inline Create (you issue a create-rfc command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the create-rfc command with the two files as input. Both methods are described here.

  2. Submit the RFC: aws amscm submit-rfc --rfc-id ID command with the returned RFC ID.

    Monitor the RFC: aws amscm get-rfc --rfc-id ID command.

To check the change type version, use this command:

aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
Note

You can use any CreateRfc parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, --notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}" to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the AMS Change Management API Reference.

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:

aws amscm create-rfc \ --change-type-id "ct-0pgvtw5rpcsb6" \ --change-type-version "1.0" --title "Create RDS From Backup" \ --execution-parameters "{\"Description\":\"Create RDS Instance Stack from Backup: awsbackup:job-00000000-0000-0000-0000-000000000.\",\"VpcId\":\"vpc-00000000\",\"StackTemplateId\":\"stm-siqajx00000000000\",\"Name\":\"restoredb\",\"TimeoutInMinutes\":360,\"Parameters\":{\"DBSnapshotIdentifier\":\"awsbackup:job-00000000-0000-0000-0000-000000000\",\"DBSubnetIds\":[\"subnet-79663144\", \"subnet-d0cf52fa\"]}}"

TEMPLATE CREATE:

  1. Output the execution parameters JSON schema for this change type to a JSON file; this example names it CreateRdsFromBackupParams.json:

    aws amscm get-change-type-version --change-type-id "ct-0g690ekkyfm79" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateRdsFromBackupParams.json
  2. Modify and save the CreateRdsFromBackupParams file.

    { "Description": "Create RDS Instance Stack from Backup: awsbackup:job-00000000-0000-0000-0000-000000000.", "VpcId": "vpc-00000000", "StackTemplateId": "stm-siqajx00000000000", "Name": "Stack Name", "TimeoutInMinutes": 360, "Parameters": { "DBSnapshotIdentifier": "awsbackup:job-00000000-0000-0000-0000-000000000", "DBSubnetIds": ["subnet-79663144", "subnet-d0cf52fa"] } }
  3. Output the RFC template to a file in your current folder; this example names it CreateRdsFromBackupRfc.json:

    aws amscm create-rfc --generate-cli-skeleton > CreateRdsFromBackupRfc.json
  4. Modify and save the CreateRdsFromBackupRfc.json file. For example, you can replace the contents with something like this:

    { "ChangeTypeId": "ct-0pgvtw5rpcsb6", "ChangeTypeVersion": "1.0", "Title": "Create RDS Instance Stack from Backup" }
  5. Create the RFC, specifying the CreateRdsFromBackupRfc file and the CreateRdsFromBackupParams file:

    aws amscm create-rfc --cli-input-json file://CreateRdsFromBackupRfc.json --execution-parameters file://CreateRdsFromBackupParams.json

    You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.

To learn more about Amazon RDS, including size recommendations, see Amazon Relational Database Service Documentation.

To learn more about Amazon RDS, including size recommendations, see Amazon Relational Database Service Documentation.

Execution Input Parameters

For detailed information about the execution input parameters, see Schema for Change Type ct-0pgvtw5rpcsb6.

Example: Required Parameters

{ "Description": "Create RDS Instance Stack from snapshot: awsbackup:job-00000000-0000-0000-0000-000000000000.", "VpcId": "vpc-12345678901234567", "StackTemplateId": "stm-siqajx00000000000", "Name": "Stack Name", "Parameters": { "DBSnapshotIdentifier": "awsbackup:job-00000000-0000-0000-0000-000000000000", "DBSubnetIds": ["subnet-1234567890abcdef0", "subnet-1234567890abcdef1"] } }

Example: All Parameters

{ "Description": "Create RDS Instance Stack from snapshot: rds:sr341e8q8bofsd-2017-04-19-22-13.", "VpcId": "vpc-12345678", "StackTemplateId": "stm-siqajx00000000000", "Name": "Stack Name", "Tags": [ { "Key": "foo", "Value": "bar" }, { "Key": "testkey", "Value": "testvalue" } ], "TimeoutInMinutes": 60, "Parameters": { "DBInstanceClass": "db.m3.medium", "DBInstanceIdentifier": "my-rds-id", "DBSnapshotIdentifier": "customizedSnapshotId", "DBSubnetIds": ["subnet-a0b1c2d3", "subnet-a0b2c9d8"] } }
프라이버시사이트 이용 약관쿠키 기본 설정
© 2025, Amazon Web Services, Inc. 또는 계열사. All rights reserved.