-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into MLPAB-2329-same-same
- Loading branch information
Showing
1 changed file
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Adding short term ingress | ||
|
||
## Overview | ||
|
||
We sometimes need to temporarily allow access to a service from a specific IP address or range of IP addresses. Instead of making changes to the allow-list repository, we maintain a short-term ingress list as a parameter store in AWS Systems Manager. | ||
|
||
## Adding an IP address to short term ingress for an account | ||
|
||
1. Sign in to the AWS Management Console and assume the operator role into the Management account, in the us-east-1 region. | ||
1. Navigate to the AWS Systems Manager, and then to the Parameter Store. | ||
1. Search for the parameter `/modernising-lpa/additional-allowed-ingress-cidrs/<account-name>` and click on it. | ||
1. Click on the `Edit` button. | ||
1. Add the IP address or range of IP addresses to the `Value` field as comma-separated values. IP addresses should be in CIDR notation. for example a single IP address would be `123.456.789.0/32` and a range of IP addresses would be `123.456.789.0/24`. | ||
1. Click on the `Save changes` button. | ||
1. Lastly, a deployment of the environment is required to apply the changes. | ||
|
||
Remember to remove the IP address or range of IP addresses from the short-term ingress list once they are no longer required. |