Support different AWS EBS storage choices

[burgerjeffrey]

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

I would like to be able to choose a storage option for the EC2 when created using the "om vm-lifecycle" command.

Describe alternatives you've considered

No response

Additional context

No response

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[haydonryan-pivotal]

I also wanted to throw my support behind this Feature Request.

In AWS it's possible that an organization will have a policy that requires EBS encryption enabled for all vms being deployed (PCI requirement). We're experiencing an issue where having enable the AWS option "EBS encryption by default" is not encrypting the EBS volume by default when created via OM / AWS cli.

aws ec2 get-ebs-encryption-by-default --region region

Returns that this feature is enabled.

We can hijack the container and run the aws command that OM is running and add in a custom --block-device-mappings parameter to the aws command and it works.

[burgerjeffrey]

I also wanted to throw my support behind this Feature Request.

In AWS it's possible that an organization will have a policy that requires EBS encryption enabled for all vms being deployed (PCI requirement). We're experiencing an issue where having enable the AWS option "EBS encryption by default" is not encrypting the EBS volume by default when created via OM / AWS cli.

aws ec2 get-ebs-encryption-by-default --region region

Returns that this feature is enabled.

We can hijack the container and run the aws command that OM is running and add in a custom --block-device-mappings parameter to the aws command and it works.

i no longer run CF, but my solution around EBS encryption of OpsMan was to encrypt the public OpsMan AMI in every AWS account I needed it in to meet my requirement by creating my own private AMI and using that instead:

aws ec2 copy-image --source-image-id ${OPSMAN_PUBLIC_AMI_ID} --source-region ${S3_REGION} --region ${S3_REGION} --encrypted --name "encrypted-${AMI_NAME}" --description "encrypted-${AMI_NAME}"

[haydonryan-pivotal]

Maybe the change is as easy as adding a CLI additional parameters section to create-vm