You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ Use the following steps to prepare your workflow for running on your EC2 self-ho
147
147
148
148
> [!IMPORTANT]
149
149
> If you are planning on using Spot instances for your runner, AWS uses a service-linked role to provision the instances.
150
-
>
150
+
>
151
151
> For this to work, at least one of the following must be true:
152
152
> - The service-linked role exists already. This happens if you request a Spot instance via the AWS Console interface.
153
153
> - You create the service-linked role via the Console, AWS CLI or AWS API.
@@ -189,7 +189,7 @@ Alternatively, you can use a vanilla EC2 AMI and set up the dependencies via `pr
189
189
Or use the existing VPC and subnet.
190
190
2. Create a new security group for the runners in the VPC.
191
191
Only **outbound** traffic on port TCP/443 is required to pull jobs from GitHub.
192
-
No inbound traffic is required for this purpose, but if your workflow needs to access external repositories or internal SSH, other ports like TCP/22, TCP/80, etc ... may be required.
192
+
No inbound traffic is required for this purpose, but if your workflow needs to access external repositories or internal SSH, other ports like TCP/22, TCP/80, etc ... may be required.
193
193
194
194
**5. Configure the GitHub workflow**
195
195
@@ -220,7 +220,10 @@ Now you're ready to go!
220
220
|`block-device-mappings`| Optional. Used only with the `start` mode. | JSON string specifying the block device mappings for the EC2 instance. For example: <br> <pre>[{"DeviceName": "/dev/sda1", "Ebs": {"VolumeSize": 100, "VolumeType": "gp3"}}]</pre> See <ahref="https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_BlockDeviceMapping.html">AWS BlockDeviceMapping docs</a> for all options. |
We have observed a consistently poor acceptance rate for Norway over the past few months, leading to significant financial losses, which we estimate to be in the millions. We have been in contact with Kustom, who provided us with data confirming this issue, and we have drawn the following conclusion:
4
+
We have compared the Swedish and Norwegian markets in terms of renewal acceptance rates over the past 60 days. The discrepancy between the two markets is highly concerning, with Norway's acceptance rate being significantly lower.
5
+
This is a matter of great urgency, and we expect you to respond immediately with a detailed plan on how you intend to resolve this issue, as well as the steps you will take to mitigate our losses going forward. It is unacceptable for a payment provider of your size—especially one approaching an IPO—to be experiencing such critical issues.
0 commit comments