Cookie の設定を選択する

当社は、当社のサイトおよびサービスを提供するために必要な必須 Cookie および類似のツールを使用しています。当社は、パフォーマンス Cookie を使用して匿名の統計情報を収集することで、お客様が当社のサイトをどのように利用しているかを把握し、改善に役立てています。必須 Cookie は無効化できませんが、[カスタマイズ] または [拒否] をクリックしてパフォーマンス Cookie を拒否することはできます。

お客様が同意した場合、AWS および承認された第三者は、Cookie を使用して便利なサイト機能を提供したり、お客様の選択を記憶したり、関連する広告を含む関連コンテンツを表示したりします。すべての必須ではない Cookie を受け入れるか拒否するには、[受け入れる] または [拒否] をクリックしてください。より詳細な選択を行うには、[カスタマイズ] をクリックしてください。

S3 Access Point | Create Access Point (Review Required)

フォーカスモード
S3 Access Point | Create Access Point (Review Required) - AMS Advanced Change Type Reference
このページはお客様の言語に翻訳されていません。 翻訳のリクエスト

Create an access point and associate it with the specified S3 bucket.

Full classification: Deployment | Advanced stack components | S3 Access Point | Create Access Point (review required)

Change Type Details

Change type ID

ct-1elb1vtam0ka5

Current version

1.0

Expected execution duration

240 minutes

AWS approval

Required

Customer approval

Not required if submitter

Execution mode

Manual

Additional Information

Create an S3 access point

Screenshot of this change type in the AMS console:

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:

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

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotation marks 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 --title="Add Static Route" --description="Create an access point and associate it with the specified S3 bucket." --ct-id="ct-1elb1vtam0ka5" --ct-version="1.0" --input-params="{\"Access Point Name\":\"accesspoint1\",\"Bucket Name\":\"s3bucket1\",\"Network Origin\":\"VPC\"}"

TEMPLATE CREATE:

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

    aws amscm get-change-type-version --change-type-id "ct-1elb1vtam0ka5" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateS3AccessPointParams.json\"Access Point Policy\":\"Example access point policy\"
  2. Modify and save the CreateS3AccessPointParams file.

    { "Access Point Name": "accesspoint1", "Bucket Name": "s3bucket1", "Network Origin": "VPC", "Vpc Id": "vpc-12345678" "Access Point Policy": "Example access point policy" }
  3. Output the RFC template JSON file to a file named CreateS3AccessPointRfc.json:

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

    { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1elb1vtam0ka5", "Title": "S3-Accesspoint-Create-RFC" }
  5. Create the RFC, specifying the CreateS3AccessPointRfc file and the CreateS3AccessPointParams file:

    aws amscm create-rfc --cli-input-json file://CreateS3AccesspointRfc.json --execution-parameters file://CreateS3AccesspointParams.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

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotation marks 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 --title="Add Static Route" --description="Create an access point and associate it with the specified S3 bucket." --ct-id="ct-1elb1vtam0ka5" --ct-version="1.0" --input-params="{\"Access Point Name\":\"accesspoint1\",\"Bucket Name\":\"s3bucket1\",\"Network Origin\":\"VPC\"}"

TEMPLATE CREATE:

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

    aws amscm get-change-type-version --change-type-id "ct-1elb1vtam0ka5" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateS3AccessPointParams.json\"Access Point Policy\":\"Example access point policy\"
  2. Modify and save the CreateS3AccessPointParams file.

    { "Access Point Name": "accesspoint1", "Bucket Name": "s3bucket1", "Network Origin": "VPC", "Vpc Id": "vpc-12345678" "Access Point Policy": "Example access point policy" }
  3. Output the RFC template JSON file to a file named CreateS3AccessPointRfc.json:

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

    { "ChangeTypeVersion": "1.0", "ChangeTypeId": "ct-1elb1vtam0ka5", "Title": "S3-Accesspoint-Create-RFC" }
  5. Create the RFC, specifying the CreateS3AccessPointRfc file and the CreateS3AccessPointParams file:

    aws amscm create-rfc --cli-input-json file://CreateS3AccesspointRfc.json --execution-parameters file://CreateS3AccesspointParams.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 S3, see Amazon Simple Storage Service Documentation.

To learn more about Amazon S3, see Amazon Simple Storage Service Documentation.

Execution Input Parameters

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

Example: Required Parameters

Example not available.

Example: All Parameters

Example not available.
プライバシーサイト規約Cookie の設定
© 2025, Amazon Web Services, Inc. or its affiliates.All rights reserved.