diff --git a/docs/citadel/identity-baseline.md b/docs/citadel/identity-baseline.md deleted file mode 100644 index 3596ad7..0000000 --- a/docs/citadel/identity-baseline.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -title: Identity Baseline -sidebar_label: Identity Baseline -sidebar_position: 10 ---- -The process of implementation of Citadel requires that the AWS account is setup with common IAM roles. These roles allow continuous compliance tools to run and create infrastructure. It includes roles to allow access from DNX and DNX automation, as well as roles for accessing the account billing (BillingAccess) and to deploy infrastructure from a developer machine (InfraDeploy). - -DNX engineers will log on to this IDP account using an MFA-enforced SSO and can assume the DNX role, a similar process is described at https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html). - -# Requirements -Admin access to the AWS account. - -# Deployment -This section shows how to deploy the CloudFormation Template required to deploy the basic roles needed to deploy Citadel. - -## Creating the CloudFormation Stack - -Steps: -1. Login to AWS console. -2. Go to Services and type "CloudFormation". -3. Click on CloudFormation. - -![Image](https://files.readme.io/13a038c-image4.png) - - -4. Click on Create Stack - ![4.1 Select "With new resources (standard)"](https://files.readme.io/cbf979e-image1.png) - -5. On the next page insert the stack link on Amazon S3 URL. - -Stack link: https://dnx-assets-prod.s3.ap-southeast-2.amazonaws.com/assets/identity-citadel.cf.yml -![Image](https://files.readme.io/2375c22-image5.png) -6. Click Next. - -7. Insert the stack name "identity-baseline". - - -8. In the Parameters area, we have five options to choose from (CreateInfraDeployUser, DNX, IdentityProviderMetadataDocument, OrgName and TrustArns). - -```bash - { - "data": { - "h-0": "Parameter", - "h-1": "Description", - "0-0": "CreateInfraDeployUser", - "1-0": "DNX", - "2-0": "DNXAutomation", - "3-0": "OrgName", - "4-0": "SAMLProviderArn", - "5-0": "SAMLProviderDocument", - "6-0": "TrustArns", - "1-1": "allow DNX access to this account. Change to true.", - "0-1": "user to be used in some pipeline systems. leave as default (false).", - "2-1": "allow access from DNX automation (required for Citadel-as-a-Service)", - "3-1": "name of YOUR organization for purpose of using in resources naming. E.g.: “apple” or “tesla”.", - "4-1": "ARN of SAML Provider to use. This creates IAM roles 'InfraDeploy' and 'BillingAccess'. Leave as default can be added later\n\n*Use when the SAML Provider is created manually in the account, otherwise use SAMLProviderDocument instead.* ", - "5-1": "SAML Provider XML Document. \nUse only when XML is less then 4096 characters. \nThis creates the SAML Provider and IAM roles 'InfraDeploy' and 'BillingAccess'. Add SAML document if available or leave the default and it can be added later", - "6-1": "Add ARN or Account ID that can deploy resources in this account. \nAn exemple would be the ARN of a InfraDeploy role from the Shared-Services AWS account" - }, - "cols": 2, - "rows": 7 - } - ``` - -![Image](https://files.readme.io/d2a27d8-image3.png) - - -9. On Configure stack options click Next. - -10. On the Review page, mark the checkbox "I acknowledge that AWS CloudFormation might create IAM resources with custom names" and click in Create stack. - -![Image](https://files.readme.io/69a0387-image2.png) - -11. On the Next page, wait for a few minutes and click on Refresh until the process is completed. - -12. When the status changes to CREATE_COMPLETE, the process is done. - -You will need to perform the above procedure for each new account where Citadel will be provisioned. - -## Account Number - -Each Amazon account has an associated 12-digit account identifier (ID). This identifier needs to be sent to DNX. -Below is how to know your account number. -1. Log in to the AWS Management Console. -2. At the top of the page, click the link that is your account name. -3. Click My Account. -4. Your 12-digit account ID is listed under Account Settings. - -When the Identity-Baseline Stack is created in each account please notify DNX and send us the Account ID numbers. \ No newline at end of file diff --git a/docs/devops_playbook/_category_.json b/docs/devops_playbook/_category_.json new file mode 100644 index 0000000..70dd279 --- /dev/null +++ b/docs/devops_playbook/_category_.json @@ -0,0 +1,10 @@ +{ + "label": "DevOps Playbook", + "position": 5, + "collapsible": true, + "collapsed": true, + "link": { + "type": "generated-index", + "title": "DevOps Playbook" + } +} diff --git a/docs/devops_playbook/index.md b/docs/devops_playbook/index.md index ca436d1..f5cefe0 100644 --- a/docs/devops_playbook/index.md +++ b/docs/devops_playbook/index.md @@ -1,7 +1,7 @@ --- layout: default title: DevOps Playbook -nav_order: 6 +nav_order: 4 has_children: true --- diff --git a/docs/foundation/email-address.md b/docs/foundation/email-address.md deleted file mode 100644 index d991233..0000000 --- a/docs/foundation/email-address.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Email Address for AWS Foundation -sidebar_position: 3 -sidebar_label: Email Address ---- - -This document refers to an email structure (email and aliases) DNX suggests to the customer, in order to be used on the AWS well-architected foundation. - -Please, note the differences between providers. If you have a provider that is not listed below, please contact the DNX team. - -**Provider: Office 365 or similar** - -1. Create an email described as below: - -**aws**@yourdomain - -_e.g.: aws@dnxsolutions.com.au_ - -2. Create an alias to each account described as below: - -Alias1: aws-organization-audit@yourdomain -_E.g.:_ _ **aws-dnx-audit@dnxsolutions.com.au** _ - -| Alias2| aws-organization-shared-services@yourdomain | -| Alias3| aws-organization-nonprod@yourdomain | -| Alias4| aws-organization-prod@yourdomain | - -**Provider: G Suite** - -1. Create an email described as below: - -**aws**@yourdomain - -_e.g.: aws@dnxsolutions.com.au_ - -2. G Suite has a feature that allows the user to create the same email like an alias, just need to insert the character plus " **+"** on the email address. So the aliases should be like the list below: - -Alias1: aws**+**organization-audit@yourdomain - -_E.g.: aws __**+**__ dnx-audit@dnxsolutions.com.au_ - -Alias2: aws **+** organization-shared-services@yourdomain - -Alias3: aws **+** organization-nonprod@yourdomain - -Alias4: aws **+** organization-prod@yourdomain - diff --git a/docs/foundation/openvpn.md b/docs/foundation/openvpn.md index 9c3b407..9ca6a1d 100644 --- a/docs/foundation/openvpn.md +++ b/docs/foundation/openvpn.md @@ -1,10 +1,10 @@ --- -title: Configure VPN Connection +title: Configure OpenVPN Connection sidebar_position: 5 -sidebar_label: VPN Configuration +sidebar_label: OpenVPN --- -# DNX Tutorial - How To manage the OpenVPN module +# How To manage the OpenVPN module ## Scope diff --git a/docs/citadel/prepare-aws-org.md b/docs/foundation/prepare-aws-org.md similarity index 99% rename from docs/citadel/prepare-aws-org.md rename to docs/foundation/prepare-aws-org.md index 2b33917..6dc7016 100644 --- a/docs/citadel/prepare-aws-org.md +++ b/docs/foundation/prepare-aws-org.md @@ -1,7 +1,7 @@ --- title: "Preparing your AWS Organization and Accounts" sidebar_label: Preparing your AWS Organization and Accounts -sidebar_position: 11 +sidebar_position: 1 --- # AWS Organization and Accounts diff --git a/docs/citadel/_category_.json b/docs/support/_category_.json similarity index 60% rename from docs/citadel/_category_.json rename to docs/support/_category_.json index bef5b61..76cda9c 100644 --- a/docs/citadel/_category_.json +++ b/docs/support/_category_.json @@ -1,10 +1,10 @@ { - "label": "Citadel", - "position": 3, + "label": "Support", + "position": 6, "collapsible": true, "collapsed": true, "link": { "type": "generated-index", - "title": "Citadel" + "title": "Support" } } \ No newline at end of file diff --git a/docs/support/support-case.md b/docs/support/support-case.md new file mode 100644 index 0000000..a4a921c --- /dev/null +++ b/docs/support/support-case.md @@ -0,0 +1,31 @@ +--- +title: Create a Support case +sidebar_position: 5 +sidebar_label: Create a support case +last_update: + date: 7/01/2022 + author: Catherine Fernandez + +--- + +# How to raise a ticket on Freshdesk? + + + +1. Go to https://dnx.freshdesk.com/support/home. + +2. Click New Support Ticket. + + +![Image](/assets/images/ticket-case-1.png) + + + + +3. Fill-out the required fields. + +![Image](/assets/images/ticket-case-2.png) + + + +4. Click the Submit button. \ No newline at end of file diff --git a/static/assets/images/ticket-case-1.png b/static/assets/images/ticket-case-1.png new file mode 100644 index 0000000..c9c00c5 Binary files /dev/null and b/static/assets/images/ticket-case-1.png differ diff --git a/static/assets/images/ticket-case-2.png b/static/assets/images/ticket-case-2.png new file mode 100644 index 0000000..925d9ae Binary files /dev/null and b/static/assets/images/ticket-case-2.png differ