LogoLogo
  • 1 Introduction to N2WS
  • 2 Installing and Upgrading N2WS
  • 3 Start Using N2WS
  • 4 Defining Backup Policies
  • 5 Consistent Backup with N2WS
  • 6 Windows Instances Backup
  • 7 Linux/Unix Instances Backup
  • 8 Using Elastic File System (EFS)
  • 9 Additional Backup Topics
  • 10 Performing Recovery
  • 11 Disaster Recovery
  • 12 Cross-Account DR, Backup, and Recovery
  • 13 File-Level Recovery
  • 14 Tag-based Backup Management
  • 15 Resource Control
  • 16 Security Concerns and Best Practices
  • 17 Alerts, Announcements, Notifications, and Reporting
  • 18 N2WS User Management
  • 19 N2WS IdP Integration
  • 20 Configuring N2WS with CloudFormation
  • 21 Managing Snapshots with Lifecycle Policies
  • 22 Configuring Workers
  • 23 Capturing and Cloning in Network Environments
  • 24 Orchestrating Recovery Scenarios
  • 25 Monitoring Costs and Savings
  • 26 Using N2WS with Azure
  • 27 Using Wasabi Storage
  • Appendix A -Recommended Configuration for Copy to S3
  • Appendix B - Agents Configuration Format
  • Appendix C - Time Zones
  • Appendix D - Datadog Integration
  • Appendix E - Splunk Integration Support
  • Appendix F - Resetting Root Password or MFA
  • Appendix G - Securing Default Certificates on N2WS Server
Powered by GitBook
On this page

Was this helpful?

Export as PDF

20 Configuring N2WS with CloudFormation

You can model and manage your infrastructure resources with AWS CloudFormation.

Previous19 N2WS IdP IntegrationNext21 Managing Snapshots with Lifecycle Policies

Was this helpful?

The process to configure N2WS to work with CloudFormation is a single stream that starts with subscribing to N2WS on the Amazon Marketplace and ends with configuring the N2WS server.

  • N2WS provides several editions, all of which support CloudFormation.

  • An IAM role will automatically be created with minimal permissions and assigned to the N2WS instance.

  1. Go to

  2. Search for N2WS.

  3. Select CPM Edition to install:

  • Free Trial & BYOL

  • Advanced

  • Free

  • Standard

  • Enterprise

4. Select Continue to Subscribe. Log in and select Accept Terms.

5. Select Continue to Configuration.

6. In the Fulfillment Option drop-down list, select CloudFormation Template. Select the relevant Software Version and Region and then select Continue to Launch.

7. In the Launch this software page, select Launch CloudFormation in the Choose Action list and then select Launch.

The Create stack/Specify template page opens.

8. Under Prepare template, select Template is ready.

9. Under Template source, choose Amazon S3 URL. Select the default Amazon S3 URL and then select Next. The Specify stack details page opens.

10. Complete the Stack name and Parameters sections. For Inbound Access CIDR, security groups act as a firewall for associated instances, controlling both inbound and outbound traffic at the instance level. Configuring Inbound Access CIDR allows you to add rules to a security group that enable you to connect to your Linux instance from your IP address using SSH:

  • If your IPv4 address is 203.0.113.25, specify 203.0.113.25/32 to list this single IPv4 address in CIDR notation. If your company allocates addresses within a range, specify the entire range, such as 203.0.113.0/24.

  • If you specify 0.0.0.0/0, it will enable all IPv4 addresses to access your instance using SSH.

11. Select Next. The Configure stack options page opens.

12. Complete the stack options and select Next. The Review page opens.

13. Select I acknowledge that AWS CloudFormation might create IAM resources, and then select Create stack. The CloudFormation Stacks page opens.

14. Select the new stack. The Instances page opens.

15. Select the instance. Copy the Instance ID value shown in the Description tab and select Launch Instance. The N2WS Server Configuration page opens.

Configure CPM with CloudFormation will fail where the requested Instance type is not supported in the requested Availability Zone. Retry your request, but do not specify an Availability Zone or choose us-east-1a, us-east-1b, us-east-1c, us-east-1d, or us-east-1f.

For further details, refer to “Adding a Rule for Inbound SSH Traffic to a Linux Instance” at ​

16. Continue configuring N2WS as in section .

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html
2
https://aws.amazon.com/marketplace