![]() disableRollback: true rollbackConfiguration: MonitoringTimeInMinutes: 20 RollbackTriggers: - Arn: arn:aws:cloudwatch:us-east-1:000000000000:alarm:health Type: AWS::CloudWatch::Alarm - Arn: arn:aws:cloudwatch:us-east-1:000000000000:alarm:latency Type: AWS::CloudWatch::Alarm tracing: # Can only be true if API Gateway is inside a stack. To be used for non-production environments. notificationArns: - 'arn:aws:sns:us-east-1:XXXXXX:mytopic' stackParameters: - ParameterKey: 'Keyname' ParameterValue: 'Value' # Disable automatic rollback by CloudFormation on failure. # serverless.yml # Stage parameters params: # Values for the "prod" stage prod: my-parameter: foo # Values for the "dev" stage dev: my-parameter: bar Provider General settings # serverless.yml provider: name: aws # Default stage (default: dev) stage: dev # Default region (default: us-east-1) region: us-east-1 # The AWS profile to use to deploy (default: "default" profile) profile: production # Use a custom name for the CloudFormation stack stackName: custom-stack-name # Optional CloudFormation tags to apply to APIs and functions tags: foo: bar baz: qux # Optional CloudFormation tags to apply to the stack stackTags: key: value # Method used for CloudFormation deployments: 'changesets' or 'direct' (default: changesets) # See deploymentMethod: direct # List of existing Amazon SNS topics in the same region where notifications about stack events are sent. Learn more about stage parameters in the Parameters documentation. ![]() env files (default: false) # See useDotenv: true # 'warn' reports deprecations on the go, 'error' will result with an exception being thrown on first approached deprecation deprecationNotificationMode: warn:summary # Disable deprecations by their codes (default: empty) # See disabledDeprecations: - DEP_CODE_1 # Deprecation code to disable - '*' # Disable all deprecation messages Parameters Root properties # serverless.yml # Service name service: myservice # Framework version constraint (semver constraint): '3', '^2.33' frameworkVersion: '3' # Configuration validation: 'error' (fatal error), 'warn' (logged to the output) or 'off' (default: warn) # See configValidationMode: error # Load environment variables from. PD snapshots are global enabling customers to easily create PDs in any region.Here is a list of all available properties in serverless.yml when the provider is set to aws. As discussed in part 2, GCE has a global scope that is independent of regions. For example, to export an EBS volume from US-EAST to US-WEST, you have to create a snapshot in US-EAST and then initiate the copy process to US-WEST to restore that. What this means to the customers? They need not deal with the manual copy of snapshots across regions. While EBS snapshots are specific to an AWS region, PD snapshots are global. Like the way EBS snapshots are stored in Amazon S3, PD snapshots are stored in Google Cloud Storage.But, the major difference between EBS snapshots and PD snapshots is at the scope. GCEcreates differential snapshots, which allow for better performance and lower storage charges. There is a lot of similarity between Amazon EBS snapshots and GCE PD snapshots. Like EBS, PD’s performance is proportional to the size of the disk. The maximum size supported by EBS is 1TB.GCE Persistent Disks can be up to 10TB.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |