mirror of https://github.com/docker/docs.git
feat(scout-ecr): changes to AWS resource names
This commit is contained in:
parent
93e4a87320
commit
58bfdfb94f
|
|
@ -47,7 +47,7 @@ The following table describes the configuration resources.
|
||||||
| `AWS::SecretsManager::Secret` | `ScoutAPICredentials` | Stores the credentials used by EventBridge to fire events to Scout. | $0.42 |
|
| `AWS::SecretsManager::Secret` | `ScoutAPICredentials` | Stores the credentials used by EventBridge to fire events to Scout. | $0.42 |
|
||||||
| `AWS::Events::ApiDestination` | `ApiDestination` | Sets up the EventBridge connection to Docker Scout for sending ECR push and delete events. | $0.01 |
|
| `AWS::Events::ApiDestination` | `ApiDestination` | Sets up the EventBridge connection to Docker Scout for sending ECR push and delete events. | $0.01 |
|
||||||
| `AWS::Events::Connection` | `Connection` | EventBridge connection credentials to Scout. | Free |
|
| `AWS::Events::Connection` | `Connection` | EventBridge connection credentials to Scout. | Free |
|
||||||
| `AWS::Events::Rule` | `Rule` | Defines the rule to send ECR pushes and deletes to Scout. | Free |
|
| `AWS::Events::Rule` | `DockerScoutEcrRule` | Defines the rule to send ECR pushes and deletes to Scout. | Free |
|
||||||
| `AWS::IAM::Role` | `InvokeApiRole` | Internal role to grant the event access to `ApiDestination`. | Free |
|
| `AWS::IAM::Role` | `InvokeApiRole` | Internal role to grant the event access to `ApiDestination`. | Free |
|
||||||
| `AWS::IAM::Role` | `AssumeRoleEcrAccess` | This role has access to `ScoutAPICredentials` for setting up the Docker Scout integration. | Free |
|
| `AWS::IAM::Role` | `AssumeRoleEcrAccess` | This role has access to `ScoutAPICredentials` for setting up the Docker Scout integration. | Free |
|
||||||
|
|
||||||
|
|
@ -79,8 +79,9 @@ To create the stack:
|
||||||
If the button is grayed-out, it means you're lacking the necessary
|
If the button is grayed-out, it means you're lacking the necessary
|
||||||
permissions in the Docker organization.
|
permissions in the Docker organization.
|
||||||
|
|
||||||
4. Follow the steps in the **Create stack** wizard until the end, and complete
|
4. Follow the steps in the **Create stack** wizard until the end. Choose the
|
||||||
the procedure by creating the resources.
|
AWS region you want to integrate. Complete the procedure by creating the
|
||||||
|
resources.
|
||||||
|
|
||||||
The fields in the wizard are pre-populated by the CloudFormation template,
|
The fields in the wizard are pre-populated by the CloudFormation template,
|
||||||
so you don't need to edit any of the fields.
|
so you don't need to edit any of the fields.
|
||||||
|
|
@ -146,7 +147,7 @@ organization.
|
||||||
> AWS resources in your account.
|
> AWS resources in your account.
|
||||||
>
|
>
|
||||||
> After removing the integration in Docker Scout, go to the AWS console and
|
> After removing the integration in Docker Scout, go to the AWS console and
|
||||||
> delete the **ScoutECRIntegration** CloudFormation stack for the integraiton
|
> delete the **DockerScoutECRIntegration** CloudFormation stack for the integration
|
||||||
> that you want to remove.
|
> that you want to remove.
|
||||||
{ .important }
|
{ .important }
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue