mysterious-wolf-74677
05/13/2021, 10:52 PMimport
feature I'm guessing?future-nightfall-79300
05/14/2021, 2:01 PMDispatched with response: {'tasks': [], 'failures': [{'reason': 'The requested CPU configuration is above your limit'}],
However, we have not found any documentation about how to raise this limit, since the service quota increase has not solved this issue. Only thing about this found by Googling has been this thread, that has no answers: https://forums.aws.amazon.com/thread.jspa?threadID=335825.
Does someone here happen to have had this issue, and has resolved it somehow?
This started to happen a while back, and before this it was working ok. So it's quite confusingalert-area-12501
05/14/2021, 2:18 PMassignGeneratedIpv6CidrBlock: true
I might assume it should automatically add a route table route for outbound ipv6 traffic like ::/0
through the internet gateway like it does with ipv4 traffic and 0.0.0.0/0
, but it doesn't. Not sure if this is really a bug or anything it just caused me some time tracking down why some outbound internet traffic was not working and found it was exclusive to ipv6.proud-art-41399
05/14/2021, 7:17 PMcold-caravan-83486
05/15/2021, 9:14 AMerror: 1 error occurred:
* updating urn:pulumi:dev::Deployment::aws:lambda/permission:Permission::wordPermission: 1 error occurred:
* doesn't support update
Is there a way to force the permission to be deleted and re-created instead of updated; or do I have to remove it from the code and pulumi up
and then put it back again?microscopic-zoo-3564
05/16/2021, 10:07 PMconst secret = pulumi.output(
aws.secretsmanager.getSecret(
{
name: stackReferenceToSecretName,
},
{ async: true }
)
)
I keep running into a typescript error Type 'string | Output<any>' is not assignable to type 'string | undefined'
shy-house-53993
05/17/2021, 11:28 AMpurple-plumber-90981
05/17/2021, 10:20 PMquick-traffic-77022
05/18/2021, 10:07 AMlemon-television-29125
05/18/2021, 2:31 PMlemon-television-29125
05/18/2021, 2:33 PMlemon-television-29125
05/18/2021, 2:34 PMfull-artist-27215
05/18/2021, 4:46 PMpulumi_docker.Image
to build and push images to an ECR repository? Thanks.lemon-television-29125
05/18/2021, 6:25 PMlemon-television-29125
05/18/2021, 6:26 PMlittle-cartoon-10569
05/18/2021, 10:27 PMwet-ambulance-3300
05/19/2021, 10:46 AMmicroscopic-dress-1605
05/19/2021, 1:01 PMaws-iam-policy
a Node.js Typescript package for building and unit testing AWS IAM Policy documents.
Today I’ve released v2.0.0 with proper support for the Condition
element (which was missing).
https://github.com/thinkinglabs/aws-iam-policy/tree/v2.0.0broad-hairdresser-1495
05/19/2021, 2:13 PMpanic: strconv.ParseUint: parsing "": invalid syntax
error:
# pulumi up
Previewing update (dev):
Type Name Plan Info
+ pulumi:pulumi:Stack staging-dev create 8 messages
└─ pulumi:providers:aws default_4_5_0 1 error
Diagnostics:
pulumi:pulumi:Stack (staging-dev):
panic: strconv.ParseUint: parsing "": invalid syntax
goroutine 1 [running]:
<http://github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge.GetModuleMajorVersion(0x0|github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfbridge.GetModuleMajorVersion(0x0>, 0x0, 0xc00199f5b0, 0x1)
/home/runner/go/pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.0.0/pkg/tfbridge/info.go:730 +0x1dc
<http://github.com/pulumi/pulumi-aws/provider/v4.Provider(0x0|github.com/pulumi/pulumi-aws/provider/v4.Provider(0x0>, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/runner/work/pulumi-aws/pulumi-aws/provider/resources.go:4173 +0x52e1b
main.main()
/home/runner/work/pulumi-aws/pulumi-aws/provider/cmd/pulumi-resource-aws/main.go:26 +0x37
pulumi:providers:aws (default_4_5_0):
error: could not read plugin [/root/.pulumi/plugins/resource-aws-v4.5.0/pulumi-resource-aws] stdout: EOF
# ll /root/.pulumi/plugins/resource-aws-v4.5.0/
total 255496
-rw-r--r--. 1 root root 38593 May 19 14:00 CHANGELOG.md
-rw-r--r--. 1 root root 11358 May 19 14:00 LICENSE
-rwxr-xr-x. 1 root root 261558786 May 19 14:00 pulumi-resource-aws
# uname -mso
Linux x86_64 GNU/Linux
wooden-student-58350
05/19/2021, 6:11 PMaws.Provider
to assume role into a sub-account role and create a resource in that sub-account:
# ~/.aws/credentials
[bastion-profile]
aws_access_key_id = redact
aws_secret_access_key = redact
# Pulumi.<stack>.yaml
…
config:
aws:allowedAccountIds:
- <bastionAccountId>
aws:profile: bastion-profile
aws:region: eu-west-2
…
# index.ts
// Assume role into IAM Role "role-manager" in sub-account.
const subAccountProvider = new aws.Provider("…", {
region: "eu-west-2",
allowedAccountIds: [subAccountId],
assumeRole: {
sessionName "role-manager-session",
roleArn: `arn:aws:iam::${subAccountId}:role/role-manager`,
externalId: "…",
durationSeconds: 60 * 5,
},
});
// Create a new resource in the sub-account.
const newRoleInSubAccount = new aws.iam.Role("new-role", {
…
}, {
provider: subAccountProvider,
});
On pulumi up
, I get the following error:
error: 1 error occurred:
* error configuring Terraform AWS Provider: IAM Role (arn:aws:iam::<redact>:role/role-manager) cannot be assumed.
There are a number of possible causes of this - the most common are:
* The credentials used in order to assume the role are invalid
* The credentials do not have appropriate permission to assume the role
* The role ARN is not valid
Error: NoCredentialProviders: no valid providers in chain. Deprecated.
For verbose messaging see aws.Config.CredentialsChainVerboseErrors
I have verified:
• aws.getCallerIdentity()
returns the expected IAM User from the “bastion-profile” credentials in ~/.aws/credentials
. That User has permission for the sts:AssumeRole
action on the Role ARN in the error message.
• The IAM Role ARN in the error message exists, and its trust relationship allows the sts:AssumeRole
action for any user in the bastion account.
• The default AWS provider works fine to create/destroy resources in the bastion account, so the credentials are valid.
What am I missing? Does Pulumi treat ~/.aws/credentials
differently for explicit providers vs the default provider?green-musician-49057
05/19/2021, 6:22 PMpulumi up
aws:cloudformation:Stack (ec2Stack):
error: 1 error occurred:
* updating urn:pulumi:env::project::aws:cloudformation/stack:Stack::ec2Stack: 1 error occurred:
* error waiting for CloudFormation Stack update: failed to update CloudFormation stack (UPDATE_ROLLBACK_COMPLETE): []
Any ideas?careful-beard-19872
05/19/2021, 7:05 PMbitter-application-91815
05/20/2021, 1:16 PMbitter-application-91815
05/20/2021, 1:16 PMbitter-application-91815
05/20/2021, 1:16 PMbitter-application-91815
05/20/2021, 1:54 PMbitter-application-91815
05/20/2021, 1:55 PMbitter-application-91815
05/20/2021, 5:29 PMbitter-application-91815
05/20/2021, 5:30 PMlittle-market-63455
05/21/2021, 8:19 AM