Skip to content

Latest commit

 

History

History
81 lines (65 loc) · 3.82 KB

File metadata and controls

81 lines (65 loc) · 3.82 KB

AppRunner

AWS's apprunner service · portable interface driver.AppRunner · AWS index

Operations (27)

Operation Description
CreateAutoScalingConfiguration
CreateConnection
CreateObservabilityConfiguration
CreateService
CreateVpcConnector
DeleteAutoScalingConfiguration
DeleteConnection
DeleteObservabilityConfiguration
DeleteService
DeleteVpcConnector
DescribeAutoScalingConfiguration
DescribeObservabilityConfiguration
DescribeService
DescribeVpcConnector
ListAutoScalingConfigurations
ListConnections
ListObservabilityConfigurations
ListOperations
ListServices
ListTagsForResource
ListVpcConnectors
PauseService
ResumeService
StartDeployment
TagResource
UntagResource
UpdateService

Optional capabilities

Discovered by type assertion; only some providers implement these.

CustomDomains

CustomDomains is the optional custom domain capability.

Operation Description
AssociateCustomDomain
DescribeCustomDomains
DisassociateCustomDomain

DefaultAutoScaling

DefaultAutoScaling is the optional capability to move the account's default auto

Operation Description
ListServicesForAutoScalingConfiguration
UpdateDefaultAutoScalingConfiguration

VpcIngressConnections

VpcIngressConnections is the optional VPC ingress connection capability.

Operation Description
CreateVpcIngressConnection
DeleteVpcIngressConnection
DescribeVpcIngressConnection
ListVpcIngressConnections
UpdateVpcIngressConnection

Not in scope

  • Services do not run your code or image: there is no data plane. ServiceUrl and VPC ingress DomainName are synthesized and not reachable, and request/latency/HTTP-status metrics are never emitted (the CloudWatch mock only gets ActiveInstances, 0 while a service is paused and 1 while it runs). Log groups /aws/apprunner/<name>/<id>/service and /application are created with the service, receive no events and are left in place when the service is deleted (as in AWS).
  • Custom domains stop at pending_certificate_dns_validation (custom domain statuses are lower case on the wire, as in the real service): the emulator cannot validate DNS, so they never reach active. Certificate validation records and the DNS target are synthesized.
  • VPC connector subnet and security group checks only consult the networking mock when the AppRunner mock is wired to one (the default NewAWS provider does this); a standalone apprunner.Mock accepts any ids. VPC ingress VpcId and VpcEndpointId are stored as given and never looked up.
  • Services, ingress connections and custom domains are created ready at once so IaC waiters complete; with --async-settle they report OPERATION_IN_PROGRESS / PENDING_CREATION first for a short window and mutating calls then raise InvalidStateException. A service never ends CREATE_FAILED.
  • Source code builds are not run: a code repository service never reads the repository, and a connection is created PENDING_HANDSHAKE and is never completed by an OAuth handshake.
  • Defaults the AWS docs do not state exactly are the emulator's choice: instance configuration 1 vCPU / 2 GB, health check TCP with interval 5, timeout 2, healthy threshold 1, unhealthy threshold 5, path /. Error message text is descriptive; the exception types are the documented ones.
  • Lists return everything when MaxResults is not given (real App Runner pages at its own default); MaxResults is validated to 1-100.