As shown in the architecture diagram below, the first template will create an NFS server, an Application server, and a DataSync agent, and a File Gateway appliance will be deployed in an AWS region simulating the on-premises environment.
Note: Instances that are launched as part of this CloudFormation template may be in the initializing state for few minutes.
While the CloudFormation deployment progresses in the on-premises region, you can proceed to deploy resources for the in-cloud region.
This template will create an S3 bucket to simulate the AWS cloud region to which the NFS server’s data will be migrated.
The below template creates an UNENCRYPTED bucket. This is intentional. This template is to be scanned and remediated with the Conformity IaC Template Scanner VS code extension for misconfigurations. Any S3 bucket created should be encrypted at a minimum. Some exceptions include static S3 websites. If you DO NOT have access to Conformity please skip this step and use the IaC under step 1.*
CLICK HERE
to see how to scan the Cloudformation template for misconfigurations- MAC OS: ⇧ + ⌘ + P
- Windows/Linux: Ctrl+Shift+P
The result will appear in a second tab called Scan Result like the image below.
You can also check out the Conformity Knowledge Base, which can help you better understand more about any best practice check violations and how to remediate and fix them in your CloudFormation template or in production environments:
AWS::S3::Bucket
BucketEncryption:
ServerSideEncryptionConfiguration:
- ServerSideEncryptionByDefault:
SSEAlgorithm: AES256
The below template creates an ENCRYPTED bucket using SSE-S3. This template is for thse who do not have a Conformity account or IDE to edit code.
It should take about 10 minutes for both CloudFormation stacks to complete.