Tjyylli

Effects on objects due to a brief relocation of massive amounts of mass

What's the meaning of "fortified infraction restraint"?

How would a mousetrap for use in space work?

Is there a kind of relay that only consumes power when switching?

What is "gratricide"?

Why do we bend a book to keep it straight?

Why should I vote and accept answers?

Do wooden building fires get hotter than 600°C?

Did Deadpool rescue all of the X-Force?

What order were files/directories outputted in dir?

How come Sam didn't become Lord of Horn Hill?

Why do we need to use the builder design pattern when we can do the same thing with setters?

How do I use the new nonlinear finite element in Mathematica 12 for this equation?

If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?

Is there any word for a place full of confusion?

Maximum summed subsequences with non-adjacent items

Why is Nikon 1.4g better when Nikon 1.8g is sharper?

How to write the following sign?

Trademark violation for app?

Take 2! Is this homebrew Lady of Pain warlock patron balanced?

What does it mean that physics no longer uses mechanical models to describe phenomena?

Amount of permutations on an NxNxN Rubik's Cube

How does Python know the values already stored in its memory?

What do you call the main part of a joke?

AWS - Unable to enable encryption of EBS volumes when creating/updating Cloudformation stack [on hold]

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

0

I am operating in the US-East-2 region for building test stacks with CloudFormation, and am using Packer to build AMI's. When I enable Encrypted:True for the BlockDeviceMappings on some of my instances and autoscalers, Cloudformation gives me the below error:
"The encrypted flag cannot be specified since device /dev/sda1 has a snapshot specified"
In looking at my snapshots, the only ones I show on my account are those that were generated when Packer creates an AMI.
I have went over my template configurations several times, and was unable to notice any changes between an older stack configuration that was known to be working. From what I can tell, both templates have identical BlockDevice configs. I am creating my CloudFormation YAML's through Troposphere.
I have also tried researching this issue myself, and have been getting a lot of mixed opinions on causes ranging from the region I am in, to bugs in Hashicorp's Packer code that was supposed to have been fixed in more recent versions. The Packer versions I have tried so far include 1.0.4 and 1.4.0. The base AMI's I have been using for my Packer builds are CentOS7. Does anyone have any insight on how to figure out possible causes and solutions? I greatly appreciate any assistance.

amazon-web-services centos-7 packer

share|improve this question

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

put on hold as off-topic by DavidPostill♦ 9 hours ago

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "This question is not about computer hardware or software, within the scope defined in the help center." – DavidPostill

If this question can be reworded to fit the rules in the help center, please edit the question.

add a comment | 

0

I am operating in the US-East-2 region for building test stacks with CloudFormation, and am using Packer to build AMI's. When I enable Encrypted:True for the BlockDeviceMappings on some of my instances and autoscalers, Cloudformation gives me the below error:
"The encrypted flag cannot be specified since device /dev/sda1 has a snapshot specified"
In looking at my snapshots, the only ones I show on my account are those that were generated when Packer creates an AMI.
I have went over my template configurations several times, and was unable to notice any changes between an older stack configuration that was known to be working. From what I can tell, both templates have identical BlockDevice configs. I am creating my CloudFormation YAML's through Troposphere.
I have also tried researching this issue myself, and have been getting a lot of mixed opinions on causes ranging from the region I am in, to bugs in Hashicorp's Packer code that was supposed to have been fixed in more recent versions. The Packer versions I have tried so far include 1.0.4 and 1.4.0. The base AMI's I have been using for my Packer builds are CentOS7. Does anyone have any insight on how to figure out possible causes and solutions? I greatly appreciate any assistance.

amazon-web-services centos-7 packer

share|improve this question

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

put on hold as off-topic by DavidPostill♦ 9 hours ago

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "This question is not about computer hardware or software, within the scope defined in the help center." – DavidPostill

If this question can be reworded to fit the rules in the help center, please edit the question.

add a comment | 

I am operating in the US-East-2 region for building test stacks with CloudFormation, and am using Packer to build AMI's. When I enable Encrypted:True for the BlockDeviceMappings on some of my instances and autoscalers, Cloudformation gives me the below error:
"The encrypted flag cannot be specified since device /dev/sda1 has a snapshot specified"
In looking at my snapshots, the only ones I show on my account are those that were generated when Packer creates an AMI.
I have went over my template configurations several times, and was unable to notice any changes between an older stack configuration that was known to be working. From what I can tell, both templates have identical BlockDevice configs. I am creating my CloudFormation YAML's through Troposphere.
I have also tried researching this issue myself, and have been getting a lot of mixed opinions on causes ranging from the region I am in, to bugs in Hashicorp's Packer code that was supposed to have been fixed in more recent versions. The Packer versions I have tried so far include 1.0.4 and 1.4.0. The base AMI's I have been using for my Packer builds are CentOS7. Does anyone have any insight on how to figure out possible causes and solutions? I greatly appreciate any assistance.

amazon-web-services centos-7 packer

share|improve this question

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 10 hours ago

mprocentmprocent

1

New contributor

mprocent is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 10 hours ago

mprocentmprocent

1